pgEdge Postgres MCP Server up to 1.0.9 Rate Limiting middleware.go ExtractIPAddress X-Forwarded-For password in configuration file

Summaryinfo

A vulnerability was found in pgEdge Postgres MCP Server up to 1.0.9 and classified as critical. This vulnerability affects the function ExtractIPAddress of the file internal/auth/middleware.go of the component Rate Limiting. The manipulation of the argument X-Forwarded-For results in password in configuration file. This vulnerability is known as CVE-2026-125321. It is possible to launch the attack remotely. No exploit is available. It is suggested to upgrade the affected component.

Detailsinfo

A vulnerability, which was classified as critical, was found in pgEdge Postgres MCP Server up to 1.0.9. Affected is the function ExtractIPAddress of the file internal/auth/middleware.go of the component Rate Limiting. The manipulation of the argument X-Forwarded-For with an unknown input leads to a password in configuration file vulnerability. CWE is classifying the issue as CWE-13. Storing a plaintext password in a configuration file allows anyone who can read the file access to the password-protected resource making them an easy target for attackers. This is going to have an impact on integrity, and availability. CVE summarizes:

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.

The advisory is shared for download at github.com. This vulnerability is traded as CVE-2026-125321 since 11/09/2026. The exploitability is told to be easy. It is possible to launch the attack remotely. The exploitation doesn't require any form of authentication. There are known technical details, but no exploit is available. The MITRE ATT&CK project declares the attack technique as T1552.001.

Upgrading to version 1.1.0 eliminates this vulnerability.

VulDB is the best source for vulnerability data and more expert information about this specific topic.

Productinfo

Type

• Artificial Intelligence Software

Vendor

• pgEdge

Name

• Postgres MCP Server

Version

• 1.0.0
• 1.0.1
• 1.0.2
• 1.0.3
• 1.0.4
• 1.0.5
• 1.0.6
• 1.0.7
• 1.0.8
• 1.0.9

CPE 2.3info

• 🔒
• 🔒
• 🔒

CPE 2.2info

• 🔒
• 🔒
• 🔒

CVSSv4info

CVSSv3info

CVSSv2info

Exploitinginfo

Threat Intelligenceinfo

Countermeasuresinfo

Timelineinfo

Sourcesinfo

Entryinfo

VulDB is the best source for vulnerability data and more expert information about this specific topic.

Discussion