Skip to main content
VulnerabilityPublished

CVE-2026-120144: PostgreSQL · Type Confusion

Affects PostgreSQLSource CVE Database V5

0
Compare

Not known to be exploited · CVSS 8.8 High : upgrade to 18.7 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
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.

Affected software

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

AI-suggested

Upgrade affected PostgreSQL installations to version 18.7 or later to remediate this vulnerability. No other mitigations are indicated by the vendor advisory. Versions prior to 18.0 are not affected and do not require action for this issue.

Description

CVE-2026-120144 is a high-severity type confusion vulnerability in PostgreSQL versions 18.0 up to but not including 18.7. It arises from incomplete invalidation of the PostgreSQL type cache, allowing an object creator to execute arbitrary code as the operating system user running the database by exploiting a composite type change during cache population. Versions prior to 18.0 are not affected. The issue is fixed in PostgreSQL 18.7.

References

Community reviews

Loading reviews…