Skip to content

ApplicationsHigh 8.8Patch available

CVE-2026-116329

Type-confusion in PostgreSQL 18 lets table maintainers execute OS-level code.

How scary is it?

updated 20 Nov 2026
  • No

    Works without logging in1

    Needs a login: a basic user account (CVSS PR:L).

  • Yes

    Reachable over the network1

    Can be attacked remotely (CVSS AV:N).

  • None known

    Public exploit code is out

    None on record in Exploit-DB, Metasploit, Nuclei templates or PoC-in-GitHub.

  • None known

    Attacks seen in the wild1

    None reported that we know of. CISA's SSVC assessment says exploitation: none.

  • No

    On CISA's exploited list2

    Not in the catalog as of our last sync.

Scare-o-meter

Routine patch

Serious on paper, with no sign of attacks that we know of. Patch in your normal cycle.

  1. Low signal
  2. Routine patch
  3. Act this week
  4. Drop everything

Why: our alert rule found no exploitation evidence and no easy remote attack path in the data we hold. Read from the same rule that decides our alert emails.

Are you affected? only if all are true

  1. You run PostgreSQL in an affected version>= 18 and < 18.7

    The CVE record states no fixed release.

    As published in the CVE record. A version outside these ranges is not a statement that it is unaffected: vendors sometimes understate a range, and distribution builds with backported fixes keep the upstream number.

    See the affected products table · Source 1

  2. An attacker can reach it over the network

    CVSS attack vector: Network (AV:N). Reachable over the internet or any routable network.

    Source 1

  3. The attacker has a user account

    CVSS privileges required: Low (PR:L). The attacker needs basic user privileges.

    Source 1

Read from the CVE record: affected versions and the CVSS vector. It narrows things down. It does not prove you are safe.

What to do

  1. Per our analysisA patch is available

    The CVE record we hold states no fixed release number. See the advisories in the references.

    See the references

  2. Recommendation, AI-writtenUpgrade to PostgreSQL 18.7+ and restrict table maintainer privileges

    Written by a language model from the CVE record. It is not the vendor's wording: check it against the sources.

Steps marked AI were written by a language model, from the CVE record or from the linked news pages. They are not the vendor's wording: check them against the sources.

Major vulnerability. Affects widely used PostgreSQL; allows arbitrary OS-level code execution by a DB role, posing significant risk to many enterprises and hosted DB services.

CVSS
8.8Highscored by the publisher (CNA)
Exploited in the wild
Not knownnot in CISA KEV as of our last sync
EPSS
0.47%chance of exploitation in the next 30 daystop 59% of scored CVEsFIRST score of 21 Nov 2026
Fix
Patch availablesee the advisories in the references
Published
12 Nov 2026analysed here 14 Nov 2026

Summary

Impact

Local arbitrary code execution as the OS user running PostgreSQL by a table maintainer via crafted statistics import.

Triage

Exploitable
At runtime
Attack vector
network
Weakness
Can a WAF block it?
No. See why

Executive summary (AI-written)

CVE-2026-116329 represents a significant security vulnerability in PostgreSQL 18, classified with a CVSS score of 8.8, indicating a high severity level. This type-confusion flaw allows table maintainers to execute arbitrary operating system-level code, creating a critical risk for any organization utilizing this database system. Given PostgreSQL's broad adoption, especially among enterprises and hosted services, the potential impact of this vulnerability is extensive, making it imperative for organizations to take immediate action to safeguard their systems. To mitigate the associated risks, organizations must promptly upgrade to PostgreSQL version 18.7 or later, which addresses this vulnerability. Additionally, it is crucial to restrict the privileges of table maintainers to minimize exposure. Failure to take these steps could lead to unauthorized access, data breaches, and substantial operational disruptions, thus jeopardizing both the integrity and availability of enterprise data assets.

Technical analysis (AI-written)

CVE-2026-116329 is a type-confusion vulnerability found in PostgreSQL 18 that affects all versions prior to 18.7. This vulnerability enables a table maintainer, through a crafted statistics import, to execute arbitrary OS-level commands with the privileges of the PostgreSQL user. The exploit can be initiated locally, making it particularly dangerous for environments where database roles are misconfigured or overly permissive. The CVSS score of 8.8 suggests a high risk level, warranting immediate attention from security teams. Attack vectors for this vulnerability primarily involve crafted statistical imports that leverage type-confusion to gain unauthorized code execution capabilities. Since table maintainers generally have more access than a standard user, an attacker successfully exploiting this vulnerability could perform actions that compromise the entire database instance and the underlying operating system. The complexity of exploitation is relatively low, particularly in mismanaged database environments where permissions can lead to escalated privileges. Mitigation strategies include immediate upgrades to PostgreSQL version 18.7, which contains the relevant patches for this vulnerability. Organizations should also evaluate and potentially restrict the privileges assigned to table maintainers, ensuring that these roles have only the minimum necessary permissions. Implementing rigorous access control policies and regular audits of database permissions can help reduce the likelihood of such vulnerabilities being exploited in the future. Additionally, organizations should monitor PostgreSQL security advisories for any further developments or related vulnerabilities. It is also recommended to conduct thorough testing of the patched version in a staging environment before deploying to production databases to ensure compatibility and performance integrity. System administrators and security professionals should maintain a proactive stance towards vulnerability management, including timely updates and adherence to security best practices in database management.

The summary, impact and action text on this page are written by our AI analysis pipeline, or taken from the NVD description when a CVE was imported from NVD. They are not the vendor's wording: check them against the sources.

Affected products

ProductAffected versions
PostgreSQL>= 18 and < 18.7Vendor says fixed in: not stated

As published in the CVE Program record. A version outside these ranges is not a statement that it is unaffected — vendors sometimes understate a range, and distribution-backported builds carry upstream numbers that do not reflect what was patched into them.

Products named in our analysis

  • PostgreSQL 18 (versions before 18.7)

Fix and mitigation

Action required

Immediate action required

WAF and other mitigations

Can a WAF block it? No. The vulnerability requires a table maintainer to execute OS-level code, implying local access or privileges are needed rather than remote HTTP requests. A web application firewall only sees HTTP traffic, so it is not on this attack's path.

Also consider: patch

Based on an AI reading of the CVE description, and no vendor rule found yet. We check Cloudflare, AWS, Google Cloud Armor and Azure; for Akamai, Imperva, Fastly, F5, ask your vendor.

Remediation steps (AI-written)

Step-by-step remediation is generated for accounts on the Max plan, for CVEs that match a technology in their stack. Add this technology to your stack to see the fix checklist.

Exploitation evidence

CISA KEV catalog
Not listed as of our last sync.
Public exploit code
None on record in Exploit-DB, Metasploit, Nuclei templates or PoC-in-GitHub.
CISA SSVC
exploitation none, automatable no, technical impact totalAssessed by CISA 13 Nov 2026 (SSVC 2.0.3). Exploitation is none, poc (public proof of concept) or active.

Timeline

  1. 12 Nov 2026Published
  2. 13 Nov 2026CISA SSVC assessment: exploitation nonesame day later
  3. 14 Nov 2026CVE record last updated1 day later
  4. 14 Nov 2026Analysed by vulneraibility.com1 day later

Common questions

Is CVE-2026-116329 being exploited?

Not confirmed. CVE-2026-116329 does not appear in CISA's Known Exploited Vulnerabilities catalog, which records only exploitation that has been observed and reported publicly. That is evidence of absence of a report, not evidence the flaw is unattacked. EPSS currently estimates a 0.47% probability of exploitation in the next 30 days.

How severe is CVE-2026-116329?

CVE-2026-116329 is rated High with a CVSS score of 8.8. Severity describes how bad exploitation would be, not how likely it is: pair it with exploitation evidence before deciding what to patch first.

Is there a patch for CVE-2026-116329?

Yes. A fix has been recorded for CVE-2026-116329. The vendor advisory is the authority on the exact fixed version — apply it from there rather than from a summary.

What does CVE-2026-116329 affect?

CVE-2026-116329 affects PostgreSQL 18 (versions before 18.7). Confirm the exact affected versions against the vendor advisory before deciding you are exposed.

What should I do about CVE-2026-116329?

Upgrade to PostgreSQL 18.7+ and restrict table maintainer privileges

Exploitation status reflects CISA's KEV catalog as we last synced it. Check the catalog directly.

References

NVDCVE.orgCVE DetailsSource

1 reference in the CVE record, grouped by the tags the record gives them.

Other links (1)

Where the data on this page comes from

Summary, impact and triage tags: written by our AI analysis pipeline from the sources above. Check them against the sources.

Similar CVEs

Get CVEs like this by email. Join the free digest: the CVEs we flag as major, all CVSS 8.0 or higher, in up to three emails a day (sent at 05:00, 11:00 and 15:00 UTC). Matching alerts to the products you run needs an account, and accounts are invite-only during the beta.