Rate limiting bypass in pgEdge Postgres MCP Server via X-Forwarded-For header
Key facts
- Attack vector
- Network
- Privileges required
- None
- User interaction
- None
- Attack complexity
- Low
- Impact type
- Denial of service
- Confidentiality · integrity · availability
- Low · None · Low
- Fix status
- Fixed
Attack profile from CVSS 3.1 · CNA. Fix status from CNA. Impact type from CWE-770.
Summary
pgEdge Postgres MCP Server before 1.1.0 uses the leftmost caller-supplied X-Forwarded-For value as the client address for login rate limiting when the nondefault HTTP transport runs with authentication enabled. An unauthenticated remote attacker can send a forged address to evade throttling or consume another user's limiter bucket, which is CWE-807 and CWE-770. The published nginx configuration appends rather than replaces X-Forwarded-For, so the flaw does not require an operator misconfiguration.
Written with Claude Haiku 5.5 from the sources below · 2026-11-10
Description from the CNA
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.
Why it matters now
SSVC decision points
CISA ADP · SSVC 2.0.3
- Exploitation
- None
- Automatable
- Yes
- Technical impact
- Partial
The decision (Track, Attend, Act) also depends on your mission and well-being impact; see CISA's SSVC guide.
Affected products
Remediation
Update pgEdge Postgres MCP Server to version 1.1.0.
Written with Claude Haiku 5.5 from the sources below · 2026-11-10
- Fix · CNA pgedge-postgres-mcp (pgEdge) Fixed in 1.1.0
Timeline
- 2026-11-10 Threatist record created from CVE-2026-125321
- 2026-11-10 CISA SSVC decision points changed
- 2026-11-10 Priority changed: MEDIUM → LOW
References
More pgEdge vulnerabilities
- TI-2026-90432 SQL injection in pgEdge Postgres MCP Server via custom pl-do tools CVSS 3.1HIGH 8.8
- TI-2026-88777 Unbounded corpus read in pgEdge RAG Server allows resource exhaustion CVSS 3.1HIGH 7.5
- TI-2026-90431 Read-only bypass in pgEdge Postgres MCP Server allows database writes CVSS 3.1HIGH 8.1
- TI-2026-87969 Trust rules in pgEdge Control Plane allow passwordless Postgres login CVSS 3.1HIGH 7.8
- TI-2026-88778 pgEdge Go LLM Library exposes provider API key fragments in error messages CVSS 3.1MEDIUM 5.8
- TI-2026-87972 pgEdge RAG Server leaks part of provider API key in error messages CVSS 3.1MEDIUM 5.8
Sources
This product uses the NVD API but is not endorsed or certified by the NVD. Sources and licences