CVE-2026-71498

MEDIUMPre-NVD 5.15.1—
EchelonGraph scoreMEDIUM confidence

This medium-severity CVE scores 5.1 under a secondary CVSS source (NVD's own analysis pending). EPSS exploit probability: 0.2%, top 87% of all CVEs by exploit prediction. GitHub Security Advisory data not yet ingested — confidence will rise once GHSA publishes (typical lag: hours to days for open-source ecosystem CVEs; never for infrastructure-only CVEs).

Triggered by: NVD CVSS baseline
Sources: epss, secondary
Elevated
5.1EG
EchelonGraph verdictMonitorLow exploitation likelihood right now — keep watching.
  • Lower severity and no public exploit yet
CISA-KEV: Not listedEPSS PROB: 0%CVSS: 5.1Exploit: Elevated riskExposed: 0

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

node-re2 provides RE2 regular expression bindings for Node.js. Prior to version 1.26.1, passing a Buffer whose final bytes form a truncated (incomplete) multi-byte UTF-8 sequence could cause the native binding to read past the end of the allocated buffer while attempting to decode the final, incomplete code point. This could result in an out-of-bounds read and potential disclosure of adjacent memory contents. This issue is fixed in version 1.26.1.

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

Published

August 6, 2026

Last Modified

September 10, 2026

Advisory Details (3)

Auto-updated Aug 6, 2026
🔬 Proof of concept available. Patch available. Sources: github_commit, github.
github Patch Available🟡 PoC Available

Out-of-bounds heap read in `replace`/`split` via a `Buffer` ending in a truncated multi-byte UTF-8 character → adjacent heap memory disclosed to JavaScript · Advisory · uhop/node-re2 · GitHub

https://github.com/uhop/node-re2/security/advisories/GHSA-j4r3-hg7j-8chg
generic

Possible heap buffer over-read when a `Buffer` subject/pattern ends in a truncated multi-byte UTF-8 lead · Issue #272 · uhop/node-re2 · GitHub

https://github.com/uhop/node-re2/issues/272
github_commit

commit 9d72042a6a0d (uhop/node-re2)

Fix landed in uhop/node-re2 commit 9d72042a6a0d — awaiting tagged release

https://github.com/uhop/node-re2/commit/9d72042a6a0da5bc523908b04808ea0e23867cc4

Vendor Advisories for CVE-2026-71498(1)

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

Affected Packages

(5 across 5 ecosystems)
Debian:11(1)
PackageVulnerable rangeFixed inDependents
node-re21.15.9+~cs1.8.18-1 ... 1.25.0+~cs1.6.0-2 (21 versions)——
Debian:12(1)
PackageVulnerable rangeFixed inDependents
node-re21.18.0+~cs2.13.8-1 ... 1.26.1+~cs1.8.0-1 (12 versions)——
Debian:13(1)
PackageVulnerable rangeFixed inDependents
node-re21.21.4+~cs2.13.13-2 ... 1.26.1+~cs1.8.0-1 (7 versions)——
Debian:14(1)
PackageVulnerable rangeFixed inDependents
node-re21.21.4+~cs2.13.13-2, 1.22.1+~cs1.3.5-1, 1.23.3+~cs1.3.5-1, 1.25.0+~cs1.6.0-1, 1.25.0+~cs1.6.0-21.26.1+~cs1.7.0-1—
npm(1)
PackageVulnerable rangeFixed inDependents
re2—1.26.1—

Weakness Classification(1)

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

Data Freshness Timeline

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

Related CVEs(same CWE)

Frequently asked(5)

What is CVE-2026-71498?
CVE-2026-71498 is a medium vulnerability published on August 6, 2026. node-re2 provides RE2 regular expression bindings for Node.js. Prior to version 1.26.1, passing a Buffer whose final bytes form a truncated (incomplete) multi-byte UTF-8 sequence could cause the native binding to read past the end of the allocated buffer while attempting to decode the final,…
When was CVE-2026-71498 disclosed?
CVE-2026-71498 was first published in the National Vulnerability Database on August 6, 2026, with the most recent update on September 10, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-71498 actively exploited?
CVE-2026-71498 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-71498?
CVE-2026-71498 has a CVSS v3 base score of 5.1 (NVD).
How do I remediate CVE-2026-71498?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-71498, 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-71498

Explore →

Is Your Infrastructure Affected by CVE-2026-71498?

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

Start Free Scan →Browse All CVEs