llamaCVEVulnerability Intelligence
/
pgAdmin 4

CVE-2026-116247

pgAdmin 4: libpq uses the pgAdmin service account's own password file and client certificate

Specific setups onlyParche disponibleexposed credentials
Descargar PNG JSON
CVSS 3.1
8.2
Alta
CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:C/C:H/I:H/A:N Fuente: CNA
9.6NVD · CVSS 3.1CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:H/A:N
ExplotaciónSin evidenciaSSVC: none · no figura en CISA KEV
Exploits públicos0Ninguno conocido
Parche1 versión9.19
Exposición19 dDesde la divulgación, 30 oct 2026, 2:55 p. m.
Detección9 minDesde la divulgación hasta su ingreso al índice
Decisión SSVCSeguir de cerca
Monitorear y programar la remediación
Sin explotación conocida, no automatizable e impacto técnico total. Hay versiones corregidas disponibles.
Timeline

Ciclo de vida de la vulnerabilidad

Hoy
Divulgación
Publicada
Evaluación SSVC +1
Explotación
Remediación
Monitoreo
Detectada +1
Fuente: OSV
Verificada
30 oct 26
2 nov 26
6 nov 26
16 nov 26
19 nov 26
30 oct 26
4 nov 26
9 nov 26
14 nov 26
19 nov 26
FechaFaseEventoDetalle
Divulgación Publicada CVE-2026-116247 divulgada · CVSS 8.2 (CNA)
Monitoreo Detectada Ingresó al índice
Monitoreo Fuente: NIST NVD Registro visto por primera vez en NIST NVD
Monitoreo Fuente: OSV Registro visto por primera vez en OSV
Divulgación Evaluación SSVC CISA-ADP · explotación ninguna
Divulgación Modificada Última actualización del registro
Monitoreo Verificada Última verificación contra las fuentes
Resumen
Resumen generado por IA · CC-BY 4.0

In server mode, pgAdmin 4 could let any user connect to a PostgreSQL server using the password file and client certificate belonging to the operating-system account that runs pgAdmin, which an attacker could exploit to access databases they should not reach. The flaw affects pgAdmin 4 releases earlier than 9.19.

Affects pgAdmin 4 before 9.19 when the service account has a password file entry or client certificate that a reachable server accepts. Fixed in 9.19.

¿Qué significa?pgAdmin's libpq uses the pgAdmin service account's own password file and client certificate. An attacker who can reach a database server that accepts those credentials can connect using the service account's stored credentials, with high confidentiality and integrity impact on that server.
¿Quién está afectado?pgAdmin 4 versions before 9.19 are in the affected range, but only where the service account has a password file entry or client certificate that a server the attacker can reach accepts. Check your pgAdmin 4 version and whether the service account has a password file or client certificate configured.
¿Qué hacer?Upgrade pgAdmin 4 to version 9.19 or later, which is the fixed version in the affected range.
Descripción original del registro (PostgreSQL)

When a server in pgAdmin 4 had no password file, client certificate or client key configured, or the configured one could not be found, pgAdmin left the parameter out of the connection and libpq fell back to the defaults of the operating-system account running pgAdmin: ~/.pgpass, ~/.postgresql/postgresql.crt and postgresql.key, or PGPASSFILE, PGSSLCERT and PGSSLKEY. In server mode any user could therefore connect to a server with the service account's saved passwords or client certificate, and supplying only a copy of its public certificate was enough for libpq to pair it with the service account's private key. A pg_service.conf entry, or a maintenance database name read as a connection string by pg_dumpall, could bring the same files back for the utilities. The fix gives each of these parameters a value in server mode, the user's own file or otherwise a path that can never be opened, in the connection string, in the environment of the utilities and in the --dbname connection string that ranks above a service entry. Desktop mode is unchanged. This issue affects pgAdmin 4: before 9.19.

Contexto

Condiciones y alcance

Condiciones necesarias para que el fallo sea explotable
01
The service account's password file entry or client certificate is accepted by a server the attacker can reach“the service account must have a password file entry or client certificate that a server the attacker can reach accepts”
Vector CVSS 3.1

Desglose de métricas

Opción resaltada = valor del vector · izquierda = peor caso · CNA
Vector de ataqueAV:N
RedAdyacenteLocalFísica
ComplejidadAC:H
BajaAlta
PrivilegiosPR:L
NingunoBajosAltos
InteracciónUI:N
NingunaRequerida
AlcanceS:C
CambiadoSin cambio
ConfidencialidadC:H
AltoBajoNinguno
IntegridadI:H
AltoBajoNinguno
DisponibilidadA:N
AltoBajoNinguno
Versiones

Rangos afectados

Afectada Corregida
pgAdmin 4< 9.19
9.19
Remediación

Estado del parche por paquete

Paquete / productoEstadoCorregida enDesde divulgaciónÚltima versión
pgAdmin
Corregida 9.19 — —
Versiones corregidas9.19
Explotación

Arsenal público

Sin exploits, módulos ni PoC públicos conocidos a la fecha de verificación.

Registro
EscenarioAny authenticated user who can register a server. Attack Complexity is High: the service account must have a password file entry or client certificate that a server the attacker can reach accepts, a deployment condition the attacker does not control. Scope is Changed because the connection is made with the service account's database credentials, an identity the attacker was never granted; Confidentiality and Integrity are High on that database server. Availability is None.PostgreSQL
EscenarioSame reasoning as the CVSS 3.1 entry. AT:P for the service account's credential and an accepting server. VC:H because the service account's stored secret is used through pgAdmin; SC:H/SI:H for the database server reached with that identity.PostgreSQL
Referencias
Parchehttps://github.com/pgadmin-org/pgadmin4/commit/32db693198f28b78fe2af12a726b80a68eb78cb2
Reportehttps://github.com/pgadmin-org/pgadmin4/issues/10652

Las referencias externas se muestran para copiar: cve.llama.ec no lo redirige a otros sitios.