Skip to main content
VulnerabilityPublished

CVE-2026-120142: PostgreSQL · Type Confusion

Affects PostgreSQLSource CVE Database V5

0
Compare

Not known to be exploited · CVSS 8.8 High : upgrade to 18.7 or 17.12 soon.

Data as of 12 Nov 2026, 14:36 UTC

CVSS 3.1 base score
8.8High
How severe the flaw is on the 0–10 CVSS scale.

Thin evidence

One scorer or none
CVSS scores by source
CNA (PostgreSQL)CVSS 3.18.8
Patch
Available – fixed in 18.7, 17.12
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 12 Nov 2026

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponized: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 12 Nov 2026.

What to do

Upgrade PostgreSQL to 18.7 or 17.12.

Affected software

ProductAffectedFixed in
PostgreSQLAffected
  • >=18 <18.7
Fixed in
  • 18.7
PostgreSQLAffected
  • >=17 <17.12
Fixed in
  • 17.12

AI-suggested

Upgrade affected PostgreSQL installations to version 17.12 or later, or 18.7 or later, where this vulnerability is fixed. No other mitigations or workarounds are indicated. Applying the official patches is the recommended and effective remediation.

Description

CVE-2026-120142 is a high-severity type confusion vulnerability in PostgreSQL affecting anonymous RECORD types. It allows an attacker who can create objects to execute arbitrary code with the privileges of the database operating system user. The flaw arises from row types with dropped attributes in identical positions but differing widths or alignments. This issue affects PostgreSQL major versions 17 and 18, specifically versions before 17.12 and 18.7. Versions prior to 17 are not vulnerable. The vulnerability has a CVSS score of 8.8, indicating a critical impact on confidentiality, integrity, and availability.

References

Community reviews

Loading reviews…