CVE-2026-14666: Improper Preservation of Consistency Between Independent Representations of Shared State in PostgreSQL
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.5, 17.11, 16.15, 15.19, and 14.24 are affected.
AI Analysis
Technical Summary
CVE-2026-14666 describes a vulnerability in PostgreSQL where incomplete tracking of changes to role membership, role attributes, and database ownership causes queries to continue using cached row-level security policies that are no longer valid. This occurs due to plan reuse with stale policies remaining effective until cache invalidation or session termination. The flaw allows users to perform reads and modifications that should have been forbidden after privilege changes. The vulnerability affects PostgreSQL versions before 18.5, 17.11, 16.15, 15.19, and 14.24. The CVSS 3.1 score is 4.2 (medium severity) with network attack vector, high attack complexity, low privileges required, no user interaction, and limited confidentiality and integrity impact.
Potential Impact
An attacker with low privileges can exploit this vulnerability to continue accessing or modifying data that should have been restricted due to recent changes in role membership or security policies. The impact is limited to confidentiality and integrity with no availability impact. Exploitation requires knowledge of the application's privilege removal patterns and row-level security policies. The vulnerability persists until the cache is invalidated or the session ends.
Mitigation Recommendations
Patch status is not yet confirmed — check the vendor advisory for current remediation guidance. Until a fix is available, 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.
CVE-2026-14666: Improper Preservation of Consistency Between Independent Representations of Shared State in PostgreSQL
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.5, 17.11, 16.15, 15.19, and 14.24 are affected.
CVSS v3.1
Score 4.2medium
Affected software
AI-Powered Analysis
Machine-generated threat intelligence
Technical Analysis
CVE-2026-14666 describes a vulnerability in PostgreSQL where incomplete tracking of changes to role membership, role attributes, and database ownership causes queries to continue using cached row-level security policies that are no longer valid. This occurs due to plan reuse with stale policies remaining effective until cache invalidation or session termination. The flaw allows users to perform reads and modifications that should have been forbidden after privilege changes. The vulnerability affects PostgreSQL versions before 18.5, 17.11, 16.15, 15.19, and 14.24. The CVSS 3.1 score is 4.2 (medium severity) with network attack vector, high attack complexity, low privileges required, no user interaction, and limited confidentiality and integrity impact.
Potential Impact
An attacker with low privileges can exploit this vulnerability to continue accessing or modifying data that should have been restricted due to recent changes in role membership or security policies. The impact is limited to confidentiality and integrity with no availability impact. Exploitation requires knowledge of the application's privilege removal patterns and row-level security policies. The vulnerability persists until the cache is invalidated or the session ends.
Mitigation Recommendations
Patch status is not yet confirmed — check the vendor advisory for current remediation guidance. Until a fix is available, 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.
Technical Details
- Data Version
- 5.2
- Assigner Short Name
- PostgreSQL
- Date Reserved
- 2026-07-03T20:28:10.229Z
- Cvss Version
- 3.1
- State
- PUBLISHED
- Remediation Level
- null
Threat ID: 6a7dc615bf8831d5393e5282
Added to database: 08/13/2026, 13:26:45 UTC
Last enriched: 08/13/2026, 14:01:49 UTC
Last updated: 08/13/2026, 18:04:19 UTC
Views: 3
Community Reviews
0 reviewsCrowdsource mitigation strategies, share intel context, and vote on the most helpful responses. Sign in to add your voice and help keep defenders ahead.
Want to contribute mitigation steps or threat intel context? Sign in or create an account to join the community discussion.
Actions
Updates to AI analysis require Pro Console access. Upgrade inside Console → Billing.
External Links
Need more coverage?
Upgrade to Pro Console for AI refresh and higher limits.
For incident response and remediation, OffSeq services can help resolve threats faster.
Latest Threats
Check if your credentials are on the dark web
Instant breach scanning across billions of leaked records. Free tier available.