RCE in widely used PostgreSQL via built-in fuzzystrmatch; can lead to OS-level code execution and enterprise disruption.
CVE-2026-15742
Integer wrap in PostgreSQL fuzzystrmatch enables arbitrary code execution via levenshtein()
WAF coverage: Integer overflow.
Also consider: patch
Is CVE-2026-15742 being exploited?
Not confirmed. CVE-2026-15742 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-15742?
CVE-2026-15742 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-15742?
Yes. A fix has been recorded for CVE-2026-15742. The vendor advisory is the authority on the exact fixed version — apply it from there rather than from a summary.
What does CVE-2026-15742 affect?
CVE-2026-15742 affects PostgreSQL versions before 18.5, 17.11, 16.15, 15.19, 14.24, fuzzystrmatch extension: levenshtein() and levenshtein_less_equal(). Confirm the exact affected versions against the vendor advisory before deciding you are exposed.
What should I do about CVE-2026-15742?
Upgrade to listed fixed PostgreSQL versions; disable fuzzystrmatch or restrict DB access until patched.
Exploitation status reflects CISA's KEV catalog as we last synced it. Check the catalog directly.
Crafted inputs to levenshtein() trigger integer wrap allowing arbitrary memory writes and code execution as the DB server OS user.
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.