CVE-2026-89160

MEDIUMNVD 6.56.5—
EchelonGraph scoreMEDIUM confidence

This medium-severity CVE scores 6.5 under NVD CVSS v3. EPSS exploit probability: 0.3% (17th percentile of EPSS-scored CVEs). GitHub Security Advisory enrichment pending alignment with NVD CVSS.

Triggered by: NVD CVSS baseline
Sources: epss, ghsa, nvd
Trending — 4 sources updated this weekElevated
6.5EG
EchelonGraph verdictMonitorLow exploitation likelihood right now — keep watching.
  • Lower severity and no public exploit yet
CISA-KEV: Not listedEPSS PROB: 0.3%CVSS: 6.5Exploit: Elevated riskExposed services: Not assessed

A fix is available — apply it.

PCRE2 before 10.48 has a pcre2_match out-of-bounds read during the PCRE2_MATCH_INVALID_UTF matching of an invalid UTF subject.

CVSS v3
6.5
EG Score
6.5MEDIUMmedium confidence
EG Risk
45
EG Risk 45/100CISA SSVC

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%
Exploitation40% × 40%
Automatability0% × 15%
CISA SSVC: Track at low or medium mission impact; Track* at high (mission-essential systems).
Action: A fix is available. Apply it within your standard update timelines.
EPSS PROB
0.3%
EPSS %ILE
17th
KEV
Not listed

CISA SSVCTrack 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). Mission impact is CISA's Mission & Well-being decision point, and only you can judge it: high means the affected system is essential to your organisation's mission, or its compromise could cause irreversible harm to people. CISA's decision table

Published

September 11, 2026

Last Modified

September 16, 2026

Advisory Details (2)

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

PCRE2: out-of-bounds reads in pcre2_match() when matching invalid UTF subjects with PCRE2_MATCH_INVALID_UTF · Advisory · PCRE2Project/pcre2 · GitHub

Affected: 10.48

https://github.com/PCRE2Project/pcre2/security/advisories/GHSA-9qww-pwc4-77qq
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-89160(3)

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

Patch Availability(1)

Vendor / EcosystemFix (by version range) / PatchReleasedSource
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

(5 across 5 ecosystems)
Alpine:v3.23(1)
PackageVulnerable rangeFix by version rangeDependents
pcre2—
  • 10.34 up to 10.48-r0: fixed in 10.48-r0
—
Alpine:v3.24(1)
PackageVulnerable rangeFix by version rangeDependents
pcre2—
  • 10.34 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.

Data Freshness Timeline

(refreshed 24× in last 7d / 93× 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-10-04 23:22 UTCEPSS rescore
  2. 2026-10-04 16:43 UTCVendor advisory
  3. 2026-10-04 16:43 UTCGHSA enrichment
  4. 2026-10-03 18:57 UTCEG score recompute
  5. 2026-10-03 18:57 UTCVendor advisory
  6. 2026-10-03 18:56 UTCGHSA enrichment
  7. 2026-10-02 20:49 UTCEG score recompute
  8. 2026-10-02 20:49 UTCVendor advisory
  9. 2026-10-02 20:49 UTCGHSA enrichment
  10. 2026-10-01 22:36 UTCEG score recompute
  11. 2026-10-01 22:36 UTCVendor advisory
  12. 2026-10-01 22:36 UTCGHSA enrichment
  13. 2026-10-01 19:51 UTCEPSS rescore
  14. 2026-10-01 00:48 UTCEG score recompute
  15. 2026-10-01 00:48 UTCVendor advisory
  16. 2026-10-01 00:48 UTCGHSA enrichment
  17. 2026-09-30 15:04 UTCEPSS rescore
  18. 2026-09-30 01:51 UTCEG score recompute
  19. 2026-09-30 01:51 UTCVendor advisory
  20. 2026-09-30 01:51 UTCGHSA enrichment
  21. 2026-09-28 20:20 UTCEG score recompute
  22. 2026-09-28 20:20 UTCVendor advisory
  23. 2026-09-28 20:20 UTCGHSA enrichment
  24. 2026-09-28 13:52 UTCEPSS rescore
  25. 2026-09-27 21:24 UTCEG score recompute
Show 68 more
  1. 2026-09-27 21:24 UTCVendor advisory
  2. 2026-09-27 21:24 UTCGHSA enrichment
  3. 2026-09-27 13:48 UTCEPSS rescore
  4. 2026-09-26 23:38 UTCEG score recompute
  5. 2026-09-26 23:38 UTCVendor advisory
  6. 2026-09-26 23:38 UTCGHSA enrichment
  7. 2026-09-26 15:59 UTCEPSS rescore
  8. 2026-09-26 01:24 UTCEG score recompute
  9. 2026-09-26 01:24 UTCVendor advisory
  10. 2026-09-26 01:24 UTCGHSA enrichment
  11. 2026-09-25 02:31 UTCEG score recompute
  12. 2026-09-25 02:31 UTCVendor advisory
  13. 2026-09-25 02:31 UTCGHSA enrichment
  14. 2026-09-24 14:04 UTCEPSS rescore
  15. 2026-09-24 04:44 UTCEG score recompute
  16. 2026-09-24 04:44 UTCVendor advisory
  17. 2026-09-24 04:44 UTCGHSA enrichment
  18. 2026-09-23 17:54 UTCEPSS rescore
  19. 2026-09-23 06:57 UTCEG score recompute
  20. 2026-09-23 06:57 UTCVendor advisory
  21. 2026-09-23 06:57 UTCGHSA enrichment
  22. 2026-09-22 16:01 UTCEPSS rescore
  23. 2026-09-22 09:10 UTCEG score recompute
  24. 2026-09-22 09:10 UTCVendor advisory
  25. 2026-09-22 09:10 UTCGHSA enrichment
  26. 2026-09-21 21:09 UTCEPSS rescore
  27. 2026-09-21 11:04 UTCEG score recompute
  28. 2026-09-21 11:04 UTCVendor advisory
  29. 2026-09-21 11:04 UTCGHSA enrichment
  30. 2026-09-20 20:16 UTCEPSS rescore
  31. 2026-09-20 13:17 UTCEG score recompute
  32. 2026-09-20 13:17 UTCVendor advisory
  33. 2026-09-20 13:17 UTCGHSA enrichment
  34. 2026-09-19 15:17 UTCEG score recompute
  35. 2026-09-19 15:17 UTCVendor advisory
  36. 2026-09-19 15:17 UTCGHSA enrichment
  37. 2026-09-18 19:28 UTCEPSS rescore
  38. 2026-09-18 17:31 UTCVendor advisory
  39. 2026-09-18 17:31 UTCGHSA enrichment
  40. 2026-09-17 19:44 UTCEG score recompute
  41. 2026-09-17 19:44 UTCVendor advisory
  42. 2026-09-17 19:44 UTCGHSA enrichment
  43. 2026-09-17 19:32 UTCEPSS rescore
  44. 2026-09-16 19:23 UTCEG score recompute▲ 2.80
  45. 2026-09-16 19:23 UTCVendor advisory
  46. 2026-09-16 19:23 UTCGHSA enrichment
  47. 2026-09-16 19:22 UTCNVD updateCVSS v3 → 6.5 · severity → MEDIUM
  48. 2026-09-16 14:09 UTCEPSS rescore
  49. 2026-09-16 05:15 UTCEPSS rescore
  50. 2026-09-15 16:34 UTCEG score recompute
  51. 2026-09-15 16:34 UTCVendor advisory
  52. 2026-09-15 16:34 UTCGHSA enrichment
  53. 2026-09-15 15:43 UTCEG score recompute
  54. 2026-09-15 15:43 UTCVendor advisory
  55. 2026-09-15 15:43 UTCGHSA enrichment
  56. 2026-09-15 03:12 UTCEPSS rescore
  57. 2026-09-14 19:33 UTCEG score recompute
  58. 2026-09-14 19:33 UTCVendor advisory
  59. 2026-09-14 19:33 UTCGHSA enrichment
  60. 2026-09-13 16:48 UTCEPSS rescore
  61. 2026-09-12 15:02 UTCEPSS rescore
  62. 2026-09-11 15:07 UTCEG score recompute
  63. 2026-09-11 15:07 UTCGHSA enrichment
  64. 2026-09-11 14:53 UTCEPSS rescore
  65. 2026-09-11 14:53 UTCEPSS rescore
  66. 2026-09-11 04:20 UTCEG score recompute
  67. 2026-09-11 04:15 UTCEG score recompute
  68. 2026-09-11 04:14 UTCMITRE cvelistV5first tracked

Related CVEs(same vendor + same CWE)

Frequently asked(5)

What is CVE-2026-89160?
CVE-2026-89160 is a medium vulnerability published on September 11, 2026. PCRE2 before 10.48 has a pcre2match out-of-bounds read during the PCRE2MATCHINVALIDUTF matching of an invalid UTF subject.
When was CVE-2026-89160 disclosed?
CVE-2026-89160 was first published 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-89160 actively exploited?
CVE-2026-89160 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.3% probability of exploitation in the next 30 days (17th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-89160?
CVE-2026-89160 has a CVSS v3 base score of 6.5 (NVD).
How do I remediate CVE-2026-89160?
A fix for CVE-2026-89160 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2026-89160 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-89160

Explore →

Is Your Infrastructure Affected by CVE-2026-89160?

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

Book a Demo →Browse All CVEs