CVE-2026-126196
pgEdge Postgres MCP SQL injection bypasses read-only mode in query_database
A remote attacker with a low-privilege login can slip writes and session changes past read-only mode.
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:H/A:H
Fuente: CNA
Ciclo de vida de la vulnerabilidad
| Fecha | Fase | Evento | Detalle |
|---|---|---|---|
| Divulgación | Publicada | CVE-2026-126196 divulgada · CVSS 8.1 (CNA) | |
| Monitoreo | Detectada | Ingresó al índice | |
| Monitoreo | Fuente: NIST NVD | Registro visto por primera vez en NIST NVD | |
| Monitoreo | Fuente: ENISA EUVD | Registro visto por primera vez en ENISA EUVD | |
| 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 |
pgEdge Postgres MCP Server's query_database tool can be bypassed by a remote attacker with low-privilege login, who sends unrecognized SQL statements containing multiple semicolon-separated statements to get around its read-only mode and combine writes with session changes when the connecting role has write privileges. This can compromise data integrity and availability, but it does not expose data beyond what the connection could already read.
Affects pgedge-postgres-mcp 1.0.0 and earlier, including alpha and beta pre-releases, where read_only is relied on as a safety boundary and the connecting role holds write privileges. Fixed in 1.1.0.
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, query_database on a read_only connection could send unrecognized statements through pgx Exec without bind parameters, selecting PostgreSQL's simple query protocol and allowing multiple semicolon-separated statements in one request. A caller could combine transaction or session state changes with database writes, and pooled session state could leave later calls writable, when the connecting role held write privileges. The flaw affected deployments relying on read_only as a safety boundary, could compromise integrity and availability, and did not add confidentiality impact beyond the reads already permitted by the connection. This issue is fixed in 1.1.0.
Condiciones y alcance
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-j7mp-839j-jrm7https://github.com/pgEdge/pgedge-postgres-mcp/pull/196https://github.com/pgEdge/pgedge-postgres-mcp/commit/b5b929305de7a22cd6ed7de8ae1be2ac90ca0868https://github.com/pgEdge/pgedge-postgres-mcp/releases/tag/v1.1.0Las referencias externas se muestran para copiar: cve.llama.ec no lo redirige a otros sitios.
