PostgreSQL is widely used across enterprises; this RCE (arbitrary code as DB OS user) can lead to full DB host compromise and lateral movement.
CVE-2026-14664
Heap overflow in PostgreSQL regexp allows arbitrary code execution as DB OS user.
WAF coverage: Heap-based buffer overflow.
Also consider: patch
Is CVE-2026-14664 being exploited?
Not confirmed. CVE-2026-14664 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.44% probability of exploitation in the next 30 days.
How severe is CVE-2026-14664?
CVE-2026-14664 is rated High. 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-14664?
Yes. A fix has been recorded for CVE-2026-14664. The vendor advisory is the authority on the exact fixed version — apply it from there rather than from a summary.
What does CVE-2026-14664 affect?
CVE-2026-14664 affects PostgreSQL < 18.5, PostgreSQL < 17.11, PostgreSQL < 16.15, PostgreSQL < 15.19, and 1 further product or version. Confirm the exact affected versions against the vendor advisory before deciding you are exposed.
What should I do about CVE-2026-14664?
Upgrade to 18.5, 17.11, 16.15, 15.19 or 14.24+ immediately; restrict DB access until patched.
Exploitation status reflects CISA's KEV catalog as we last synced it. Check the catalog directly.
Crafted regexp/text can trigger heap overflow, enabling arbitrary code execution as the OS user running PostgreSQL, risking DB host compromise and data theft.
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.