Loading vulnerability…
CVE-2026-15742 is an integer-wraparound vulnerability in PostgreSQL's fuzzystrmatch extension. Extreme arguments supplied to the levenshtein() or levenshtein_less_equal() SQL functions can cause arithmetic to wrap, enabling writes across a very large, effectively arbitrary memory-address range. The memory corruption can be leveraged to execute arbitrary code in the operating-system context of the PostgreSQL database service account. Affected releases are PostgreSQL versions prior to 18.6, 17.11, 16.15, 15.19, and 14.24.
Mallory correlates every CVE against your assets, your vendors, and active adversary campaigns. Know which vulnerabilities matter for you, not just which ones are loud.
What it means. What to do now. Patch path, mitigations, and the assume-compromise checklist.
What an attacker gets, and what they’ve been doing with it.
If you can’t patch tonight, do this now.
Patch, then assume compromise.
No public exploits tracked yet. Mallory keeps watching.
No public exploit code observed for this vulnerability.
Products and vendors Mallory has correlated with this vulnerability. Open in Mallory to drill down to specific CPE configurations and version ranges.
Vendor-confirmed product mapping. Mallory continuously reconciles this list against your asset inventory.
29 sources tracked across advisories, community write-ups, and news. New activity surfaces here as Mallory finds it.
A PostgreSQL fuzzystrmatch arbitrary-code-execution vulnerability caused by integer wraparound.
A PostgreSQL vulnerability referenced by the plugin; no technical vulnerability details are provided.
A PostgreSQL fuzzystrmatch integer-wraparound flaw enabling writes to effectively arbitrary addresses.
A fuzzystrmatch integer-wraparound vulnerability enabling writes to effectively arbitrary addresses.
Query your assets running an affected version, and investigate the blast radius.
Every observed campaign linking this CVE to a named adversary.
Malware families riding this exploit, with evidence and IOCs.
YARA, Sigma, Snort, and vendor rules, auto-deployed to your SIEM.
Cross-references every affected SKU, including bundled OEM variants.
Community discussion across Reddit, Mastodon, and other social sources.