llamaCVEVulnerability Intelligence
/
pgAdmin 4

CVE-2026-116242

pgAdmin 4: SSH tunnels use the pgAdmin service account's own SSH identity

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-116242 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

pgAdmin 4 is affected, specifically its SSH tunnel feature when running in server mode. Before the fix, any user could configure a tunnel that silently used the SSH keys, SSH config, and agent of the operating-system account running pgAdmin, letting them log in to hosts that trusted that account without having credentials of their own.

Affects pgAdmin 4 before 9.19 in server mode, where all users share one operating-system account whose SSH identity has an unencrypted default key. Fixed in 9.19.

¿Qué significa?In server mode, SSH tunnels use the pgAdmin service account's own SSH identity, so an attacker can authenticate to other systems as that account. This gives high confidentiality and integrity access to the SSH host and the network reached through it.
¿Quién está afectado?pgAdmin 4 versions before 9.19 are affected. The bug needs server mode, where one operating-system account is shared by all users, and the service account must have an unencrypted default key, agent or configuration that a host the attacker can name accepts. Check your pgAdmin 4 version and whether your installation runs in server mode with such a service account key.
¿Qué hacer?Upgrade pgAdmin 4 to version 9.19 or later, which contains the fix. The advisory says details will be published with the 9.19 release notes.
Descripción original del registro (PostgreSQL)

pgAdmin 4 opens SSH tunnels with the sshtunnel library but gave it neither host_pkey_directories nor ssh_config_file, so it always loaded the unencrypted private keys in ~/.ssh of the operating-system account running pgAdmin, read that account's ~/.ssh/config (IdentityFile, User, HostName, ProxyCommand) for the tunnel host, and could use its ssh-agent. In server mode any user could therefore configure a tunnel to a host that accepts the service account's key, with no credentials of their own or with an identity file that did not exist in their storage, and reach it as that account. The fix makes tunnels in server mode use only the identity file or password the user configured: the service account's keys, configuration and agent are no longer used, and an identity file that cannot be found in the user's storage is reported instead of falling back to ~/.ssh. 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
pgAdmin 4 running in server mode, where one operating-system account is shared by all users“In server mode any user could therefore”
02
The service account has an unencrypted default key, agent or configuration that a host the attacker can name accepts“the service account must have an unencrypted default key, agent or configuration that a host the attacker can name 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 with an SSH tunnel. Attack Complexity is High: the service account must have an unencrypted default key, agent or configuration that a host the attacker can name accepts. Scope is Changed because the tunnel authenticates as the service account to another system, an identity the attacker was never granted; Confidentiality and Integrity are High for the access it gives. Availability is None.PostgreSQL
EscenarioSame reasoning as the CVSS 3.1 entry. AT:P for the service account's SSH identity and an accepting host. VC:H because the service account's key is used through pgAdmin; SC:H/SI:H for the SSH host and the network reached through it.PostgreSQL
Referencias
Parchehttps://github.com/pgadmin-org/pgadmin4/commit/d52fe4740eb1af89d940f2e412bd66a0a89f08bb
Reportehttps://github.com/pgadmin-org/pgadmin4/issues/10662

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