Skip to main content
VulnerabilityPublished

CVE-2026-16237: PostgreSQL · Improper Protection of Alternate Path

Affects PostgreSQLSource CVE Database V5

0
Compare

Not known to be exploited · CVSS 5.4 Medium · fixed in 18.7 : update PostgreSQL when convenient.

Data as of 12 Nov 2026, 14:35 UTC

CVSS 3.1 base score
5.4Medium
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.15.4
Patch
Available – fixed in 18.7, 17.12, 16.16 +2
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:L/A:N

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 to a fixed release listed under Affected software.

Affected software

ProductAffectedFixed in
PostgreSQLAffected
  • >=18 <18.7
Fixed in
  • 18.7
PostgreSQLAffected
  • >=17 <17.12
Fixed in
  • 17.12
PostgreSQLAffected
  • >=16 <16.16
Fixed in
  • 16.16
PostgreSQLAffected
  • >=15 <15.20
Fixed in
  • 15.20
PostgreSQLAffected
  • <14.25
Fixed in
  • 14.25

AI-suggested

Upgrade PostgreSQL to version 18.7, 17.12, 16.16, 15.20, or 14.25 or later, where this vulnerability is fixed. Applying these official fixes will prevent exploitation of this issue.

Description

CVE-2026-16237 is a vulnerability in PostgreSQL affecting versions prior to 18.7, 17.12, 16.16, 15.20, and 14.25. It involves improper protection of alternate paths in the INSERT ... ON CONFLICT operation on auto-updatable views. An attacker with INSERT and UPDATE privileges on the view can bypass the view's WHERE condition and read or modify every row in the base table. This issue affects both regular and security_barrier views.

References

Community reviews

Loading reviews…