CVE-2026-89158

MEDIUMNVD 6.56.5
EchelonGraph scoreHIGH confidence

Score 6.5 from GitHub Security Advisory published 2026-09-11. NVD baseline CVSS 6.5; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: epss, ghsa, nvd
Trending — 4 sources updated this week
6.5EG
EchelonGraph verdictMonitorLow exploitation likelihood right now — keep watching.
  • Lower severity and no public exploit yet
CISA-KEV: Not listedEPSS PROB: 0%CVSS: 6.5Exploit: None knownExposed: 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_compile_32 integer overflow and resultant out-of-bounds write.

CVSS v3
6.5
EG Score
6.5(high)
EG Risk
29(Track)
EG Risk 29/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
Severity65% × 45%
Exploitation0% × 40%
Automatability0% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
0%
EPSS %ILE
13%
KEV
Not listed

Published

September 11, 2026

Last Modified

September 16, 2026

Advisory Details (2)

Auto-updated Sep 11, 2026
Patch available. Sources: github_release, github.
github Patch Available

PCRE2: integer overflow in pcre2_compile_32() causes out-of-bounds write on 32-bit systems · Advisory · PCRE2Project/pcre2 · GitHub

Affected: 10.48

https://github.com/PCRE2Project/pcre2/security/advisories/GHSA-fmgr-6ggq-9859
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-89158(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 25× in last 7d / 44× 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-20 20:16 UTCEPSS rescore
  2. 2026-09-20 14:00 UTCVendor advisory
  3. 2026-09-20 14:00 UTCGHSA enrichment
  4. 2026-09-19 15:58 UTCEG score recompute
  5. 2026-09-19 15:58 UTCVendor advisory
  6. 2026-09-19 15:58 UTCGHSA enrichment
  7. 2026-09-18 19:28 UTCEPSS rescore
  8. 2026-09-18 17:47 UTCVendor advisory
  9. 2026-09-18 17:47 UTCGHSA enrichment
  10. 2026-09-17 19:44 UTCEG score recompute
  11. 2026-09-17 19:44 UTCVendor advisory
  12. 2026-09-17 19:44 UTCGHSA enrichment
  13. 2026-09-17 19:32 UTCEPSS rescore
  14. 2026-09-16 19:37 UTCEG score recompute
  15. 2026-09-16 19:37 UTCVendor advisory
  16. 2026-09-16 19:37 UTCGHSA enrichment
  17. 2026-09-16 14:09 UTCEPSS rescore
  18. 2026-09-16 05:42 UTCEG score recompute
  19. 2026-09-16 05:42 UTCVendor advisory
  20. 2026-09-16 05:42 UTCGHSA enrichment
  21. 2026-09-16 05:15 UTCEPSS rescore
  22. 2026-09-15 07:39 UTCEG score recompute
  23. 2026-09-15 07:39 UTCVendor advisory
  24. 2026-09-15 07:39 UTCGHSA enrichment
  25. 2026-09-15 03:12 UTCEPSS rescore
Show 19 more
  1. 2026-09-14 09:36 UTCEG score recompute
  2. 2026-09-14 09:36 UTCVendor advisory
  3. 2026-09-14 09:36 UTCGHSA enrichment
  4. 2026-09-13 16:48 UTCEPSS rescore
  5. 2026-09-13 11:34 UTCEG score recompute
  6. 2026-09-13 11:34 UTCVendor advisory
  7. 2026-09-13 11:34 UTCGHSA enrichment
  8. 2026-09-12 15:02 UTCEPSS rescore
  9. 2026-09-12 13:32 UTCGHSA enrichment
  10. 2026-09-11 15:29 UTCGHSA enrichment
  11. 2026-09-11 15:07 UTCEG score recompute
  12. 2026-09-11 15:07 UTCGHSA enrichment
  13. 2026-09-11 14:53 UTCEPSS rescore
  14. 2026-09-11 14:53 UTCEPSS rescore
  15. 2026-09-11 14:20 UTCEG score recompute
  16. 2026-09-11 14:20 UTCGHSA enrichment
  17. 2026-09-11 04:20 UTCEG score recompute
  18. 2026-09-11 04:15 UTCEG score recompute
  19. 2026-09-11 04:14 UTCMITRE cvelistV5first tracked

Frequently asked(5)

What is CVE-2026-89158?
CVE-2026-89158 is a medium vulnerability published on September 11, 2026. PCRE2 before 10.48, on 32-bit platforms, has a pcre2compile32 integer overflow and resultant out-of-bounds write.
When was CVE-2026-89158 disclosed?
CVE-2026-89158 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-89158 actively exploited?
CVE-2026-89158 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 87.0% of all scored CVEs.
What is the CVSS score of CVE-2026-89158?
CVE-2026-89158 has a CVSS v3 base score of 6.5 (NVD).
How do I remediate CVE-2026-89158?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-89158, 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-89158

Explore →

Is Your Infrastructure Affected by CVE-2026-89158?

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