Quick answers
- Is CVE-2026-116243 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-116243 being exploited in the wild.
- How severe is CVE-2026-116243?
- High severity, with a CVSS score of 7.5, published 30 October 2026.
- Which products and versions are affected?
- Pgadmin 4 before 9.19.
- Is there a fix for CVE-2026-116243?
- Yes: fixed in pgAdmin 4 9.19. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
- How is CVE-2026-116243 attacked?
- It is attacked over the network, in a web application.
- Am I affected by CVE-2026-116243?
- Check whether you run Pgadmin 4 at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.
How to fix
- Fixed in: pgAdmin 4 9.19
Technical details
pgAdmin 4 validates binary paths only against the per-user STORAGE_DIR but not against SHARED_STORAGE directories, allowing authenticated users to upload executable files to shared storage and redirect pgAdmin to execute them via pg_dump, pg_restore, pg_dumpall, or psql. The vulnerability is exploitable on Windows server mode and systems where arbitrary filenames are executable. The fix adds comprehensive path validation including symlink resolution, ".." collapsing, case-insensitive comparison, and NUL character rejection.
Affected products
- pgAdmin pgAdmin 4 before 9.19
Timeline
- 2026-10-30: advisory