CVE-2026-86145

HIGHPre-NVD 8.28.2—
EchelonGraph scoreHIGH confidence

Score 8.2 from GitHub Security Advisory (severity: HIGH) published 2026-09-05. a secondary CVSS source baseline 8.2; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: epss, ghsa, secondary
Trending — 4 sources updated this week
8.2EG
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 0%CVSS: 8.2Exploit: 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 allows a pcre2_dfa_match out-of-bounds write because reuse of a cached workspace block, in a recursive DFA matching workspace, lacks a size check (even though a newly allocated block, for the same purpose, does have a size check). This outcome requires an attacker-controlled regular expression, or a recursive pattern in conjunction with a small heap limit (this can be set through the API).

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

Published

September 5, 2026

Last Modified

September 9, 2026

Advisory Details (2)

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

PCRE2 10.48

Patch available: PCRE2Project/pcre2 pcre2-10.48

https://github.com/PCRE2Project/pcre2/releases/tag/pcre2-10.48
github Patch Available🟡 PoC Available

PCRE2: out-of-bounds write in pcre2_dfa_match() with recursive patterns under a low heap limit · Advisory · PCRE2Project/pcre2 · GitHub

Affected: 10.48

https://github.com/PCRE2Project/pcre2/security/advisories/GHSA-3r4p-g7gg-ppmf

Vendor Advisories for CVE-2026-86145(2)

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

Affected Packages

(3 across 3 ecosystems)
Debian:12(1)
PackageVulnerable rangeFixed inDependents
pcre210.42-110.42-1+deb12u1—
Debian:13(1)
PackageVulnerable rangeFixed inDependents
pcre210.45-1 ... 10.48-2 (8 versions)——
Debian:14(1)
PackageVulnerable rangeFixed inDependents
pcre210.45-1 ... 10.48-2 (8 versions)——

Weakness Classification(1)

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

Data Freshness Timeline

(refreshed 41× in last 7d / 76× 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-18 22:26 UTCEG score recompute
  2. 2026-09-18 22:26 UTCVendor advisory
  3. 2026-09-18 22:26 UTCGHSA enrichment
  4. 2026-09-18 19:28 UTCEPSS rescore
  5. 2026-09-18 10:10 UTCVendor advisory
  6. 2026-09-18 10:10 UTCGHSA enrichment
  7. 2026-09-17 21:53 UTCEG score recompute
  8. 2026-09-17 21:53 UTCVendor advisory
  9. 2026-09-17 21:53 UTCGHSA enrichment
  10. 2026-09-17 19:32 UTCEPSS rescore
  11. 2026-09-17 09:36 UTCVendor advisory
  12. 2026-09-17 09:36 UTCGHSA enrichment
  13. 2026-09-16 21:19 UTCEG score recompute
  14. 2026-09-16 21:19 UTCVendor advisory
  15. 2026-09-16 21:19 UTCGHSA enrichment
  16. 2026-09-16 14:09 UTCEPSS rescore
  17. 2026-09-16 09:00 UTCEG score recompute
  18. 2026-09-16 09:00 UTCVendor advisory
  19. 2026-09-16 09:00 UTCGHSA enrichment
  20. 2026-09-16 05:15 UTCEPSS rescore
  21. 2026-09-15 19:43 UTCVendor advisory
  22. 2026-09-15 19:43 UTCGHSA enrichment
  23. 2026-09-15 07:24 UTCEG score recompute
  24. 2026-09-15 07:24 UTCVendor advisory
  25. 2026-09-15 07:24 UTCGHSA enrichment
Show 51 more
  1. 2026-09-15 03:12 UTCEPSS rescore
  2. 2026-09-15 03:12 UTCEPSS rescore
  3. 2026-09-14 19:07 UTCVendor advisory
  4. 2026-09-14 19:07 UTCGHSA enrichment
  5. 2026-09-14 06:50 UTCVendor advisory
  6. 2026-09-14 06:50 UTCGHSA enrichment
  7. 2026-09-13 18:33 UTCEG score recompute
  8. 2026-09-13 18:33 UTCVendor advisory
  9. 2026-09-13 18:33 UTCGHSA enrichment
  10. 2026-09-13 06:16 UTCVendor advisory
  11. 2026-09-13 06:16 UTCGHSA enrichment
  12. 2026-09-12 17:59 UTCEG score recompute
  13. 2026-09-12 17:59 UTCVendor advisory
  14. 2026-09-12 17:59 UTCGHSA enrichment
  15. 2026-09-12 05:42 UTCVendor advisory
  16. 2026-09-12 05:42 UTCGHSA enrichment
  17. 2026-09-11 17:25 UTCEG score recompute
  18. 2026-09-11 17:25 UTCVendor advisory
  19. 2026-09-11 17:25 UTCGHSA enrichment
  20. 2026-09-11 14:53 UTCEPSS rescore
  21. 2026-09-11 14:53 UTCEPSS rescore
  22. 2026-09-11 05:00 UTCGHSA enrichment
  23. 2026-09-10 16:43 UTCEG score recompute
  24. 2026-09-10 16:43 UTCGHSA enrichment
  25. 2026-09-10 04:26 UTCGHSA enrichment
  26. 2026-09-09 16:09 UTCVendor advisory
  27. 2026-09-09 16:09 UTCGHSA enrichment
  28. 2026-09-09 08:13 UTCEG score recompute
  29. 2026-09-09 08:13 UTCGHSA enrichment
  30. 2026-09-08 22:01 UTCEPSS rescore
  31. 2026-09-08 19:56 UTCEG score recompute
  32. 2026-09-08 19:56 UTCGHSA enrichment
  33. 2026-09-08 16:16 UTCVendor advisory
  34. 2026-09-08 16:16 UTCGHSA enrichment
  35. 2026-09-08 03:50 UTCEG score recompute
  36. 2026-09-08 03:50 UTCGHSA enrichment
  37. 2026-09-07 15:32 UTCGHSA enrichment
  38. 2026-09-07 03:15 UTCGHSA enrichment
  39. 2026-09-06 14:54 UTCEG score recompute
  40. 2026-09-06 14:54 UTCGHSA enrichment
  41. 2026-09-06 13:48 UTCEPSS rescore
  42. 2026-09-06 02:36 UTCEG score recompute
  43. 2026-09-06 02:36 UTCGHSA enrichment
  44. 2026-09-05 15:31 UTCEPSS rescore
  45. 2026-09-05 14:19 UTCEG score recompute
  46. 2026-09-05 14:19 UTCGHSA enrichment
  47. 2026-09-05 13:18 UTCEG score recompute
  48. 2026-09-05 13:17 UTCGHSA enrichment
  49. 2026-09-05 06:25 UTCEG score recompute
  50. 2026-09-05 05:24 UTCEG score recompute
  51. 2026-09-05 05:23 UTCMITRE cvelistV5first tracked

Frequently asked(5)

What is CVE-2026-86145?
CVE-2026-86145 is a high vulnerability published on September 5, 2026. PCRE2 before 10.48 allows a pcre2dfamatch out-of-bounds write because reuse of a cached workspace block, in a recursive DFA matching workspace, lacks a size check (even though a newly allocated block, for the same purpose, does have a size check). This outcome requires an attacker-controlled…
When was CVE-2026-86145 disclosed?
CVE-2026-86145 was first published in the National Vulnerability Database on September 5, 2026, with the most recent update on September 9, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-86145 actively exploited?
CVE-2026-86145 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 68.9% of all scored CVEs.
What is the CVSS score of CVE-2026-86145?
CVE-2026-86145 has a CVSS v3 base score of 8.2 (NVD).
How do I remediate CVE-2026-86145?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-86145, 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

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

Explore →

Is Your Infrastructure Affected by CVE-2026-86145?

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

Start Free Scan →Browse All CVEs