Affects PostgreSQL, a widely used database; allows arbitrary code execution as the DB server OS user, posing broad operational and data risk.
CVE-2026-14677
Integer wrap in 32-bit PostgreSQL pltcl/plperl enabling arbitrary code execution.
Is CVE-2026-14677 being exploited?
Not confirmed. CVE-2026-14677 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-14677?
CVE-2026-14677 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-14677?
Yes. A fix has been recorded for CVE-2026-14677. The vendor advisory is the authority on the exact fixed version — apply it from there rather than from a summary.
What does CVE-2026-14677 affect?
CVE-2026-14677 affects PostgreSQL < 18.5 (32-bit builds with pltcl/plperl), PostgreSQL < 17.11 (32-bit builds with pltcl/plperl), PostgreSQL < 16.15 (32-bit builds with pltcl/plperl), PostgreSQL < 15.19 (32-bit builds with pltcl/plperl), 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-14677?
Upgrade to listed fixed releases or disable pltcl/plperl until patched; apply updates immediately.
Exploitation status reflects CISA's KEV catalog as we last synced it. Check the catalog directly.
Crafted pltcl/plperl function bodies cause undersized allocation and OOB write, enabling arbitrary code execution as the OS user running PostgreSQL.
Patch when possible
- 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.