PostgreSQL is widely used enterprise DB; a stack buffer overflow in core database code can cause crashes or enable code execution, making it notable for broad IT audiences.
CVE-2026-14679
PostgreSQL stack buffer overflow via argument name matching allowing limited memory writes.
WAF coverage: Stack-based buffer overflow.
Also consider: patch
Is CVE-2026-14679 being exploited?
Not confirmed. CVE-2026-14679 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.29% probability of exploitation in the next 30 days.
How severe is CVE-2026-14679?
CVE-2026-14679 is rated High with a CVSS score of 8.2. 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-14679?
Yes. A fix has been recorded for CVE-2026-14679. The vendor advisory is the authority on the exact fixed version — apply it from there rather than from a summary.
What does CVE-2026-14679 affect?
CVE-2026-14679 affects PostgreSQL < 18.5, PostgreSQL < 17.11, PostgreSQL < 16.15, PostgreSQL < 15.19, 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-14679?
Upgrade to fixed PostgreSQL versions (18.5,17.11,16.15,15.19,14.24) immediately
Exploitation status reflects CISA's KEV catalog as we last synced it. Check the catalog directly.
Authenticated database object creators can trigger a stack buffer overflow allowing limited 0x0/0x1 memory writes, potentially causing crashes or enabling code execution.
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.