CVE-2026-15742

HIGHPre-NVD 8.88.8
EchelonGraph scoreMEDIUM confidence

“—” beside the score: it is equal to the CVSS score beside it.

Score 8.8 from GitHub Security Advisory (severity: HIGH) published 2026-08-13. A secondary CVSS source baseline 8.8; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: EPSS, GitHub Security Advisory, a secondary CVSS source

Also known asEUVD-2026-57847 (ENISA EUVD) · GHSA-rvq6-xp6x-5575 (GitHub Security Advisories)Source: ENISA EUVD

8.8EG
EchelonGraph verdictPlan a fixRemediate within your standard update timelines (the SSVC decision on this page).
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 0.6%CVSS: 8.8Exploit: None knownExposed services: Not assessed

A fix is available — apply it.

Integer wraparound in PostgreSQL fuzzystrmatch allows a user to direct writes to a huge range of addresses, executing arbitrary code as the operating system user running the database, via extreme inputs to SQL function levenshtein() or levenshtein_less_equal(). Versions before PostgreSQL 18.6, 17.11, 16.15, 15.19, and 14.24 are affected.

CVSS v3
8.8
EG Score
8.8HIGHmedium confidence
EG Risk
40
EG Risk 40/100

EG Risk is EchelonGraph's 0–100 priority score. It fuses impact severity (EG Severity, the CVSS base score, never the KEV-floored or EPSS-lifted EG Score) with real-world exploitation and automatability, under weights EchelonGraph set by hand, so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner.

How it’s computed (value × EchelonGraph’s weight)
Severity88% × 45%
Impact severity (EG Severity): CVSS 8.8 of 10. Never the KEV-floored or EPSS-lifted EG Score.
Exploitation0.6% × 40%
FIRST EPSS: the 30-day exploitation probability when EchelonGraph scored this CVE.
Automatability0% × 15%
CISA's SSVC Automatable value: no (Vulnrichment).
SSVC (CISA's decision table, applied by EchelonGraph): Track at low or medium mission impact; Track* at high (mission-essential systems).
Exploitation none (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact total (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE.
Action: A fix is available. Apply it within your standard update timelines.
EPSS PROB
0.6%
EPSS %ILE
49th
KEV
Not listed

What the EG score is made of (scorer v4.0: the three questions the 0–10 score mixes, published apart · methodology)

The EG score (8.8): severity, escalated by confirmed exploitation. This CVE's 8.8 is its impact severity (EG Severity), not escalated.

EG Severity
8.8 HIGHCVSS-B, impact only: no KEV listing, EPSS or EG-KEV tier raises it.GitHub Security Advisory CVSS
EG Likelihood
0.6% within 30 daysSource: FIRST EPSS (model v2026.06.15, score date 2026-11-11). FIRST's exploitation probability, not an EchelonGraph model.
Confirmed exploitation
None on record (CISA KEV, EG-KEV Tier 1)Reported apart from the likelihood: an observed fact, not a probability.
EG Priority
SSVC Track at medium mission impactTrack at low or medium mission impact; Track* at high (mission-essential systems).CISA BOD 26-04: 14 days if the affected system is publicly exposed; Fix on system upgrade if it is not.Each input and its source, and whom BOD 26-04 binds: the SSVC and BOD 26-04 blocks below.

SSVC (CISA's decision table, applied by EchelonGraph)Track at low or medium mission impact; Track* at high (mission-essential systems).

A fix is available. Apply it within your standard update timelines.

Exploitation none (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact total (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE. Mission impact is CISA's Mission & Well-being decision point, and only you can judge it. CISA's table makes it high when Mission Prevalence is Essential — the vulnerable component "directly provides capabilities that constitute at least one MEF for at least one entity" (MEF: mission essential function) — or when Public Well-Being Impact is Irreversible: "multiple fatalities are likely", the cyber-physical system "is likely lost or destroyed", "extreme or serious externalities" are imposed on other parties, or social systems such as elections or the financial grid "are destabilized and potentially collapse". CISA's decision table

BOD 26-04 (CISA's remediation timeline, Table 1)14 days if the affected system is publicly exposed; Fix on system upgrade if it is not.

The score's inputs: In CISA KEV no (CISA's KEV catalog) · Automatable no (CISA Vulnrichment) · Technical impact total (CISA Vulnrichment). Whether your system is publicly exposed is yours to answer. BOD 26-04 binds US Federal Civilian Executive Branch agencies; for anyone else it is CISA's published timeline, a reference rather than an obligation. The directive · how EchelonGraph applies it

Published

August 13, 2026

Last Modified

August 29, 2026

Advisory Details (1)

Auto-updated Aug 13, 2026
Patch available.
Web page

PostgreSQL: CVE-2026-15742: PostgreSQL fuzzystrmatch writes effectively-arbitrary addresses, via integer wraparound

https://www.postgresql.org/support/security/CVE-2026-15742/

Patch Availability(26)

Vendor / EcosystemFix (by version range) / PatchReleasedSource
ubuntupostgresql-server-dev-16 (16.15-0ubuntu0.24.04.1) @ noble2026-11-12ubuntu
redhatpostgresql-0:9.2.24-9.el7_9.72026-10-19redhat
redhatpostgresql:12-8040020260924163759.522a0ee42026-09-30redhat
redhatansible-automation-platform/bootc-automation-portal-rhel9:17906573742026-09-29redhat
redhatpostgresql-0:13.23-1.el9_2.52026-09-28redhat
redhatpostgresql16-0:16.15-1.el10_02026-09-28redhat
redhatpostgresql:12-8080020260923144922.63b345852026-09-28redhat
redhatpostgresql-0:13.23-1.el9_6.52026-09-28redhat
redhatpostgresql-0:13.23-1.el9_4.42026-09-28redhat
redhatpostgresql:12-8060020260923144955.ad008a3a2026-09-28redhat
redhatrhui5/rhua-rhel9:17902420042026-09-24redhat
redhatpostgresql:16-9040020260922062609.rhel92026-09-23redhat
redhatpostgresql:15-8080020260921162003.63b345852026-09-23redhat
redhatpostgresql:16-9060020260921091101.rhel92026-09-23redhat
redhatpostgresql:15-9040020260917091622.rhel92026-09-23redhat
redhatpostgresql:15-9020020260917092006.rhel92026-09-23redhat
redhatpostgresql:12-8100020260917081510.489197e62026-09-23redhat
redhatpostgresql16-0:16.15-1.el10_22026-09-22redhat
redhatpostgresql:16-8100020260910192321.489197e62026-09-22redhat
redhatpostgresql:15-9080020260903073937.rhel92026-09-22redhat
redhatpostgresql-0:13.23-6.el9_82026-09-22redhat
redhatpostgresql:15-8100020260906175012.489197e62026-09-22redhat
redhatpostgresql:15-9060020260917102335.rhel92026-09-21redhat
redhatpostgresql:18-9080020260914093252.rhel92026-09-16redhat
redhatpostgresql:16-9080020260907191505.rhel92026-09-15redhat
redhatpostgresql18-0:18.6-1.el10_22026-09-14redhat

Patches are aggregated from vendor advisories (Red Hat, Microsoft, Cisco, GitHub) and package ecosystems (OSV, GHSA). Multiple rows for the same upstream release have been deduplicated.

Affected Packages

(15 across 7 ecosystems)
Alpine:v3.21(3)
PackageVulnerable rangeFix by version rangeDependents
postgresql15—
  • every version up to 15.19-r0: fixed in 15.19-r0
—
postgresql16—
  • every version up to 16.15-r0: fixed in 16.15-r0
—
postgresql17—
  • every version up to 17.11-r0: fixed in 17.11-r0
—
Alpine:v3.22(3)
PackageVulnerable rangeFix by version rangeDependents
postgresql15—
  • every version up to 15.19-r0: fixed in 15.19-r0
—
postgresql16—
  • every version up to 16.15-r0: fixed in 16.15-r0
—
postgresql17—
  • every version up to 17.11-r0: fixed in 17.11-r0
—
Alpine:v3.23(3)
PackageVulnerable rangeFix by version rangeDependents
postgresql16—
  • every version up to 16.15-r0: fixed in 16.15-r0
—
postgresql17—
  • every version up to 17.11-r0: fixed in 17.11-r0
—
postgresql18—
  • every version up to 18.5-r0: fixed in 18.5-r0
—
Alpine:v3.24(3)
PackageVulnerable rangeFix by version rangeDependents
postgresql16—
  • every version up to 16.15-r0: fixed in 16.15-r0
—
postgresql17—
  • every version up to 17.11-r0: fixed in 17.11-r0
—
postgresql18—
  • every version up to 18.5-r0: fixed in 18.5-r0
—
Debian:12(1)
PackageVulnerable rangeFix by version rangeDependents
postgresql-1515.10-0+deb12u1 ... 15.9-0+deb12u1 (21 versions)
  • every version up to 15.19-0+deb12u1: fixed in 15.19-0+deb12u1
—
Debian:13(1)
PackageVulnerable rangeFix by version rangeDependents
postgresql-1717.10-0+deb13u1 ... 17.9-0+deb13u1 (7 versions)
  • every version up to 17.11-0+deb13u1: fixed in 17.11-0+deb13u1
—
Debian:14(1)
PackageVulnerable rangeFix by version rangeDependents
postgresql-1818.0-1 ... 18~~devel.20250502-1 (20 versions)
  • every version up to 18.6-1: fixed in 18.6-1
—

Weakness Classification(1)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

Additional Vendor Advisories

(6)

Data Freshness Timeline

(refreshed 9× in last 7d / 40× in last 30d)

Each row is a time one of our pipelines fetched, updated or re-scored this CVE. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed its CVE.org record (CNA or CISA ADP). An arrow marks a change the record states ("CVSS v3 → 9.1"); EPSS and GHSA rows show the values recorded at that time, not what changed (EPSS values are rounded; hover one for the exact figures). "EchelonGraph re-scored" is our own recompute of this CVE's score, not an update from a source, and is not counted in the refreshes above. Most recent first.

Showing the most recent 100 of 346 rows on record for this CVE.

A repeat, a row identical to one the same pipeline wrote less than 10 seconds earlier, is not a separate refresh and is not counted. None are among the latest 100 rows. The 246 oldest rows on record are not shown and were not checked, so the counts can still include repeats.

  1. 2026-11-13 16:51 UTCEPSS rescoreEPSS 0.6% · 49th percentile
  2. 2026-11-12 16:33 UTCEPSS rescoreEPSS 0.6% · 48th percentile
  3. 2026-11-12 01:50 UTCEchelonGraph re-scored
  4. 2026-11-12 01:50 UTCVendor advisory
  5. 2026-11-12 01:50 UTCGHSA enrichmentGHSA-rvq6-xp6x-5575 · GitHub severity HIGH · GitHub CVSS 8.8
  6. 2026-11-11 16:38 UTCEPSS rescoreEPSS 0.6% · 48th percentile
  7. 2026-11-10 16:42 UTCEPSS rescoreEPSS 0.6% · 48th percentile
  8. 2026-11-09 16:34 UTCEPSS rescoreEPSS 0.6% · 48th percentile
  9. 2026-11-08 16:38 UTCEPSS rescoreEPSS 0.6% · 48th percentile
  10. 2026-11-07 16:38 UTCEPSS rescoreEPSS 0.6% · 48th percentile
  11. 2026-11-06 16:36 UTCEPSS rescoreEPSS 0.6% · 48th percentile
  12. 2026-11-05 17:55 UTCEchelonGraph re-scored
  13. 2026-11-05 17:55 UTCVendor advisory
  14. 2026-11-05 17:55 UTCGHSA enrichmentGHSA-rvq6-xp6x-5575 · GitHub severity HIGH · GitHub CVSS 8.8
  15. 2026-11-05 16:36 UTCEPSS rescoreEPSS 0.6% · 48th percentile
  16. 2026-11-04 16:34 UTCEPSS rescoreEPSS 0.6% · 48th percentile
  17. 2026-11-03 16:47 UTCEPSS rescoreEPSS 0.6% · 48th percentile
  18. 2026-11-02 16:44 UTCEPSS rescoreEPSS 0.6% · 48th percentile
  19. 2026-11-01 16:34 UTCEPSS rescoreEPSS 0.6% · 48th percentile
  20. 2026-10-31 16:32 UTCEPSS rescoreEPSS 0.6% · 48th percentile
  21. 2026-10-30 16:33 UTCEPSS rescoreEPSS 0.6% · 48th percentile
  22. 2026-10-30 10:01 UTCEchelonGraph re-scored
  23. 2026-10-30 10:01 UTCVendor advisory
  24. 2026-10-30 10:01 UTCGHSA enrichmentGHSA-rvq6-xp6x-5575 · GitHub severity HIGH · GitHub CVSS 8.8
  25. 2026-10-29 16:32 UTCEPSS rescoreEPSS 0.6% · 48th percentile
Show 75 more
  1. 2026-10-28 16:31 UTCEPSS rescoreEPSS 0.6% · 48th percentile
  2. 2026-10-27 16:31 UTCEPSS rescoreEPSS 0.6% · 48th percentile
  3. 2026-10-26 16:31 UTCEPSS rescoreEPSS 0.6% · 48th percentile
  4. 2026-10-25 16:32 UTCEPSS rescoreEPSS 0.6% · 48th percentile
  5. 2026-10-25 14:47 UTCEchelonGraph re-scored
  6. 2026-10-24 16:32 UTCEPSS rescoreEPSS 0.6% · 45th percentile
  7. 2026-10-24 02:06 UTCEchelonGraph re-scored
  8. 2026-10-24 02:06 UTCVendor advisory
  9. 2026-10-24 02:05 UTCGHSA enrichmentGHSA-rvq6-xp6x-5575 · GitHub severity HIGH · GitHub CVSS 8.8
  10. 2026-10-23 16:31 UTCEPSS rescoreEPSS 0.6% · 45th percentile
  11. 2026-10-22 16:33 UTCEPSS rescoreEPSS 0.6% · 45th percentile
  12. 2026-10-21 16:32 UTCEPSS rescoreEPSS 0.6% · 45th percentile
  13. 2026-10-20 16:32 UTCEPSS rescoreEPSS 0.6% · 45th percentile
  14. 2026-10-19 16:31 UTCEPSS rescoreEPSS 0.6% · 45th percentile
  15. 2026-10-18 16:31 UTCEPSS rescoreEPSS 0.6% · 45th percentile
  16. 2026-10-18 04:01 UTCEchelonGraph re-scored
  17. 2026-10-17 18:10 UTCEchelonGraph re-scored
  18. 2026-10-17 18:10 UTCVendor advisory
  19. 2026-10-17 18:09 UTCGHSA enrichmentGHSA-rvq6-xp6x-5575 · GitHub severity HIGH · GitHub CVSS 8.8
  20. 2026-10-17 16:33 UTCEPSS rescoreEPSS 0.6% · 45th percentile
  21. 2026-10-16 16:40 UTCEPSS rescoreEPSS 0.6% · 45th percentile
  22. 2026-10-15 16:31 UTCEPSS rescoreEPSS 0.6% · 45th percentile
  23. 2026-10-14 16:32 UTCEPSS rescoreEPSS 0.6% · 44th percentile
  24. 2026-10-13 16:33 UTCEPSS rescoreEPSS 0.6% · 44th percentile
  25. 2026-10-12 16:33 UTCEPSS rescoreEPSS 0.6% · 44th percentile
  26. 2026-10-12 16:31 UTCEchelonGraph re-scored
  27. 2026-10-11 20:09 UTCEchelonGraph re-scored
  28. 2026-10-11 17:22 UTCEchelonGraph re-scored
  29. 2026-10-11 14:55 UTCEchelonGraph re-scored
  30. 2026-10-11 13:48 UTCEPSS rescoreEPSS 0.6% · 44th percentile
  31. 2026-10-10 19:59 UTCEPSS rescoreEPSS 0.6% · 44th percentile
  32. 2026-10-09 20:06 UTCEPSS rescoreEPSS 0.6% · 44th percentile
  33. 2026-10-08 17:11 UTCEPSS rescoreEPSS 0.6% · 44th percentile
  34. 2026-10-07 23:47 UTCEPSS rescoreEPSS 0.6% · 44th percentile
  35. 2026-10-07 01:21 UTCEchelonGraph re-scored
  36. 2026-10-07 01:21 UTCVendor advisory
  37. 2026-10-07 01:21 UTCGHSA enrichmentGHSA-rvq6-xp6x-5575 · GitHub severity HIGH · GitHub CVSS 8.8
  38. 2026-10-06 15:17 UTCEPSS rescoreEPSS 0.6% · 44th percentile
  39. 2026-10-06 13:53 UTCEchelonGraph re-scored
  40. 2026-10-06 13:53 UTCVendor advisory
  41. 2026-10-06 13:53 UTCGHSA enrichmentGHSA-rvq6-xp6x-5575 · GitHub severity HIGH · GitHub CVSS 8.8
  42. 2026-10-05 17:42 UTCEPSS rescoreEPSS 0.6% · 44th percentile
  43. 2026-10-05 14:41 UTCEchelonGraph re-scored
  44. 2026-10-05 14:41 UTCVendor advisory
  45. 2026-10-05 14:41 UTCGHSA enrichmentGHSA-rvq6-xp6x-5575 · GitHub severity HIGH · GitHub CVSS 8.8
  46. 2026-10-04 23:21 UTCEPSS rescoreEPSS 0.6% · 44th percentile
  47. 2026-10-04 22:24 UTCVendor advisory
  48. 2026-10-04 22:24 UTCGHSA enrichmentGHSA-rvq6-xp6x-5575 · GitHub severity HIGH · GitHub CVSS 8.8
  49. 2026-10-04 07:20 UTCVendor advisory
  50. 2026-10-04 07:20 UTCGHSA enrichmentGHSA-rvq6-xp6x-5575 · GitHub severity HIGH · GitHub CVSS 8.8
  51. 2026-10-03 19:52 UTCEchelonGraph re-scored
  52. 2026-10-03 19:52 UTCVendor advisory
  53. 2026-10-03 19:52 UTCGHSA enrichmentGHSA-rvq6-xp6x-5575 · GitHub severity HIGH · GitHub CVSS 8.8
  54. 2026-10-03 14:25 UTCEPSS rescoreEPSS 0.6% · 44th percentile
  55. 2026-10-02 19:33 UTCEchelonGraph re-scored
  56. 2026-10-02 19:33 UTCVendor advisory
  57. 2026-10-02 19:33 UTCGHSA enrichmentGHSA-rvq6-xp6x-5575 · GitHub severity HIGH · GitHub CVSS 8.8
  58. 2026-10-02 08:05 UTCEchelonGraph re-scored
  59. 2026-10-02 08:05 UTCVendor advisory
  60. 2026-10-02 08:04 UTCGHSA enrichmentGHSA-rvq6-xp6x-5575 · GitHub severity HIGH · GitHub CVSS 8.8
  61. 2026-10-01 19:49 UTCEPSS rescoreEPSS 0.6% · 44th percentile
  62. 2026-10-01 09:19 UTCVendor advisory
  63. 2026-10-01 09:19 UTCGHSA enrichmentGHSA-rvq6-xp6x-5575 · GitHub severity HIGH · GitHub CVSS 8.8
  64. 2026-09-30 21:50 UTCEchelonGraph re-scored
  65. 2026-09-30 21:50 UTCVendor advisory
  66. 2026-09-30 21:50 UTCGHSA enrichmentGHSA-rvq6-xp6x-5575 · GitHub severity HIGH · GitHub CVSS 8.8
  67. 2026-09-30 15:02 UTCEPSS rescoreEPSS 0.6% · 44th percentile
  68. 2026-09-29 15:20 UTCEPSS rescoreEPSS 0.6% · 44th percentile
  69. 2026-09-29 04:14 UTCEchelonGraph re-scored
  70. 2026-09-29 04:14 UTCVendor advisory
  71. 2026-09-29 04:14 UTCGHSA enrichmentGHSA-rvq6-xp6x-5575 · GitHub severity HIGH · GitHub CVSS 8.8
  72. 2026-09-28 13:51 UTCEPSS rescoreEPSS 0.6% · 44th percentile
  73. 2026-09-28 12:29 UTCVendor advisory
  74. 2026-09-28 12:29 UTCGHSA enrichmentGHSA-rvq6-xp6x-5575 · GitHub severity HIGH · GitHub CVSS 8.8
  75. 2026-09-28 01:01 UTCEchelonGraph re-scored

Frequently asked(5)

What is CVE-2026-15742?
CVE-2026-15742 is a high-severity vulnerability; its CVE record was published on August 13, 2026. Integer wraparound in PostgreSQL fuzzystrmatch allows a user to direct writes to a huge range of addresses, executing arbitrary code as the operating system user running the database, via extreme inputs to SQL function levenshtein() or levenshtein_less_equal(). Versions before PostgreSQL 18.6,…
When was the CVE record for CVE-2026-15742 published?
The CVE record for CVE-2026-15742 was published on August 13, 2026. That is the record's publication date; the vulnerability itself may have been made public earlier. EchelonGraph's copy of the record carries a last-modified date of August 29, 2026; the record at its source may have been updated since.
Is CVE-2026-15742 actively exploited?
CVE-2026-15742 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.6% probability of exploitation in the next 30 days (49th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-15742?
CVE-2026-15742 has a CVSS base score of 8.8 (a secondary CVSS source that NVD displays; NVD's own analysis pending).
How do I remediate CVE-2026-15742?
A fix for CVE-2026-15742 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2026-15742 are linked in the Vendor Advisories panel on this page.

Dependency Blast Radius

See which npm, PyPI, Go, and Maven packages are affected by CVE-2026-15742

Explore →

Is Your Infrastructure Affected by CVE-2026-15742?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.