CVSS 3.1
6.5 mediumCVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:LCVE-2026-125321 pgedge pgedge-postgres-mcp
Medium (6.5) in pgedge pgedge-postgres-mcp. EPSS 0.5% estimated probability of exploitation activity in the next 30 days.
On this page
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.
Severity
- EPSS
- 0.5% estimated probability of exploitation activity in the next 30 days; 41st percentile. Scored 2026-11-13. A forecast for this CVE across the internet, not for your own systems.
- CISA's assessment (SSVC)
- Exploitation: none · Automatable: yes · Technical impact: partial, assessed 2026-11-10. From CISA's Vulnrichment in the CVE List: whether it is exploited, whether exploiting it can be automated, and how much control it gives.
- CWEs
- CWE-770 Allocation of Resources Without Limits or Throttling
CWE-807 Reliance on Untrusted Inputs in a Security Decision - OWASP Top 10
- A06:2025 Insecure Design
- Published
- Modified
- Assigned by
- GitHub_M (CNA)
- NVD analysis
- Deferred: the NVD does not plan to analyze it
- Record from
- the NVD, synced
Ask an AI about this CVE
Show the prompt
Explain CVE-2026-125321 for an engineer deciding whether to act. Use https://cve.bz/api/public/cves/CVE-2026-125321?via=ask-ai-copy and https://cve.bz/cve/CVE-2026-125321?via=ask-ai-copy as the source of truth: what is affected and which versions fix it, whether it is in CISA KEV, public exploits, and its EPSS (an internet-wide 30-day estimate of exploitation activity, not a forecast for my systems). If they give no fixed versions, use the CVE record https://cveawg.mitre.org/api/cve/CVE-2026-125321 or the vendor advisory, not third-party mirrors. Tell me how to check whether I am affected and how to verify a fix. Cite the sources and say where they are uncertain.Opens a third-party assistant; its answer is its own, not cve.bz's. The prompt holds only this CVE's id and public links.
Badge for a README or a site
An image that stays current: it is drawn from the data each time it is fetched (a host that proxies images, as GitHub does, may show its copy for a while). Markdown:
[](https://cve.bz/cve/CVE-2026-125321)
HTML:
<a href="https://cve.bz/cve/CVE-2026-125321"><img src="https://cve.bz/cve/badge/CVE-2026-125321.svg" alt="CVE-2026-125321"></a>
Affected
Versions
From the CNA's record in the CVE List.
| Product | Affected |
|---|---|
| pgedge-postgres-mcp | < 1.1.0 |
Attack patterns (CAPEC)
The attack patterns MITRE's CAPEC relates to this record's weaknesses, as MITRE names them. Credits. More on the page of CWE-770 (20).
History
- The NVD deferred its analysis
Changes since this site first stored the record. The same for every record: /api/public/changes.