llamaCVEVulnerability Intelligence
/
pgAdmin 4

CVE-2026-116249

pgAdmin 4: Connection file paths and parameter keys escape the user's storage directory

Specific setups onlyParche disponiblepath traversal
Descargar PNG JSON
CVSS 3.1
8.4
Alta
CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:C/C:H/I:H/A:L 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ón20 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
20 nov 26
30 oct 26
4 nov 26
10 nov 26
15 nov 26
20 nov 26
FechaFaseEventoDetalle
Divulgación Publicada CVE-2026-116249 divulgada · CVSS 8.4 (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

pgAdmin 4 (server mode) is affected: a crafted file path or connection parameter in a server definition could make it read another user's saved passwords, certificates, or SSH keys, or create or append files as the account running pgAdmin. The impact is unauthorized access to other users' credentials and arbitrary file writes outside the storage directory.

Only affects pgAdmin 4 before 9.19, and only where the referenced file is kept in the user's storage directory. Fixed in pgAdmin 4 9.19.

¿Qué significa?Connection file paths and parameter keys can point outside the storage directory that pgAdmin 4 is meant to confine them to. The advisory says this happens when a victim keeps such a file in their storage directory.
¿Quién está afectado?Versions of pgAdmin 4 before 9.19 are affected. The advisory's condition is that the referenced file is kept in the user's storage directory. To check a version, open the About dialog in pgAdmin 4 (Help menu) and read the version number.
¿Qué hacer?Upgrade to pgAdmin 4 9.19 or later. The fix is in 9.19, released on 29-10-2026.
Descripción original del registro (PostgreSQL)

In server mode pgAdmin 4 resolves a server's password file, SSL certificate, key, CRL and SSH tunnel identity file relative to the user's storage directory, but get_complete_file_path() only stripped leading slashes before joining the two. A path such as "../<another user>/.pgpass", set through the server dialog, the REST API or a servers.json import, therefore named another user's file, and connecting used that user's saved passwords, client certificate or SSH key. The sslkeylogfile connection parameter was passed to libpq unchanged, so a path outside storage let libpq create or append a file as the account running pgAdmin. make_conninfo() also quoted connection parameter values but not their names, so a crafted parameter name could smuggle additional keyword=value pairs past these checks. The fix requires the resolved path, with symbolic links followed, to stay inside the user's storage directory or the named shared storage directory, confines sslkeylogfile the same way, and accepts only exact libpq keywords as connection parameter names. A refused path or keyword is reported instead of letting libpq fall back to a default. This issue affects pgAdmin 4: before 9.19.

Contexto

Condiciones y alcance

Condiciones necesarias para que el fallo sea explotable
01
The victim keeps the referenced file in their storage directory“the victim must keep such a file in their storage directory”
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:L
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 victim must keep such a file in their storage directory, and the attacker must know its name and a host and role it is accepted for. Scope is Changed because the connection is made to a database server with another user's credentials, an authority the attacker was never given; Confidentiality and Integrity are High for that access. Availability is Low for the file sslkeylogfile can create or append to outside storage.PostgreSQL
EscenarioSame reasoning as the CVSS 3.1 entry. AT:P for the victim's file and its name, which the attacker does not control. VC:H for the credential read through pgAdmin, VI:L/VA:L for the sslkeylogfile write; SC:H/SI:H for the database server reached with the other user's identity.PostgreSQL
Referencias
Parchehttps://github.com/pgadmin-org/pgadmin4/commit/2afe505ef4a31591796449d54ab1604355ff06c2
Reportehttps://github.com/pgadmin-org/pgadmin4/issues/10650

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