CVE-2026-125321 · AI agents & MCP
NO FIX YET · SEE WHAT TO DO
The pgEdge Postgres MCP Server trusted the leftmost X-Forwarded-For header from callers when rate-limiting logins over its HTTP transport. An unauthenticated attacker can rotate or forge that address to bypass login throttling or exhaust another user's login attempts.
first public Sep 3, 2026 · 1 source
Could this affect your app?
Free first check from your website. Connect your repo for the full answer.
Deployments of the pgEdge Postgres MCP Server that use the HTTP transport with authentication enabled are exposed; the published nginx configuration appends X-Forwarded-For, which makes the issue reachable without operator misconfiguration. Stdio-only or unauthenticated deployments are not described as affected by the sources.
Not affected if auth-disabled, stdio-transport
Who cares http-transport, mcp, nginx, pgedge, postgres
1.1.0 are affected.1.1.0.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.
Check it with your coding agent
It reads this page and tells you if your code is affected.
Are you affected?
Ask from here. InfraStack checks the affected versions against your stack and answers in your inbox.
InfraStack checks the affected versions against your stack and answers in Slack, with the evidence and the fix.
NVD data is provided by NIST and is public domain. Posts quoted belong to their authors.