Skip to main content
VulnerabilityPublished Updated

CVE-2026-14666: PostgreSQL · Improper Preservation of Consistency Between Independent Representations of Shared State

Affects PostgreSQLSource CVE Database V5

0
Compare

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

Data as of 12 Nov 2026, 23:24 UTC

CVSS 3.1 base score
4.2Medium
How severe the flaw is on the 0–10 CVSS scale.
EPSS
0.2% chance of exploitation in 30 days – higher than 11% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
Patch
Available – fixed in 18.6, 17.11, 16.15 +3
CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:U/C:L/I:L/A:N

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 13 Aug 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 13 Nov 2026.

What to do

Upgrade to a fixed release listed under Affected software.

Affected software

ProductAffectedFixed in
PostgreSQLAffected
  • >=18 <18.6
Fixed in
  • 18.6
PostgreSQLAffected
  • >=17 <17.11
Fixed in
  • 17.11
PostgreSQLAffected
  • >=16 <16.15
Fixed in
  • 16.15
PostgreSQLAffected
  • >=15 <15.19
Fixed in
  • 15.19
PostgreSQLAffected
  • <14.24
Fixed in
  • 14.24
Postgresqlpostgresql/postgresqlpkg:deb/postgresql/postgresqlOther threatsAffected
  • <18.5
  • <17.11
  • <16.15
  • <15.19
  • <14.24
Fixed in
  • 18.5
  • 17.11
  • 16.15
  • 15.19
  • 14.24

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

AI-suggested

If you cannot patch yet, administrators should consider terminating sessions or otherwise invalidating cached plans after changes to role membership, role attributes, or database ownership to prevent use of stale row-level security policies.

Description

Incomplete tracking in PostgreSQL of changes to role membership, role attributes, and database ownership allows a query to continue using cached row-level security policies after those changes require a different policy, via plan reuse. Stale policies continue until some other event invalidates the cache or connection termination ends the session. This permits a user to complete reads and modifications that were recently permitted but now forbidden. An attacker must tailor an attack to a particular application's pattern of privilege removal and role-specific row security policies. Versions before PostgreSQL 18.6, 17.11, 16.15, 15.19, and 14.24 are affected.

References

Community reviews

Loading reviews…