llamaCVEVulnerability Intelligence
/
pgAdmin 4

CVE-2026-116250

pgAdmin 4: Files opened in a storage directory follow a symbolic link, hard link or FIFO planted after the containment check

Specific setups onlyParche disponiblerace condition
Descargar PNG JSON
CVSS 3.1
6.5
Media
CVSS:3.1/AV:L/AC:H/PR:L/UI:N/S:U/C:H/I:H/A:L Fuente: CNA
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-116250 divulgada · CVSS 6.5 (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 (the server-mode web application for PostgreSQL administration) is affected, including its servers.json import and export, file listing, and the Backup, Restore, and Import/Export Data features that call pg_dump, pg_dumpall, pg_restore, and psql. The flaw could let a symbolic link, hard link, or FIFO swapped into a user's storage directory redirect file reads, writes, or table loads to locations outside that directory, with the effects running as the pgAdmin operating-system account.

In pgAdmin 4 before 9.19, server mode on POSIX systems is affected; desktop mode is not. CVSS scores it 6.5 (medium), and the fix is in 9.19.

¿Qué significa?When pgAdmin opens a file in a storage directory, it checks that the file is inside that directory, then opens it later. An attacker who can write to the directory in the gap can swap in a symbolic link, hard link or FIFO, so the file opened is not the one that was checked. The fix in server mode on POSIX walks down from the storage directory to open the file.
¿Quién está afectado?Versions of pgAdmin 4 before 9.19 running in server mode on POSIX systems are affected. Desktop mode is not affected according to the fix description. To check, look at the pgAdmin 4 version in the About dialog and confirm whether pgAdmin runs in server mode or desktop mode.
¿Qué hacer?Upgrade to pgAdmin 4 9.19 or later. The fix was released on 29-10-2026.
fix-completeThe record marks the fix as partial, but the checked facts do not say what remains unfixed. Check the vendor advisory for the remaining gap.
Descripción original del registro (PostgreSQL)

In server mode pgAdmin 4 validates a path a user gives for a file in their storage directory with check_access_permission() and then opened it by name. Several places opened it with a plain open() or handed the path to a utility that opened it later: the servers.json export and import and the import file listing, and the files given to pg_dump, pg_dumpall, pg_restore and psql by Backup, Restore and Import/Export Data. A symbolic link swapped in at the file or at any parent directory between the check and the open redirected the operation outside the storage directory, so a file could be written, overwritten or read, or loaded into a table, as the operating-system account running pgAdmin. A hard link to an outside file, which O_NOFOLLOW does not detect, and a FIFO, which could hang a request, had the same effect. CVE-2026-86861 fixed this for the File Manager's save_file; these were the remaining paths. Exploitation requires creating such a link or FIFO inside the user's storage directory. pgAdmin offers no way to do so, and the per-user storage directories belong to the pgAdmin account, so this requires write access to the storage backend as a different operating-system user, for example a shared or network-mounted storage directory, and winning the race. The fix opens each file by walking down from the storage directory one component at a time with O_NOFOLLOW, accepting only a regular file with one link, and passes the utilities the open descriptor (/dev/fd/N) on Linux. Error messages no longer include the server path. This issue affects pgAdmin 4: before 9.19.

Contexto

Condiciones y alcance

Condiciones necesarias para que el fallo sea explotable
01
Server mode is in use (desktop mode is not affected per the fix description).“In server mode on POSIX the file is now opened by walking down from the storage directory”
El parche publicado es parcial: verifique el advisory del fabricante.
Vector CVSS 3.1

Desglose de métricas

Opción resaltada = valor del vector · izquierda = peor caso · CNA
Vector de ataqueAV:L
RedAdyacenteLocalFísica
ComplejidadAC:H
BajaAlta
PrivilegiosPR:L
NingunoBajosAltos
InteracciónUI:N
NingunaRequerida
AlcanceS:U
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
EscenarioThreat model: an operating-system user other than the pgAdmin service account who can write into a storage directory pgAdmin uses (a shared or network-mounted storage backend), and who also has, or works with, a pgAdmin account using it. An attacker with access to the host as the service account gains nothing from this flaw, so the Attack Vector is Local. Attack Complexity is High: the link must be planted and a race between the check and the open won. Confidentiality and Integrity are High because a file readable or writable by the pgAdmin account can be read (including loaded into a table) or overwritten; Availability is Low for a clobbered file or a hung request. Scope is Unchanged: the operations run with the authority pgAdmin already holds.PostgreSQL
EscenarioSame reasoning as the CVSS 3.1 entry. AT:P for the race and for the write access to the storage backend obtained outside pgAdmin. VC:H/VI:H/VA:L as above; no subsequent-system impact.PostgreSQL
Referencias
Parchehttps://github.com/pgadmin-org/pgadmin4/commit/99f5606e2ebc7c94c7acdbab877ce7de54bfc756
Parchehttps://github.com/pgadmin-org/pgadmin4/commit/c4321b9968342716f34bc5f10de6cac3c0567e68
Parchehttps://github.com/pgadmin-org/pgadmin4/commit/730d1e783c339ec696a1f77f2eee6f4b52cb6c37
Reportehttps://github.com/pgadmin-org/pgadmin4/issues/10647

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