Missing authorization in PostgreSQL logical decoding allows a non-superuser holding REPLICATION privilege to dlopen any file visible to the operating system account running the server, via the choice of logical decoding plugin. This in turn runs arbitrary code as that account. Versions before PostgreSQL 18.5, 17.11, 16.15, 15.19, and 14.24 are affected.
CVE-2026-6471
Score 7.2 from GitHub Security Advisory (severity: HIGH) published 2026-08-13. a secondary CVSS source baseline 7.2; sources differ by 0.0.
- High severity, but no confirmed exploitation yet
A fix is available — apply it.
- CVSS v3
- 7.2
- EG Score
- 7.2(high)
- EG Risk
- 33(Track)EG Risk 33/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 computedSeverity72% × 45%Exploitation1% × 40%Automatability0% × 15%Action: Routine — remediate on your standard cadence. - EPSS PROB
- 1%
- EPSS %ILE
- 42%
- KEV
- Not listed
Published
August 13, 2026
Last Modified
August 19, 2026
Advisory Details (1)
Auto-updated Aug 13, 2026PostgreSQL: CVE-2026-6471: PostgreSQL logical decoding can dlopen arbitrary file
https://www.postgresql.org/support/security/CVE-2026-6471/Vendor Advisories for CVE-2026-6471(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 / Ecosystem | Fixed in / Patch | Released | Source |
|---|---|---|---|
| ubuntu | postgresql-server-dev-18 (18.6-0ubuntu0.26.04.1) @ resolute | 2026-08-20 | ubuntu |
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 31× in last 7d / 40× 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.
- 2026-08-20 23:46 UTCEG score recompute
- 2026-08-20 23:46 UTCVendor advisory
- 2026-08-20 23:46 UTCGHSA enrichment
- 2026-08-20 22:56 UTCEPSS rescore
- 2026-08-20 12:10 UTCGHSA enrichment
- 2026-08-20 00:34 UTCEG score recompute
- 2026-08-20 00:34 UTCGHSA enrichment
- 2026-08-19 17:04 UTCEPSS rescore
- 2026-08-19 12:57 UTCGHSA enrichment
- 2026-08-19 01:20 UTCGHSA enrichment
- 2026-08-18 15:12 UTCEG score recompute
- 2026-08-18 15:12 UTCGHSA enrichment
- 2026-08-18 13:49 UTCEPSS rescore
- 2026-08-18 13:49 UTCEPSS rescore
- 2026-08-18 02:22 UTCGHSA enrichment
- 2026-08-17 14:38 UTCEG score recompute
- 2026-08-17 14:38 UTCGHSA enrichment
- 2026-08-17 13:47 UTCEPSS rescore
- 2026-08-17 03:02 UTCGHSA enrichment
- 2026-08-16 15:25 UTCEG score recompute
- 2026-08-16 15:25 UTCGHSA enrichment
- 2026-08-16 14:56 UTCEPSS rescore
- 2026-08-16 14:56 UTCEPSS rescore
- 2026-08-16 03:49 UTCEG score recompute
- 2026-08-16 03:49 UTCGHSA enrichment
Show 15 moreShow fewer
- 2026-08-16 02:15 UTCEPSS rescore
- 2026-08-15 16:13 UTCGHSA enrichment
- 2026-08-15 04:37 UTCEG score recompute
- 2026-08-15 04:37 UTCGHSA enrichment
- 2026-08-15 01:31 UTCEPSS rescore
- 2026-08-14 17:01 UTCGHSA enrichment
- 2026-08-14 05:25 UTCGHSA enrichment
- 2026-08-14 04:05 UTCGHSA enrichment
- 2026-08-13 16:29 UTCEG score recompute
- 2026-08-13 16:29 UTCGHSA enrichment
- 2026-08-13 16:01 UTCEG score recompute
- 2026-08-13 16:01 UTCGHSA enrichment
- 2026-08-13 13:35 UTCEG score recompute
- 2026-08-13 13:17 UTCEG score recompute
- 2026-08-13 13:16 UTCMITRE cvelistV5first tracked
Related CVEs(same vendor + same CWE)
Same vendor
10 shownubuntu
- CVE-2004-0989EG 10.0EPSS p97HIGH
- CVE-2004-0990EG 10.0EPSS p98HIGH
- CVE-2004-1010EG 10.0EPSS p95HIGH
- CVE-2004-0941EG 10.0EPSS p95HIGH
- CVE-2004-0981EG 10.0EPSS p93HIGH
- CVE-2004-0882EG 10.0EPSS p96HIGH
- CVE-2004-0888EG 10.0EPSS p95HIGH
- CVE-2004-1012EG 10.0EPSS p93HIGH
- CVE-2004-1013EG 10.0EPSS p93HIGH
- CVE-2004-1018EG 10.0EPSS p97HIGH
Same CWE
10 shownCWE-862
- CVE-2013-3960EG 9.9CRITICAL
- CVE-2015-10143EG 9.8CRITICAL
- CVE-2016-11036EG 9.8CRITICAL
- CVE-2018-11541EG 9.8CRITICAL
- CVE-2011-4183NVD 6.5EG 9.8CRITICAL
- CVE-2018-10251EG 9.8EPSS p91CRITICAL
- CVE-2018-1217EG 9.8EPSS p99CRITICAL
- CVE-2018-0015EG 9.8CRITICAL
- CVE-2017-12582EG 9.8CRITICAL
- CVE-2017-1000056EG 9.8CRITICAL
Frequently asked(5)
What is CVE-2026-6471?
When was CVE-2026-6471 disclosed?
Is CVE-2026-6471 actively exploited?
What is the CVSS score of CVE-2026-6471?
How do I remediate CVE-2026-6471?
Dependency Blast Radius
Explore the affected products and dependency analysis for CVE-2026-6471
Is Your Infrastructure Affected by CVE-2026-6471?
EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.