CVE-2026-14666

MEDIUMPre-NVD 4.24.2—
EchelonGraph scoreHIGH confidence

Score 4.2 from GitHub Security Advisory published 2026-08-13. a secondary CVSS source baseline 4.2; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: epss, ghsa, secondary
Trending — 4 sources updated this week
4.2EG
EchelonGraph verdictMonitorLow exploitation likelihood right now — keep watching.
  • Lower severity and no public exploit yet
CISA-KEV: Not listedEPSS PROB: 0%CVSS: 4.2Exploit: None knownExposed: 0

A fix is available — apply it.

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
4.2
EG Score
4.2(high)
EG Risk
19(Track)
EG Risk 19/100SSVC: Track

EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).

How it’s computed
Severity42% × 45%
Exploitation0% × 40%
Automatability0% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
0%
EPSS %ILE
11%
KEV
Not listed

Published

August 13, 2026

Last Modified

August 19, 2026

Advisory Details (1)

Auto-updated Aug 13, 2026
No patch confirmed yet.
generic

PostgreSQL: CVE-2026-14666: PostgreSQL row security caching disregards role modifications

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

Vendor Advisories for CVE-2026-14666(1)

These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.

Patch Availability(1)

Vendor / EcosystemFixed in / PatchReleasedSource
ubuntupostgresql-server-dev-18 (18.6-0ubuntu0.26.04.1) @ resolute2026-08-20ubuntu

Patches are aggregated from vendor advisories (Red Hat, Microsoft, Cisco, GitHub) and package ecosystems (OSV, GHSA). Multiple rows for the same upstream release have been deduplicated.

Weakness Classification(1)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

All Vendor Advisories

(1)

Every vendor that published an advisory referencing this CVE — pulled from our cve_vendor_advisories aggregation. Click any row for the vendor's original advisory page.

Data Freshness Timeline

(refreshed 19× in last 7d / 25× in last 30d)

Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.

  1. 2026-08-20 22:55 UTCEPSS rescore
  2. 2026-08-20 15:34 UTCEG score recompute
  3. 2026-08-20 15:34 UTCVendor advisory
  4. 2026-08-20 15:34 UTCGHSA enrichment
  5. 2026-08-19 17:03 UTCEPSS rescore
  6. 2026-08-19 15:04 UTCGHSA enrichment
  7. 2026-08-18 15:33 UTCEG score recompute
  8. 2026-08-18 15:33 UTCGHSA enrichment
  9. 2026-08-18 13:48 UTCEPSS rescore
  10. 2026-08-17 19:13 UTCEG score recompute
  11. 2026-08-17 19:13 UTCGHSA enrichment
  12. 2026-08-16 17:55 UTCEG score recompute
  13. 2026-08-16 17:55 UTCGHSA enrichment
  14. 2026-08-16 14:56 UTCEPSS rescore
  15. 2026-08-16 02:14 UTCEPSS rescore
  16. 2026-08-15 17:27 UTCEG score recompute
  17. 2026-08-15 17:27 UTCGHSA enrichment
  18. 2026-08-15 01:30 UTCEPSS rescore
  19. 2026-08-14 16:58 UTCGHSA enrichment
  20. 2026-08-13 16:30 UTCEG score recompute
  21. 2026-08-13 16:30 UTCGHSA enrichment
  22. 2026-08-13 16:02 UTCEG score recompute
  23. 2026-08-13 16:02 UTCGHSA enrichment
  24. 2026-08-13 13:17 UTCEG score recompute
  25. 2026-08-13 13:16 UTCMITRE cvelistV5first tracked

Frequently asked(5)

What is CVE-2026-14666?
CVE-2026-14666 is a medium vulnerability published on August 13, 2026. 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…
When was CVE-2026-14666 disclosed?
CVE-2026-14666 was first published in the National Vulnerability Database on August 13, 2026, with the most recent update on August 19, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-14666 actively exploited?
CVE-2026-14666 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0% probability of exploitation in the next 30 days, which ranks it in the top 88.6% of all scored CVEs.
What is the CVSS score of CVE-2026-14666?
CVE-2026-14666 has a CVSS v3 base score of 4.2 (NVD).
How do I remediate CVE-2026-14666?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-14666, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

Dependency Blast Radius

Explore the affected products and dependency analysis for CVE-2026-14666

Explore →

Is Your Infrastructure Affected by CVE-2026-14666?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.

Start Free Scan →Browse All CVEs