CVE-2026-125321 Details
Description
pgEdge Postgres MCP Server enables SQL queries against PostgreSQL databases through Model Context Protocol compatible clients. Prior to 1.1.0, deployments exposing the nondefault HTTP transport with authentication enabled used the leftmost caller-supplied X-Forwarded-For value as the client address for login rate limiting. ExtractIPAddress in internal/auth/middleware.go supplied that value to IsAllowed and RecordFailedAttempt in internal/auth/rate_limiter.go, allowing an unauthenticated caller to rotate addresses to evade throttling or assert another user's address to consume that user's limiter bucket. The published nginx configuration appended rather than replaced X-Forwarded-For, making the issue reachable without an operator misconfiguration. Username-keyed account lockout did not use the client address, but shipped defaults disabled that separate control through MaxFailedAttemptsBeforeLockout: 0. This issue is fixed in version 1.1.0.
A vulnerability in pgEdge Postgres MCP Server prior to version 1.1.0 allows for the evasion of login rate limiting by manipulating the X-Forwarded-For header. This issue arises in deployments that expose the non-default HTTP transport with authentication enabled. The server's login rate limiter uses the leftmost entry of the X-Forwarded-For header, which can be controlled by the caller, to determine the client's IP address for rate limiting. This exploitation can lead to unthrottled login attempts or disrupt another user's login by consuming their rate limit.
Upgrade to pgEdge Postgres MCP Server version 1.1.0 or later, which resolves the vulnerability by sourcing the client IP from the connection rather than the X-Forwarded-For header. After upgrading, verify and adjust the nginx proxy configuration to replace the X-Forwarded-For header with the real client address, and configure the server to read the client IP from the header only when it comes from a trusted proxy.
Metrics
CVSS 4.0 Severity and Vector Strings:
CVSS 3.x Severity and Vector Strings:
No data available for CVSS Version 2.0 on this CVE.
Volerion
Assessed Nov 10, 2026CISA-ADP
Assessed Nov 10, 2026References to Advisories, Solutions, and Tools
By selecting these links, you will be leaving this site. These are references gathered from the official CVE record and are not endorsed by Volerion.
| URL | Source(s) | Tag(s) |
|---|---|---|
| https://github.com/pgEdge/pgedge-postgres-mcp/commit/6a19e46a240b9f4661a4a253811948dd75c4077e | [email protected] | Source CodeVendor |
| https://github.com/pgEdge/pgedge-postgres-mcp/issues/204 | [email protected] | Issue TrackingTechnical DescriptionVendor |
| https://github.com/pgEdge/pgedge-postgres-mcp/pull/205 | [email protected] | Source CodeVendor |
| https://github.com/pgEdge/pgedge-postgres-mcp/security/advisories/GHSA-v347-v3w7-7fq9 | [email protected] | AdvisoryRemedyVendor |
Weakness Enumeration
| CWE-ID | CWE Name | Source |
|---|---|---|
| CWE-770 | Allocation of Resources Without Limits or Throttling | [email protected] |
| CWE-807 | Reliance on Untrusted Inputs in a Security Decision | [email protected] |
Affected Products
| Product | Versions |
|---|---|
| pgEdge Postgres MCP Server | <= 1.0.0 (semver) |
CPE
Remediation
| |
Change History
2 change records found show changes
| Date | Action | Recorded By |
|---|---|---|
| Nov 10, 2026 | CVE Modified | CISA-ADP |
| Nov 10, 2026 | New CVE Received | [email protected] |
Volerion