CVE-2026-89157

HIGHNVD 7.47.4—
EchelonGraph scoreMEDIUM confidence

This high-severity CVE scores 7.4 under NVD CVSS v3. EPSS exploit probability: 0.2%, top 88% of all CVEs by exploit prediction. GitHub Security Advisory enrichment pending alignment with NVD CVSS.

Triggered by: NVD CVSS baseline
Sources: epss, ghsa, nvd
Trending — 5 sources updated this weekElevated
7.4EG
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 0%CVSS: 7.4Exploit: Elevated riskExposed: 0

No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.

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.4(medium)
EG Risk
49(Track)
EG Risk 49/100SSVC: Track

EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).

How it’s computed
Severity74% × 45%
Exploitation40% × 40%
Automatability0% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
0%
EPSS %ILE
12%
KEV
Not listed

Published

September 11, 2026

Last Modified

September 16, 2026

Advisory Details (2)

Auto-updated Sep 11, 2026
🔬 Proof of concept available. Patch available. Sources: github_release, github.
github Patch Available🟡 PoC Available

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

Vendor Advisories for CVE-2026-89157(1)

These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.

Weakness Classification(1)

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

All Vendor Advisories

(1)

Every vendor that published an advisory referencing this CVE — pulled from our cve_vendor_advisories aggregation. Click any row for the vendor's original advisory page.

Data Freshness Timeline

(refreshed 41× in last 7d / 57× in last 30d)

Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.

  1. 2026-09-21 02:22 UTCEG score recompute
  2. 2026-09-21 02:22 UTCVendor advisory
  3. 2026-09-21 02:22 UTCGHSA enrichment
  4. 2026-09-20 20:16 UTCEPSS rescore
  5. 2026-09-20 15:08 UTCVendor advisory
  6. 2026-09-20 15:08 UTCGHSA enrichment
  7. 2026-09-20 03:55 UTCVendor advisory
  8. 2026-09-20 03:55 UTCGHSA enrichment
  9. 2026-09-19 16:41 UTCEG score recompute
  10. 2026-09-19 16:41 UTCVendor advisory
  11. 2026-09-19 16:41 UTCGHSA enrichment
  12. 2026-09-19 05:27 UTCEG score recompute
  13. 2026-09-19 05:27 UTCVendor advisory
  14. 2026-09-19 05:27 UTCGHSA enrichment
  15. 2026-09-18 19:28 UTCEPSS rescore
  16. 2026-09-18 18:14 UTCVendor advisory
  17. 2026-09-18 18:14 UTCGHSA enrichment
  18. 2026-09-18 06:58 UTCVendor advisory
  19. 2026-09-18 06:58 UTCGHSA enrichment
  20. 2026-09-17 19:44 UTCEG score recompute
  21. 2026-09-17 19:44 UTCVendor advisory
  22. 2026-09-17 19:44 UTCGHSA enrichment
  23. 2026-09-17 19:32 UTCEPSS rescore
  24. 2026-09-17 06:51 UTCVendor advisory
  25. 2026-09-17 06:51 UTCGHSA enrichment
Show 32 more
  1. 2026-09-16 19:37 UTCEG score recompute▲ 1.70
  2. 2026-09-16 19:37 UTCVendor advisory
  3. 2026-09-16 19:37 UTCGHSA enrichment
  4. 2026-09-16 19:31 UTCNVD updateCVSS v3 → 7.4 · severity → HIGH
  5. 2026-09-16 18:07 UTCEG score recompute
  6. 2026-09-16 18:07 UTCVendor advisory
  7. 2026-09-16 18:07 UTCGHSA enrichment
  8. 2026-09-16 14:09 UTCEPSS rescore
  9. 2026-09-16 05:15 UTCEPSS rescore
  10. 2026-09-15 16:38 UTCEG score recompute
  11. 2026-09-15 16:38 UTCVendor advisory
  12. 2026-09-15 16:38 UTCGHSA enrichment
  13. 2026-09-15 03:12 UTCEPSS rescore
  14. 2026-09-14 16:36 UTCEG score recompute
  15. 2026-09-14 16:36 UTCVendor advisory
  16. 2026-09-14 16:36 UTCGHSA enrichment
  17. 2026-09-13 16:48 UTCEPSS rescore
  18. 2026-09-13 16:34 UTCVendor advisory
  19. 2026-09-13 16:34 UTCGHSA enrichment
  20. 2026-09-12 16:32 UTCEG score recompute
  21. 2026-09-12 16:32 UTCGHSA enrichment
  22. 2026-09-11 16:30 UTCEG score recompute
  23. 2026-09-11 16:30 UTCGHSA enrichment
  24. 2026-09-11 16:09 UTCEG score recompute
  25. 2026-09-11 16:09 UTCGHSA enrichment
  26. 2026-09-11 15:07 UTCEG score recompute
  27. 2026-09-11 15:07 UTCGHSA enrichment
  28. 2026-09-11 14:53 UTCEPSS rescore
  29. 2026-09-11 14:53 UTCEPSS rescore
  30. 2026-09-11 04:20 UTCEG score recompute
  31. 2026-09-11 04:15 UTCEG score recompute
  32. 2026-09-11 04:14 UTCMITRE cvelistV5first tracked

Related CVEs(same CWE)

Frequently asked(5)

What is CVE-2026-89157?
CVE-2026-89157 is a high vulnerability published on September 11, 2026. PCRE2 before 10.48, on 32-bit platforms, has a pcre2patternconvert out-of-bounds write when an attacker can provide a large pattern.
When was CVE-2026-89157 disclosed?
CVE-2026-89157 was first published in the National Vulnerability Database on September 11, 2026, with the most recent update on September 16, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-89157 actively exploited?
CVE-2026-89157 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0% probability of exploitation in the next 30 days, which ranks it in the top 88.0% of all 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?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-89157, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

Dependency Blast Radius

Explore the affected products and dependency analysis for 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.

Start Free Scan →Browse All CVEs