Skip to main content
Mallory
HighVulnerability

CVE-2026-116330: PostgreSQL pg_dump tar-format restoration command injection

Published Nov 12, 2026 · Updated today
Trending this weekNot trendingOutside this week’s top 100
Mention activity · 30 days19 mentions · peak 6 in a dayToday
CVSS8.8High · v3.1
EPSS0.37%32nd percentile
CISA KEVNoNot listed
In the wildNoneNo exploitation reported
IdentifiersCVE-2026-116330CWE-829 · Inclusion of Functionality from…

CVE-2026-116330 is an untrusted-data inclusion vulnerability in the restoration script generated by PostgreSQL pg_dump for tar-format archives. A predictable restriction key allows a compromised origin server to inject psql commands that bypass restoration-script restrictions, resulting in arbitrary code execution as the client operating-system account running psql. The vulnerability is a gap in the fix for CVE-2025-8714. It affects PostgreSQL 18 before 18.7, 17 before 17.12, 16 before 16.16, 15 before 15.20, and 14 before 14.25.

Do you run this?See affected versions in your environment and whether adversaries are exploiting this vulnerability against assets like yours.
Check your exposure
Analyst brief

Impact, mitigation & remediation

What it means and what to do now: patch path, interim mitigations, and the assume-compromise checklist.

Impact

What an attacker gets, and what they’ve been doing with it.

Successful exploitation compromises the restoration client, rather than only the destination database. Arbitrary code runs with the privileges of the operating-system account executing psql, potentially allowing access to sensitive files and credentials, modification or deletion of accessible data, and disruption of client-side services. The extent of compromise depends on that account's permissions.

Mitigation

If you can’t patch tonight, do this now.

Until patched, avoid executing tar-format restoration scripts originating from untrusted or potentially compromised PostgreSQL servers. If restoration cannot be deferred, use an isolated environment and a minimally privileged operating-system account to reduce the consequences of client-side code execution; these measures do not correct the vulnerability.

Remediation

Patch, then assume compromise.

Upgrade PostgreSQL, including the pg_dump client utility used to generate tar-format archives, to version 18.7, 17.12, 16.16, 15.20, or 14.25, or a later fixed release in the corresponding branch. The fix makes the restriction and unrestriction commands functional in tar-format restoration output. Regenerate affected archives with the corrected utility before using their embedded restoration scripts.

Public exploits

Exploits

No public exploits tracked yet. Mallory keeps watching.

View more in app →
No public exploit code observed for this vulnerability. Mallory keeps watching.
FAQ

Frequently asked questions

Is CVE-2026-116330 exploited in the wild?
As of Nov 17, 2026, Mallory has no reports of CVE-2026-116330 being exploited in the wild. It is not listed in CISA KEV.
Is there a public exploit for CVE-2026-116330?
As of Nov 17, 2026, Mallory has found no public exploit for CVE-2026-116330.
Is there a patch for CVE-2026-116330?
Upgrade PostgreSQL, including the pg_dump client utility used to generate tar-format archives, to version 18.7, 17.12, 16.16, 15.20, or 14.25, or a later fixed release in the corresponding branch. The fix makes the restriction and unrestriction commands functional in tar-format restoration output.
How severe is CVE-2026-116330?
CVE-2026-116330 has a CVSS v3.1 score of 8.8 (High) and an EPSS score of 0.37% (32nd percentile) as of Nov 17, 2026.
Activity feed

Recent activity

19 sources tracked across advisories, community write-ups, and news. New activity surfaces here as Mallory finds it.

View more in app →
+9 more in the timeline. Sign up to see them
Do you run this?See affected versions in your environment and whether adversaries are exploiting this vulnerability against assets like yours.
Check your exposure
Mallory platform

The version that knows your environment.

This page is what’s public. Mallory adds the parts that aren’t: which of your assets are affected, which adversaries are exploiting it right now, and which detections to deploy tonight.
Exposure mappingQuery your assets running an affected version, and investigate the blast radius.
Threat actor evidenceEvery report linking this CVE to a named adversary.
Associated malwareMalware families linked to this CVE, with evidence and IOCs.
Detection signaturesYARA, Sigma, Snort, and vendor rules, auto-deployed to your SIEM.
Vendor-by-vendor mappingCross-references every affected SKU, including bundled OEM variants.
Social activity2Community discussion across Reddit, Mastodon, and other social sources.