PostgreSQL is widely deployed; vulnerability allows OS-level code execution as DB service user—high-impact for many organizations.
CVE-2026-14671
Type confusion in PostgreSQL refint allows OS-level code execution as DB service user
WAF coverage: Network-reachable. Generic WAF signatures may reduce blast radius. No CWE mapping to be precise.
Also consider: patch
Is CVE-2026-14671 being exploited?
Not confirmed. CVE-2026-14671 does not appear in CISA's Known Exploited Vulnerabilities catalog, which records only exploitation that has been observed and reported publicly. That is evidence of absence of a report, not evidence the flaw is unattacked. EPSS currently estimates a 0.42% probability of exploitation in the next 30 days.
How severe is CVE-2026-14671?
CVE-2026-14671 is rated High with a CVSS score of 8.8. Severity describes how bad exploitation would be, not how likely it is: pair it with exploitation evidence before deciding what to patch first.
Is there a patch for CVE-2026-14671?
Yes. A fix has been recorded for CVE-2026-14671. The vendor advisory is the authority on the exact fixed version — apply it from there rather than from a summary.
What does CVE-2026-14671 affect?
CVE-2026-14671 affects PostgreSQL refint module, Versions before 18.5, Versions before 17.11, Versions before 16.15, and 2 further products or versions. Confirm the exact affected versions against the vendor advisory before deciding you are exposed.
What should I do about CVE-2026-14671?
Upgrade to 18.5/17.11/16.15/15.19/14.24 or apply vendor patch; restrict CREATE privileges.
Exploitation status reflects CISA's KEV catalog as we last synced it. Check the catalog directly.
Authenticated DB object creator can execute arbitrary OS commands as the database service account via refint type confusion.
Immediate action required
- affected>= 18 and < 18.6
- affected>= 17 and < 17.11
- affected>= 16 and < 16.15
- affected>= 15 and < 15.19
- affected< 14.24
As published in the CVE Program record. A version outside these ranges is not a statement that it is unaffected — vendors sometimes understate a range, and distribution-backported builds carry upstream numbers that do not reflect what was patched into them.