PostgreSQL is widely used; this RCE in a core extension can lead to OS-level compromise across many organizations.
CVE-2026-14676
Heap buffer overflow in PostgreSQL pg_stat_statements enabling OS-level code execution.
Is CVE-2026-14676 being exploited?
Not confirmed. CVE-2026-14676 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.43% probability of exploitation in the next 30 days.
How severe is CVE-2026-14676?
CVE-2026-14676 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-14676?
Yes. A fix has been recorded for CVE-2026-14676. The vendor advisory is the authority on the exact fixed version — apply it from there rather than from a summary.
What does CVE-2026-14676 affect?
CVE-2026-14676 affects PostgreSQL 18.0–18.4 (pg_stat_statements enabled), pg_stat_statements extension. Confirm the exact affected versions against the vendor advisory before deciding you are exposed.
What should I do about CVE-2026-14676?
Upgrade to PostgreSQL 18.5 or apply vendor patch; disable pg_stat_statements if needed.
Exploitation status reflects CISA's KEV catalog as we last synced it. Check the catalog directly.
Arbitrary code execution as the OS user running PostgreSQL via crafted queries with array constants.
Immediate action required
- affected>= 18 and < 18.6
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.