Quick answers
- Is CVE-2026-116330 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-116330 being exploited in the wild.
- How severe is CVE-2026-116330?
- High severity, with a CVSS score of 8.8, published 12 November 2026.
- Which products and versions are affected?
- PostgreSQL 14.x before 14.25, 15.x before 15.20, 16.x before 16.16, 17.x before 17.12, 18.x before 18.7.
- Is there a fix for CVE-2026-116330?
- Yes: fixed in PostgreSQL 14.25, 15.20, 16.16, 17.12, 18.7. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
- How is CVE-2026-116330 attacked?
- It is attacked over the network, in a software library.
- Am I affected by CVE-2026-116330?
- Check whether you run PostgreSQL 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: PostgreSQL 14.25, 15.20, 16.16, 17.12, 18.7
Technical details
A command injection vulnerability exists in PostgreSQL's tar-format restore.sql generation within pg_dump due to insufficient validation of untrusted data from the source database. The vulnerability stems from a predictable restriction key mechanism that fails to properly sanitize input, allowing injection of arbitrary psql commands. An attacker with control over the PostgreSQL server can exploit this when a client restores from an untrusted backup.
Affected products
- PostgreSQL PostgreSQL 14.x before 14.25, 15.x before 15.20, 16.x before 16.16, 17.x before 17.12, 18.x before 18.7
Timeline
- 2026-11-12: disclosed