CVE-2026-15742: PostgreSQL · Integer Overflow or Wraparound
Affects PostgreSQLSource CVE Database V5
Not known to be exploited · CVSS 8.8 High · fixed in 18.6 : patch PostgreSQL soon.
Data as of 12 Nov 2026, 23:24 UTC
- EPSS
- 0.5% chance of exploitation in 30 days – higher than 48% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
- Patch
- Available – fixed in 18.6, 17.11, 16.15 +3
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:HExploitation evidence
Disclosed: evidence found.
CVE published 13 Aug 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponized: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors
A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 13 Nov 2026.
What to do
Upgrade to a fixed release listed under Affected software.
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| PostgreSQL | Affected
| Fixed in
|
| PostgreSQL | Affected
| Fixed in
|
| PostgreSQL | Affected
| Fixed in
|
| PostgreSQL | Affected
| Fixed in
|
| PostgreSQL | Affected
| Fixed in
|
Postgresqlpostgresql/postgresqlpkg:deb/postgresql/postgresqlOther threats | Affected
| Fixed in
|
Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.
AI-suggested
Upgrading PostgreSQL to versions 14.24, 15.19, 16.15, 17.11, or 18.6 and later addresses this vulnerability. Users should apply these official patches to remediate the issue. No alternative mitigations are indicated in the provided data.
Description
CVE-2026-15742 is an integer overflow or wraparound vulnerability in PostgreSQL's fuzzystrmatch extension. It allows a user with database privileges to execute arbitrary code as the operating system user running the database by providing extreme inputs to the levenshtein() or levenshtein_less_equal() SQL functions. This affects multiple PostgreSQL versions prior to 18.6, 17.11, 16.15, 15.19, and 14.24.