llamaCVEVulnerability Intelligence
/
pgAdmin 4

CVE-2026-116252

pgAdmin 4: Materialized view refresh redirects its connection through a crafted database name

Specific setups onlyParche disponibleargument injection
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-116252 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 web-based administration tool for PostgreSQL databases, is affected in its materialized view refresh feature. A user with permission to create databases could craft a database name that redirects the connection to an attacker-chosen host, leaking the saved server password and letting the pgAdmin host connect to arbitrary addresses.

Affects pgAdmin 4 before 9.19 when a shared server lets a CREATEDB role create a database with a crafted name that another user refreshes a materialized view in. CVSS scores it 6.5 (medium). Fixed in 9.19.

¿Qué significa?A crafted database name can redirect the pgAdmin 4 connection used when refreshing a materialized view. The refresh then runs through a connection other than the one intended.
¿Quién está afectado?All pgAdmin 4 versions before 9.19 are in the affected range. The bug needs a database role with CREATEDB on a server that other pgAdmin users connect to, and a user who refreshes a materialized view in the database with the crafted name. Check the installed pgAdmin 4 version against 9.19 to see which release is in use.
¿Qué hacer?Upgrade pgAdmin 4 to version 9.19 or later, which contains the fix.
Descripción original del registro (PostgreSQL)

pgAdmin 4's materialized view refresh passed the target database's name to psql's --dbname argument unchanged. libpq treats a --dbname value containing "=" (or a postgresql:// URI) as a full connection string, whose keywords override the host, port and other settings pgAdmin had supplied. A database whose name is such a string, which any role with CREATEDB can create, therefore redirected the psql process pgAdmin starts for the refresh to a host and port of the creator's choosing, and the connecting user's saved server password was presented to that endpoint. It also let the pgAdmin host be made to open connections to arbitrary addresses. The same weakness was fixed for Backup, Restore, Maintenance and Import/Export Data in earlier releases (CVE-2026-86862); the materialized view refresh was the remaining caller. The fix routes the name through the same database_conninfo() helper, so libpq treats it strictly as a database name. This issue affects pgAdmin 4: before 9.19.

Contexto

Condiciones y alcance

Condiciones necesarias para que el fallo sea explotable
01
The attacker holds a database role with CREATEDB on a server that another pgAdmin user connects to.“The attacker needs a database role with CREATEDB on a server another pgAdmin user connects to”
02
The pgAdmin user refreshes a materialized view in the database whose name is the crafted connection string.“that user must refresh a materialized view in that database”
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
EscenarioSame threat model and vector as CVE-2026-86862, of which this is the remaining caller. The attacker needs a database role with CREATEDB on a server another pgAdmin user connects to, and that user must refresh a materialized view in that database; no other precondition applies, so Attack Complexity is Low. Confidentiality is High because the victim's saved server password is sent to the attacker's endpoint. Integrity and Availability are None. Scope is Unchanged, as for CVE-2026-86862: the credential is captured from the user's own connection rather than a different authority being exercised.PostgreSQL
EscenarioSame reasoning as the CVSS 3.1 entry. AT:N because no condition outside the attacker's control is needed beyond the victim using the feature. VC:H for the captured password; no subsequent-system impact is claimed from the flaw itself.PostgreSQL
Referencias
Parchehttps://github.com/pgadmin-org/pgadmin4/commit/a1a43e8c28cf10cec73df0c476905562d19af483
Reportehttps://github.com/pgadmin-org/pgadmin4/issues/10645

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