CVE-2026-14666: PostgreSQL row security caching disregards role modifications
CVE-2026-14666 key facts
- CISA KEV
- Not listed (catalogue checked )
- Highest advisory rating
- Critical
- CVSS base score
- 4.2 (Red Hat)
- CVSS vector
CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:U/C:L/I:L/A:N· base score 4.2, scored by PostgreSQLAttack vector: network. Attack complexity: high. Privileges required: low. User interaction: none. Scope: unchanged. Confidentiality impact: low. Integrity impact: low. Availability impact: none.- Weakness
- CWE-1250 Improper Preservation of Consistency Between Independent Representations of Shared State
- EPSS
- 0.21% chance of exploitation in the next 30 days (11th percentile). FIRST EPSS, .
- CISA SSVC
- Exploitation: none observed. Automatable: no. Technical impact: partial. CISA, .
- Assigned by
- PostgreSQL (CNA)
- CVE record published
- Listed by VulniPulse
- Record changed
Ratings, versions and fixes are quoted from the vendor advisories that cover only CVE-2026-14666; each belongs to its advisory, not to every product listed. How records are collected and checked.
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.
Text from the CVE.org record (PostgreSQL).
How do I fix CVE-2026-14666?
- To mitigate this issue, ensure that all active PostgreSQL sessions are terminated or restarted after any changes to role membership, role attributes, or database ownership that affect row-level security policies. This action forces the invalidation of stale cached security policies, preventing unauthorized data access. Note that terminating sessions will disrupt active user connections. (Red Hat)
Vendor advisories for CVE-2026-14666
Red Hat
1 advisory- Advisory severityMedium4.2
Medium [CVE-2026-14666] Row security caching disregards role modifications leading to unauthorized data access
CVE-2026-14666Source published Source updated
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. Active sessions may continue using cached, outdated security policies, enabling unauthorized read or write access to data.…
- Affected products in this advisory
- Red Hat Enterprise Linux 10
- Red Hat Enterprise Linux 8
- Red Hat Enterprise Linux 9
- Self-service automation portal 2
2 more entries in the full advisory.
- Source-reported affected versions
- < 18.5
- < 17.11
- < 16.15
- < 15.19
1 more entries in the full advisory.
- Source-reported fixed versions
- No fixed-version detail extracted. This does not mean no fix exists.
- Mitigation guidance
- To mitigate this issue, ensure that all active PostgreSQL sessions are terminated or restarted after any changes to role membership, role attributes, or database ownership that affect row-level security policies. This action forces the invalidation of stale cached security policies, preventing unauthorized data access. Note that terminating sessions will disrupt active user connections.
Splunk
1 advisory- Advisory severityCritical
Critical [CVE-2025-61726 +79] Third-Party Package Updates in Splunk Enterprise - November 2026
SVD-2026-1104Source published
This bulletin covers 80 CVEs. The products, versions, score and guidance below describe the bulletin; check its source for applicability to this specific CVE.
Splunk remedied common vulnerabilities and exposures (CVEs) in third-party packages in Splunk Enterprise versions 10.6.1, 10.4.5, 10.2.9, 10.0.12, and 9.4.17 or higher. Affected products named by the advisory: Splunk Enterprise 10.6; Splunk Enterprise 10.4; Splunk Enterprise 10.2; Splunk Enterprise 10.0; and 1 more. Affected products named by the advisory: Splunk Enterprise 9.4.
- Affected products in this advisory
- Splunk Enterprise 10.6
- Splunk Enterprise 10.4
- Splunk Enterprise 10.2
- Splunk Enterprise 10.0
1 more entries in the full advisory.
- Source-reported affected versions
- Splunk Enterprise 10.6.0.5
- Splunk Enterprise 10.4.0 to 10.4.4
- Splunk Enterprise 10.2.0 to 10.2.8
- Splunk Enterprise 10.0.0 to 10.0.11
1 more entries in the full advisory.
- Source-reported fixed versions
- Splunk Enterprise 10.6.1
- Splunk Enterprise 10.4.5
- Splunk Enterprise 10.2.9
- Splunk Enterprise 10.0.12
1 more entries in the full advisory.
- Mitigation guidance
- Upgrade Splunk Enterprise to an applicable fixed release identified in the OSS entries below. The listed versions contain different component updates; the details specify which releases contain each fix.
References
Timeline
- CVE record published
- CVE record last updated
- First vendor advisory listed by VulniPulse
More Red Hat advisories
CVE-2026-111497Oct 22, 2026Out-of-Bounds Write in Google Brotli DecoderCVE-2026-109619Oct 21, 2026fatal error handling retains stale request state leading to use-after-freeCVE-2026-109618Oct 21, 2026OOM bailout during request parsing leads to memory corruption and RCECVE-2026-125350Nov 10, 2026Use after free in XMLCVE-2026-114713Nov 8, 2026Command injection via unescaped message tagCVE-2026-90436Nov 6, 2026Remote code execution via insecure deserialization of SOAP fault messages
Get an email when Red Hat publishes the next one.
See Red Hat's last 90 days first. Live alerts for one product are free for life; every vendor is US$15 a month after a free month.