Free and open · new CVEs checked every 20 minutesStatusRSSOpen dataContact

CVE-2026-14666: Incomplete tracking in PostgreSQL of changes to role membership, role attributes, and database ownership allow

17
Routine
MEDIUM 4.2UPGRADE

CVE-2026-14666 is a medium-severity flaw (CVSS 4.2) affecting postgresql. Below: why it ranks where it does, which versions are affected, what to do, and the exact commands.

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 forbi

Why this priority

  • No elevated risk signals yet

A fixed release or distro patch exists.

Risk facts

CVSS score4.2 (Medium)
Attack vectorNetwork (remote)
Attack complexityHigh
Privileges neededLow
User interactionNone
EPSS exploit chance0.2% (top 89%)
CISA exploited listNo
WeaknessCWE-1250
Published2026-08-13
Last modified2026-08-29
Publisher (CNA): PostgreSQL · Vendor: postgresql

Share: LinkedIn · X · Reddit

Last updated 2026-08-29 · Sources: CVE Program, NVD, CISA KEV, EPSS and vendor advisories · How we score

Am I affected?

Timeline

postgresql postgresql UPGRADE
Affected: >= 14.0 and < 14.24 · >= 15.0 and < 15.19 · >= 16.0 and < 16.15 · >= 17.0 and < 17.11 · >= 18.0 and < 18.5
Fixed in: 14.24, 15.19, 16.15, 17.11, 18.5
Safe to downgrade to: a release before 14.0
1. Check installed version
apt-cache policy postgresql || rpm -q postgresql || postgresql --version
2. UPGRADE to 14.24 (Debian / Ubuntu)
sudo apt update && sudo apt install --only-upgrade postgresql
2. UPGRADE (RHEL / Amazon Linux / Fedora)
sudo dnf upgrade postgresql
Note
Distros often backport fixes without changing the version number. Confirm with the distro advisory or changelog.
3. If no update is available yet, DOWNGRADE to a release before 14.0 (Debian / Ubuntu)
apt-cache madison postgresql sudo apt install postgresql=<VERSION_BEFORE_14.0> sudo apt-mark hold postgresql
3. If no update is available yet, DOWNGRADE (RHEL / Amazon Linux / Fedora)
dnf --showduplicates list postgresql sudo dnf downgrade postgresql-<VERSION_BEFORE_14.0> sudo dnf versionlock add postgresql
Downgrade risk
Downgrading can break dependent software and may reopen older bugs. Read the distro advisory first and test on a non-production host.
After downgrade
Restart the service, and keep the package held until a fixed release ships.
Verify at the official source NVD · CVE Program · Report a problem with this page
Scores and fixes here are computed automatically from those and other public sources. Confirm with the vendor advisory before changing production systems.

Quick answers

How do I fix CVE-2026-14666?

postgresql: upgrade to 14.24, 15.19, 16.15, 17.11, 18.5. Exact commands for each OS are on this page.

Is CVE-2026-14666 being exploited?

CVE-2026-14666 is not on the CISA Known Exploited Vulnerabilities list at the time of the last update. Check again, as this can change.

What does CVE-2026-14666 affect?

CVE-2026-14666 affects postgresql. Severity is medium (CVSS 4.2). 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. St

How urgent is CVE-2026-14666?

Priority 17/100. No elevated risk signals yet.

Software pages

PostgreSQL vulnerabilities

Related CVEs

References

← Back to latest CVEs

Get the weekly exploited-CVE digest by emailThe CVEs being attacked this week and how to fix them. No spam, unsubscribe any time.