CVE-2026-14666 Vulnerability Analysis & Exploit Details

CVE-2026-14666
Vulnerability Scoring

4.2

/10

Medium Risk

The vulnerability CVE-2026-14666 could compromise system integrity but typically requires user interaction to be exploited.

Attack Complexity Details

Attack Complexity: High
Exploits require significant effort and special conditions.
Attack Vector: Network
Vulnerability is exploitable over a network without physical access.
Privileges Required: Low
Some privileges are necessary to exploit the vulnerability.
Scope: Unchanged
Exploit remains within the originally vulnerable component.
User Interaction: None
No user interaction is necessary for exploitation.

CVE-2026-14666 Details

Status: Modified

Last updated: 🕚 29 Aug 2026, 23:17 UTC
Originally published on: 🕐 13 Aug 2026, 13:17 UTC

Time between publication and last update: 16 days

CVSS Release: version 3

CVSS3 Source

f86ef6dc-4d3a-42ad-8f28-e6d5547a5007

CVSS3 Type

Secondary

CVSS3 Vector

CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:U/C:L/I:L/A:N

CVE-2026-14666 Vulnerability Summary

CVE-2026-14666: 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.

Assessing the Risk of CVE-2026-14666

Access Complexity Graph

The exploitability of CVE-2026-14666 depends on two key factors: attack complexity (the level of effort required to execute an exploit) and privileges required (the access level an attacker needs).

Exploitability Analysis for CVE-2026-14666

This vulnerability, CVE-2026-14666, requires a high level of attack complexity and low privileges, making it difficult but not impossible to exploit. Organizations should ensure robust security configurations to mitigate risks.

Understanding AC and PR

A lower complexity and fewer privilege requirements make exploitation easier. Security teams should evaluate these aspects to determine the urgency of mitigation strategies, such as patch management and access control policies.

Attack Complexity (AC) measures the difficulty in executing an exploit. A high AC means that specific conditions must be met, making an attack more challenging, while a low AC means the vulnerability can be exploited with minimal effort.

Privileges Required (PR) determine the level of system access necessary for an attack. Vulnerabilities requiring no privileges are more accessible to attackers, whereas high privilege requirements limit exploitation to authorized users with elevated access.

CVSS Score Breakdown Chart

Above is the CVSS Sub-score Breakdown for CVE-2026-14666, illustrating how Base, Impact, and Exploitability factors combine to form the overall severity rating. A higher sub-score typically indicates a more severe or easier-to-exploit vulnerability.

CIA Impact Analysis

Below is the Impact Analysis for CVE-2026-14666, showing how Confidentiality, Integrity, and Availability might be affected if the vulnerability is exploited. Higher values usually signal greater potential damage.

Confidentiality: Low
CVE-2026-14666 could lead to minor leaks of non-critical information without major privacy breaches.
Integrity: Low
Exploiting CVE-2026-14666 may cause minor changes to data without severely impacting its accuracy.
Availability: None
CVE-2026-14666 does not impact system availability.

CVE-2026-14666 References

External References

https://www.postgresql.org/support/security/CVE-2026-14666/

CWE Common Weakness Enumeration

CWE-1250

Vulnerable Configurations

cpe:2.3:a:postgresql:postgresql:14.0:*:*:*:*:*:*:*
cpe:2.3:a:postgresql:postgresql:14.0:*:*:*:*:*:*:*
cpe:2.3:a:postgresql:postgresql:14.1:*:*:*:*:*:*:*
cpe:2.3:a:postgresql:postgresql:14.1:*:*:*:*:*:*:*
cpe:2.3:a:postgresql:postgresql:14.2:*:*:*:*:*:*:*
cpe:2.3:a:postgresql:postgresql:14.2:*:*:*:*:*:*:*
cpe:2.3:a:postgresql:postgresql:14.3:*:*:*:*:*:*:*
cpe:2.3:a:postgresql:postgresql:14.3:*:*:*:*:*:*:*
cpe:2.3:a:postgresql:postgresql:14.4:*:*:*:*:*:*:*
cpe:2.3:a:postgresql:postgresql:14.4:*:*:*:*:*:*:*
cpe:2.3:a:postgresql:postgresql:14.5:*:*:*:*:*:*:*
cpe:2.3:a:postgresql:postgresql:14.5:*:*:*:*:*:*:*
cpe:2.3:a:postgresql:postgresql:14.6:*:*:*:*:*:*:*
cpe:2.3:a:postgresql:postgresql:14.6:*:*:*:*:*:*:*
cpe:2.3:a:postgresql:postgresql:14.7:*:*:*:*:*:*:*
cpe:2.3:a:postgresql:postgresql:14.7:*:*:*:*:*:*:*
cpe:2.3:a:postgresql:postgresql:14.8:*:*:*:*:*:*:*
cpe:2.3:a:postgresql:postgresql:14.8:*:*:*:*:*:*:*
cpe:2.3:a:postgresql:postgresql:14.9:*:*:*:*:*:*:*
cpe:2.3:a:postgresql:postgresql:14.9:*:*:*:*:*:*:*
cpe:2.3:a:postgresql:postgresql:14.10:*:*:*:*:*:*:*
cpe:2.3:a:postgresql:postgresql:14.10:*:*:*:*:*:*:*
cpe:2.3:a:postgresql:postgresql:14.11:*:*:*:*:*:*:*
cpe:2.3:a:postgresql:postgresql:14.11:*:*:*:*:*:*:*
cpe:2.3:a:postgresql:postgresql:14.12:*:*:*:*:*:*:*
cpe:2.3:a:postgresql:postgresql:14.12:*:*:*:*:*:*:*
cpe:2.3:a:postgresql:postgresql:14.13:*:*:*:*:*:*:*
cpe:2.3:a:postgresql:postgresql:14.13:*:*:*:*:*:*:*
cpe:2.3:a:postgresql:postgresql:14.14:*:*:*:*:*:*:*
cpe:2.3:a:postgresql:postgresql:14.14:*:*:*:*:*:*:*
cpe:2.3:a:postgresql:postgresql:14.15:*:*:*:*:*:*:*
cpe:2.3:a:postgresql:postgresql:14.15:*:*:*:*:*:*:*
cpe:2.3:a:postgresql:postgresql:14.16:*:*:*:*:*:*:*
cpe:2.3:a:postgresql:postgresql:14.16:*:*:*:*:*:*:*
cpe:2.3:a:postgresql:postgresql:14.17:*:*:*:*:*:*:*
cpe:2.3:a:postgresql:postgresql:14.17:*:*:*:*:*:*:*
cpe:2.3:a:postgresql:postgresql:14.18:*:*:*:*:*:*:*
cpe:2.3:a:postgresql:postgresql:14.18:*:*:*:*:*:*:*
cpe:2.3:a:postgresql:postgresql:14.19:*:*:*:*:*:*:*
cpe:2.3:a:postgresql:postgresql:14.19:*:*:*:*:*:*:*
cpe:2.3:a:postgresql:postgresql:14.20:*:*:*:*:*:*:*
cpe:2.3:a:postgresql:postgresql:14.20:*:*:*:*:*:*:*
cpe:2.3:a:postgresql:postgresql:14.21:*:*:*:*:*:*:*
cpe:2.3:a:postgresql:postgresql:14.21:*:*:*:*:*:*:*
cpe:2.3:a:postgresql:postgresql:14.22:*:*:*:*:*:*:*
cpe:2.3:a:postgresql:postgresql:14.22:*:*:*:*:*:*:*
cpe:2.3:a:postgresql:postgresql:14.23:*:*:*:*:*:*:*
cpe:2.3:a:postgresql:postgresql:14.23:*:*:*:*:*:*:*
cpe:2.3:a:postgresql:postgresql:15.0:*:*:*:*:*:*:*
cpe:2.3:a:postgresql:postgresql:15.0:*:*:*:*:*:*:*
cpe:2.3:a:postgresql:postgresql:15.1:*:*:*:*:*:*:*
cpe:2.3:a:postgresql:postgresql:15.1:*:*:*:*:*:*:*
cpe:2.3:a:postgresql:postgresql:15.2:*:*:*:*:*:*:*
cpe:2.3:a:postgresql:postgresql:15.2:*:*:*:*:*:*:*
cpe:2.3:a:postgresql:postgresql:15.3:*:*:*:*:*:*:*
cpe:2.3:a:postgresql:postgresql:15.3:*:*:*:*:*:*:*
cpe:2.3:a:postgresql:postgresql:15.4:*:*:*:*:*:*:*
cpe:2.3:a:postgresql:postgresql:15.4:*:*:*:*:*:*:*
cpe:2.3:a:postgresql:postgresql:15.5:*:*:*:*:*:*:*
cpe:2.3:a:postgresql:postgresql:15.5:*:*:*:*:*:*:*
cpe:2.3:a:postgresql:postgresql:15.6:*:*:*:*:*:*:*
cpe:2.3:a:postgresql:postgresql:15.6:*:*:*:*:*:*:*
cpe:2.3:a:postgresql:postgresql:15.7:*:*:*:*:*:*:*
cpe:2.3:a:postgresql:postgresql:15.7:*:*:*:*:*:*:*
cpe:2.3:a:postgresql:postgresql:15.8:*:*:*:*:*:*:*
cpe:2.3:a:postgresql:postgresql:15.8:*:*:*:*:*:*:*
cpe:2.3:a:postgresql:postgresql:15.9:*:*:*:*:*:*:*
cpe:2.3:a:postgresql:postgresql:15.9:*:*:*:*:*:*:*
cpe:2.3:a:postgresql:postgresql:15.10:*:*:*:*:*:*:*
cpe:2.3:a:postgresql:postgresql:15.10:*:*:*:*:*:*:*
cpe:2.3:a:postgresql:postgresql:15.11:*:*:*:*:*:*:*
cpe:2.3:a:postgresql:postgresql:15.11:*:*:*:*:*:*:*
cpe:2.3:a:postgresql:postgresql:15.12:*:*:*:*:*:*:*
cpe:2.3:a:postgresql:postgresql:15.12:*:*:*:*:*:*:*
cpe:2.3:a:postgresql:postgresql:15.13:*:*:*:*:*:*:*
cpe:2.3:a:postgresql:postgresql:15.13:*:*:*:*:*:*:*
cpe:2.3:a:postgresql:postgresql:15.14:*:*:*:*:*:*:*
cpe:2.3:a:postgresql:postgresql:15.14:*:*:*:*:*:*:*
cpe:2.3:a:postgresql:postgresql:15.15:*:*:*:*:*:*:*
cpe:2.3:a:postgresql:postgresql:15.15:*:*:*:*:*:*:*
cpe:2.3:a:postgresql:postgresql:15.16:*:*:*:*:*:*:*
cpe:2.3:a:postgresql:postgresql:15.16:*:*:*:*:*:*:*
cpe:2.3:a:postgresql:postgresql:15.17:*:*:*:*:*:*:*
cpe:2.3:a:postgresql:postgresql:15.17:*:*:*:*:*:*:*
cpe:2.3:a:postgresql:postgresql:15.18:*:*:*:*:*:*:*
cpe:2.3:a:postgresql:postgresql:15.18:*:*:*:*:*:*:*
cpe:2.3:a:postgresql:postgresql:16.0:*:*:*:*:*:*:*
cpe:2.3:a:postgresql:postgresql:16.0:*:*:*:*:*:*:*
cpe:2.3:a:postgresql:postgresql:16.0:rc1:*:*:*:*:*:*
cpe:2.3:a:postgresql:postgresql:16.0:rc1:*:*:*:*:*:*
cpe:2.3:a:postgresql:postgresql:16.1:*:*:*:*:*:*:*
cpe:2.3:a:postgresql:postgresql:16.1:*:*:*:*:*:*:*
cpe:2.3:a:postgresql:postgresql:16.2:*:*:*:*:*:*:*
cpe:2.3:a:postgresql:postgresql:16.2:*:*:*:*:*:*:*
cpe:2.3:a:postgresql:postgresql:16.3:*:*:*:*:*:*:*
cpe:2.3:a:postgresql:postgresql:16.3:*:*:*:*:*:*:*
cpe:2.3:a:postgresql:postgresql:16.4:*:*:*:*:*:*:*
cpe:2.3:a:postgresql:postgresql:16.4:*:*:*:*:*:*:*
cpe:2.3:a:postgresql:postgresql:16.5:*:*:*:*:*:*:*
cpe:2.3:a:postgresql:postgresql:16.5:*:*:*:*:*:*:*
cpe:2.3:a:postgresql:postgresql:16.6:*:*:*:*:*:*:*
cpe:2.3:a:postgresql:postgresql:16.6:*:*:*:*:*:*:*
cpe:2.3:a:postgresql:postgresql:16.7:*:*:*:*:*:*:*
cpe:2.3:a:postgresql:postgresql:16.7:*:*:*:*:*:*:*
cpe:2.3:a:postgresql:postgresql:16.8:*:*:*:*:*:*:*
cpe:2.3:a:postgresql:postgresql:16.8:*:*:*:*:*:*:*
cpe:2.3:a:postgresql:postgresql:16.9:*:*:*:*:*:*:*
cpe:2.3:a:postgresql:postgresql:16.9:*:*:*:*:*:*:*
cpe:2.3:a:postgresql:postgresql:16.10:*:*:*:*:*:*:*
cpe:2.3:a:postgresql:postgresql:16.10:*:*:*:*:*:*:*
cpe:2.3:a:postgresql:postgresql:16.11:*:*:*:*:*:*:*
cpe:2.3:a:postgresql:postgresql:16.11:*:*:*:*:*:*:*
cpe:2.3:a:postgresql:postgresql:16.12:*:*:*:*:*:*:*
cpe:2.3:a:postgresql:postgresql:16.12:*:*:*:*:*:*:*
cpe:2.3:a:postgresql:postgresql:16.13:*:*:*:*:*:*:*
cpe:2.3:a:postgresql:postgresql:16.13:*:*:*:*:*:*:*
cpe:2.3:a:postgresql:postgresql:16.14:*:*:*:*:*:*:*
cpe:2.3:a:postgresql:postgresql:16.14:*:*:*:*:*:*:*
cpe:2.3:a:postgresql:postgresql:17.0:-:*:*:*:*:*:*
cpe:2.3:a:postgresql:postgresql:17.0:-:*:*:*:*:*:*
cpe:2.3:a:postgresql:postgresql:17.0:rc1:*:*:*:*:*:*
cpe:2.3:a:postgresql:postgresql:17.0:rc1:*:*:*:*:*:*
cpe:2.3:a:postgresql:postgresql:17.0:beta1:*:*:*:*:*:*
cpe:2.3:a:postgresql:postgresql:17.0:beta1:*:*:*:*:*:*
cpe:2.3:a:postgresql:postgresql:17.0:beta2:*:*:*:*:*:*
cpe:2.3:a:postgresql:postgresql:17.0:beta2:*:*:*:*:*:*
cpe:2.3:a:postgresql:postgresql:17.0:beta3:*:*:*:*:*:*
cpe:2.3:a:postgresql:postgresql:17.0:beta3:*:*:*:*:*:*
cpe:2.3:a:postgresql:postgresql:17.1:*:*:*:*:*:*:*
cpe:2.3:a:postgresql:postgresql:17.1:*:*:*:*:*:*:*
cpe:2.3:a:postgresql:postgresql:17.2:*:*:*:*:*:*:*
cpe:2.3:a:postgresql:postgresql:17.2:*:*:*:*:*:*:*
cpe:2.3:a:postgresql:postgresql:17.3:*:*:*:*:*:*:*
cpe:2.3:a:postgresql:postgresql:17.3:*:*:*:*:*:*:*
cpe:2.3:a:postgresql:postgresql:17.4:*:*:*:*:*:*:*
cpe:2.3:a:postgresql:postgresql:17.4:*:*:*:*:*:*:*
cpe:2.3:a:postgresql:postgresql:17.5:*:*:*:*:*:*:*
cpe:2.3:a:postgresql:postgresql:17.5:*:*:*:*:*:*:*
cpe:2.3:a:postgresql:postgresql:17.6:*:*:*:*:*:*:*
cpe:2.3:a:postgresql:postgresql:17.6:*:*:*:*:*:*:*
cpe:2.3:a:postgresql:postgresql:17.7:*:*:*:*:*:*:*
cpe:2.3:a:postgresql:postgresql:17.7:*:*:*:*:*:*:*
cpe:2.3:a:postgresql:postgresql:17.8:*:*:*:*:*:*:*
cpe:2.3:a:postgresql:postgresql:17.8:*:*:*:*:*:*:*
cpe:2.3:a:postgresql:postgresql:17.9:*:*:*:*:*:*:*
cpe:2.3:a:postgresql:postgresql:17.9:*:*:*:*:*:*:*
cpe:2.3:a:postgresql:postgresql:17.10:*:*:*:*:*:*:*
cpe:2.3:a:postgresql:postgresql:17.10:*:*:*:*:*:*:*
cpe:2.3:a:postgresql:postgresql:18.0:*:*:*:*:*:*:*
cpe:2.3:a:postgresql:postgresql:18.0:*:*:*:*:*:*:*
cpe:2.3:a:postgresql:postgresql:18.1:*:*:*:*:*:*:*
cpe:2.3:a:postgresql:postgresql:18.1:*:*:*:*:*:*:*
cpe:2.3:a:postgresql:postgresql:18.2:*:*:*:*:*:*:*
cpe:2.3:a:postgresql:postgresql:18.2:*:*:*:*:*:*:*
cpe:2.3:a:postgresql:postgresql:18.3:*:*:*:*:*:*:*
cpe:2.3:a:postgresql:postgresql:18.3:*:*:*:*:*:*:*
cpe:2.3:a:postgresql:postgresql:18.4:*:*:*:*:*:*:*
cpe:2.3:a:postgresql:postgresql:18.4:*:*:*:*:*:*:*

Protect Your Infrastructure against CVE-2026-14666: Combat Critical CVE Threats

Stay updated with real-time CVE vulnerabilities and take action to secure your systems. Enhance your cybersecurity posture with the latest threat intelligence and mitigation techniques. Develop the skills necessary to defend against CVEs and secure critical infrastructures. Join the top cybersecurity professionals safeguarding today's infrastructures.

Other 5 Recently Published CVEs Vulnerabilities

CVE-2026-85200 – The GEO my WP plugin for WordPress is vulnerable to Local File Inclusion in all versions up to, and including, 4.5.5.3 via the gmw_posts_locator_aj...
CVE-2026-85198 – The MPG – Multiple Page Generator, Bulk Landing Pages & Programmatic SEO plugin for WordPress is vulnerable to generic SQL Injection via URL Path i...
CVE-2026-78175 – The Tutor LMS – eLearning and online course solution plugin for WordPress is vulnerable to PHP Object Injection in all versions up to, and includin...
CVE-2026-78159 – The The Events Calendar plugin for WordPress is vulnerable to Remote Code Execution in all versions up to, and including, 6.17.3 via the parse_arra...
CVE-2026-78006 – The The Events Calendar plugin for WordPress is vulnerable to Remote Code Execution in all versions up to, and including, 6.17.4 via the is_safe_wi...