llamaCVEVulnerability Intelligence
/
pgAdmin 4

CVE-2026-116240

pgAdmin 4: File Manager and storage-path tools act on a different path from the one checked

Specific setups onlyParche disponiblepath traversal
Descargar PNG JSON
CVSS 3.1
6.5
Media
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N 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
Remediar en la ventana regular de mantenimiento
Sin explotación conocida, no automatizable e impacto técnico parcial. 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-116240 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 in server mode is affected, specifically its File Manager and storage-path tools (Query Tool file opening, Import/Export, Backup, Restore, and the Google client secret handling). Depending on the operating system and deployment, an authenticated user could read, write, list, delete, or move files outside their intended storage directory, including files of other users. Desktop mode is not affected.

Affects pgAdmin 4 versions before 9.19. Cross-user file access applies only where one user's storage directory name is a prefix of another's, and writing outside storage only on Windows server mode. Fixed in 9.19.

¿Qué significa?The File Manager and storage-path tools check one file path but then act on a different one. This lets a user reach files beyond the location that was checked. Per the facts, it can read any file the pgAdmin account can read through the Query Tool's file open, and list any directory on the host.
¿Quién está afectado?pgAdmin 4 versions before 9.19 are affected. Reading and listing reach every deployment, while reading, deleting or moving other users' files needs a deployment where one user's storage directory name is a prefix of another's, and writing outside storage needs Windows server mode. To check, look at the version shown in pgAdmin's About dialog and at the storage directory names in use on the server.
¿Qué hacer?Upgrade pgAdmin 4 to version 9.19 or later. The facts do not list a separate workaround.
Descripción original del registro (PostgreSQL)

In server mode pgAdmin 4 validates a path into the user's storage directory with check_access_permission(), which builds the absolute path with get_abs_path(). Several callers then acted on a path they built differently, so the path checked and the path used could name different files: - Opening a file in the Query Tool, the Google client secret and, on Windows, Import/Export Data, Backup, Restore and saving a file joined the path to the storage directory after stripping leading slashes and backslashes. On POSIX a path checked as a name inside storage could become an absolute path once stripped, so any file the pgAdmin account can read could be opened; on Windows a path naming a drive discarded the storage directory, so these could read, or write, outside it. - Listing a folder decoded the path a second time after the check, so a folder named like an encoded "..", which a user can create, listed any directory on the host. - Download, delete, rename and the file-exists check appended the path to the storage directory without a separator, so in a deployment where one user's storage directory name is a prefix of another's, another user's files could be read, deleted or moved; download also checked the path appended to itself. - Creating a folder could create one in another user's directory. The fix makes check_access_permission() return the path it checked and every caller act on that path, decodes folder paths once, and opens, deletes and renames files relative to directories opened from the storage directory without following symbolic links. Desktop mode is not affected. This issue affects pgAdmin 4: before 9.19.

Contexto

Condiciones y alcance

Condiciones necesarias para que el fallo sea explotable
01
For reading, deleting or moving another user's files: one user's storage directory name is a prefix of another's“a deployment where one user's storage directory name is a prefix of another's”
02
For writing outside storage: Windows server mode“the write outside storage is limited to Windows server mode”
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:L
BajaAlta
PrivilegiosPR:L
NingunoBajosAltos
InteracciónUI:N
NingunaRequerida
AlcanceS:U
CambiadoSin cambio
ConfidencialidadC:H
AltoBajoNinguno
IntegridadI:N
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
EscenarioScored for the worst variant, which needs only an authenticated user in server mode: reading any file the pgAdmin account can read through the Query Tool's file open, and listing any directory. Attack Complexity is Low. Confidentiality is High because that includes pgAdmin's own configuration and database. Integrity is None for this variant; the read, delete and rename of another user's files need a deployment where one user's storage directory name is a prefix of another's, and the write outside storage is limited to Windows server mode. Scope is Unchanged: the access is with the authority of the pgAdmin account.PostgreSQL
EscenarioSame reasoning as the CVSS 3.1 entry. AT:N for the any-file read, which needs no deployment condition. VC:H; no subsequent-system impact is claimed.PostgreSQL
Referencias
Parchehttps://github.com/pgadmin-org/pgadmin4/commit/ad6c028cff625a095676065767c7b80219205d28
Reportehttps://github.com/pgadmin-org/pgadmin4/issues/10674

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