CVE-2026-125321
pgEdge Postgres MCP denial of service in login rate limiting
An unauthenticated attacker can forge a header to evade login throttling and degrade other users' ability to log in.
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:L
Fuente: CNA
Ciclo de vida de la vulnerabilidad
| Fecha | Fase | Evento | Detalle |
|---|---|---|---|
| Divulgación | Publicada | CVE-2026-125321 divulgada · CVSS 6.5 (CNA) | |
| Monitoreo | Detectada | Ingresó al índice | |
| Divulgación | Evaluación SSVC | CISA-ADP · explotación ninguna | |
| Divulgación | Modificada | Última actualización del registro | |
| Monitoreo | Fuente: OSV | Registro visto por primera vez en OSV | |
| Monitoreo | Verificada | Última verificación contra las fuentes |
The pgEdge Postgres MCP Server, which lets MCP-compatible clients run SQL queries against PostgreSQL databases, has a flaw in its login rate limiting on the non-default HTTP transport when authentication is enabled. An unauthenticated attacker can reach it remotely over the network without logging in, forging the X-Forwarded-For header to evade login throttling or to consume another user's rate-limit bucket, which can degrade that user's ability to log in.
Descripción original del registro (GitHub_M)
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.
Desglose de métricas
Rangos afectados
Estado del parche por paquete
| Paquete / producto | Estado | Corregida en | Desde divulgación | Última versión |
|---|---|---|---|---|
pgedge-postgres-mcp |
Corregida | 1.1.0 | — | — |
1.1.0Arsenal público
Sin exploits, módulos ni PoC públicos conocidos a la fecha de verificación.
https://github.com/pgEdge/pgedge-postgres-mcp/security/advisories/GHSA-v347-v3w7-7fq9https://github.com/pgEdge/pgedge-postgres-mcp/issues/204https://github.com/pgEdge/pgedge-postgres-mcp/pull/205https://github.com/pgEdge/pgedge-postgres-mcp/commit/6a19e46a240b9f4661a4a253811948dd75c4077eLas referencias externas se muestran para copiar: cve.llama.ec no lo redirige a otros sitios.
