CVE-2026-89157

HIGHNVD 7.47.4
EchelonGraph scoreMEDIUM confidence

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

This high-severity CVE scores 7.4 under NVD CVSS v3. EPSS exploit probability: 0.3% (28th percentile of EPSS-scored CVEs). GitHub Security Advisory CVSS 5.7 is lower than this score; a lower GitHub score revises it only when its advisory is newer than the CVE record's last change, and this advisory (published 2026-09-11) is not newer than that change (2026-09-16), so it does not.

Triggered by: Headline CVSS from NVD CVSS v3
Sources: EPSS, GitHub Security Advisory, NVD CVSS v3
Elevated

Also known asEUVD-2026-75943 (ENISA EUVD) · GHSA-797w-fgfq-r75v (GitHub Security Advisories)Source: ENISA EUVD

7.4EG
EchelonGraph verdictPlan a fixRemediate within your standard update timelines (the SSVC decision on this page).
  • CISA's Vulnrichment rates exploitation as PoC; EchelonGraph holds no exploit-code reference for it
CISA-KEV: Not listedEPSS PROB: 0.3%CVSS: 7.4Exploit: No code on recordExposed services: Not assessed

A fix is available — apply it.

PCRE2 before 10.48, on 32-bit platforms, has a pcre2_pattern_convert out-of-bounds write when an attacker can provide a large pattern.

CVSS v3
7.4
EG Score
7.4HIGHmedium confidence
EG Risk
49
EG Risk 49/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)
Severity74% × 45%
Impact severity (EG Severity): CVSS 7.4 of 10. Never the KEV-floored or EPSS-lifted EG Score.
Exploitation40% × 40%
EchelonGraph's fixed weight for EG-KEV Tier 3 (Elevated): a constant, not a probability.
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 public PoC (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact partial (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.3%
EPSS %ILE
28th
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 (7.4): severity, escalated by confirmed exploitation. This CVE's 7.4 is its impact severity (EG Severity), not escalated.

EG Severity
7.4 HIGHCVSS-B, impact only: no KEV listing, EPSS or EG-KEV tier raises it.NVD CVSS v3 · CVSS v3.0 or v3.1
EG Likelihood
0.3% within 30 daysSource: FIRST EPSS (model v2026.06.15, score date 2026-11-10). 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: 60 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 public PoC (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact partial (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)60 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 partial (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

September 11, 2026

Last Modified

September 16, 2026

Advisory Details (2)

Auto-updated Sep 11, 2026
Patch available. Sources: github_release, github.
GitHub advisoryMentions a patch (unverified)

PCRE2: out-of-bounds write in pcre2_pattern_convert() with large patterns on 32-bit systems · Advisory · PCRE2Project/pcre2 · GitHub

Affected: 10.48

https://github.com/PCRE2Project/pcre2/security/advisories/GHSA-q8g2-wprr-34m9
GitHub release Patch Available

PCRE2 10.48

Patch available: PCRE2Project/pcre2 pcre2-10.48

https://github.com/PCRE2Project/pcre2/releases/tag/pcre2-10.48

Patch Availability(8)

Vendor / EcosystemFix (by version range) / PatchReleasedSource
ubuntupcre2-utils (10.46-1ubuntu0.1) @ resolute2026-11-11ubuntu
redhatcostmanagement/costmanagement-metrics-rhel9-operator:17932026622026-11-04redhat
redhatcostmanagement/costmanagement-ui-rhel10:17926052722026-10-21redhat
redhatrhui5/rhua-rhel9:17919786932026-10-14redhat
redhatpcre2-0:10.32-4.el8_102026-10-13redhat
redhatpcre2-0:10.40-7.el9_82026-10-12redhat
redhatpcre2-0:10.44-1.5.el10_22026-10-12redhat
redhatpcre2-main-10.48-0.1.hum12026-09-15redhat

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

(7 across 7 ecosystems)
Alpine:v3.21(1)
PackageVulnerable rangeFix by version rangeDependents
pcre2—
  • 10.30 up to 10.43-r1: fixed in 10.43-r1
—
Alpine:v3.22(1)
PackageVulnerable rangeFix by version rangeDependents
pcre2—
  • 10.30 up to 10.46-r1: fixed in 10.46-r1
—
Alpine:v3.23(1)
PackageVulnerable rangeFix by version rangeDependents
pcre2—
  • 10.30 up to 10.48-r0: fixed in 10.48-r0
—
Alpine:v3.24(1)
PackageVulnerable rangeFix by version rangeDependents
pcre2—
  • 10.30 up to 10.48-r0: fixed in 10.48-r0
—
Debian:12(1)
PackageVulnerable rangeFix by version rangeDependents
pcre210.42-1
  • every version up to 10.42-1+deb12u1: fixed in 10.42-1+deb12u1
—
Debian:13(1)
PackageVulnerable rangeFix by version rangeDependents
pcre210.45-1, 10.46-1~deb13u1
  • every version up to 10.46-1~deb13u2: fixed in 10.46-1~deb13u2
—
Debian:14(1)
PackageVulnerable rangeFix by version rangeDependents
pcre210.45-1 ... 10.47-2 (7 versions)
  • every version up to 10.48-1: fixed in 10.48-1
—

Weakness Classification(1)

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

Additional Vendor Advisories

(1)

Vendors that published advisories for this CVE beyond the curated set above. Broader coverage but minimal per-row detail — click through for the original advisory.

Data Freshness Timeline

(refreshed 9× in last 7d / 38× 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 232 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 132 oldest rows on record are not shown and were not checked, so the counts can still include repeats.

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

Frequently asked(5)

What is CVE-2026-89157?
CVE-2026-89157 is a high-severity vulnerability; its CVE record was published on September 11, 2026. PCRE2 before 10.48, on 32-bit platforms, has a pcre2_pattern_convert out-of-bounds write when an attacker can provide a large pattern.
When was the CVE record for CVE-2026-89157 published?
The CVE record for CVE-2026-89157 was published on September 11, 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 September 16, 2026; the record at its source may have been updated since.
Is CVE-2026-89157 actively exploited?
CVE-2026-89157 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.3% probability of exploitation in the next 30 days (28th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-89157?
CVE-2026-89157 has a CVSS v3 base score of 7.4 (NVD).
How do I remediate CVE-2026-89157?
A fix for CVE-2026-89157 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2026-89157 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-89157

Explore →

Is Your Infrastructure Affected by CVE-2026-89157?

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