CVE-2026-71430

MEDIUMPre-NVD 6.26.2—
EchelonGraph scoreMEDIUM confidence

This medium-severity CVE scores 6.2 under a secondary CVSS source (NVD's own analysis pending). EPSS exploit probability: 0.1%, top 99% 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
6.2EG
EchelonGraph verdictMonitorLow exploitation likelihood right now — keep watching.
  • Lower severity and no public exploit yet
CISA-KEV: Not listedEPSS PROB: 0%CVSS: 6.2Exploit: 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.25.1, the WrappedRE2::Replace function built its replacement result and passed it to V8 using ToLocalChecked without checking for the empty MaybeLocal that V8 returns when the resulting string or buffer exceeds V8's maximum string length. When a global replace uses an output amplifying replacement template, the result can grow quadratically with the input size, and once the result exceeds V8's maximum string length, the unchecked ToLocalChecked call causes a fatal, uncatchable process abort instead of a catchable exception. This issue is fixed in version 1.25.1.

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

Published

August 6, 2026

Last Modified

August 7, 2026

Advisory Details (1)

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

String.prototype.replace(re2, template) aborts the Node process (uncatchable ToLocalChecked on empty MaybeLocal) when the result exceeds V8's max string length · Advisory · uhop/node-re2 · GitHub

https://github.com/uhop/node-re2/security/advisories/GHSA-8hcv-x26h-mcgp

Vendor Advisories for CVE-2026-71430(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.25.0+~cs1.6.0-2 (10 versions)——
Debian:13(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-2——
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-2——
npm(1)
PackageVulnerable rangeFixed inDependents
re2—1.25.1—

Weakness Classification(1)

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

Data Freshness Timeline

(refreshed 16× in last 7d / 30× 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-08-20 23:05 UTCEG score recompute
  2. 2026-08-20 22:56 UTCEPSS rescore
  3. 2026-08-19 20:42 UTCEG score recompute
  4. 2026-08-19 17:04 UTCEPSS rescore
  5. 2026-08-18 18:18 UTCEG score recompute
  6. 2026-08-18 13:49 UTCEPSS rescore
  7. 2026-08-18 13:49 UTCEPSS rescore
  8. 2026-08-17 15:54 UTCEG score recompute
  9. 2026-08-17 13:47 UTCEPSS rescore
  10. 2026-08-16 14:56 UTCEPSS rescore
  11. 2026-08-16 14:56 UTCEPSS rescore
  12. 2026-08-16 13:31 UTCEG score recompute
  13. 2026-08-16 02:15 UTCEPSS rescore
  14. 2026-08-15 11:08 UTCEG score recompute
  15. 2026-08-15 01:31 UTCEPSS rescore
  16. 2026-08-14 08:45 UTCEG score recompute
  17. 2026-08-13 22:00 UTCEPSS rescore
  18. 2026-08-13 06:22 UTCEG score recompute
  19. 2026-08-12 13:51 UTCEPSS rescore
  20. 2026-08-12 03:59 UTCEG score recompute
  21. 2026-08-11 01:35 UTCEG score recompute
  22. 2026-08-11 00:00 UTCEPSS rescore
  23. 2026-08-09 23:12 UTCEG score recompute
  24. 2026-08-09 13:47 UTCEPSS rescore
  25. 2026-08-08 20:50 UTCEG score recompute
Show 5 more
  1. 2026-08-08 16:37 UTCEPSS rescore
  2. 2026-08-07 18:27 UTCEG score recompute
  3. 2026-08-07 17:27 UTCEG score recompute
  4. 2026-08-06 22:38 UTCEG score recompute
  5. 2026-08-06 22:07 UTCEG score recompute

Frequently asked(5)

What is CVE-2026-71430?
CVE-2026-71430 is a medium vulnerability published on August 6, 2026. node-re2 provides RE2 regular expression bindings for Node.js. Prior to version 1.25.1, the WrappedRE2::Replace function built its replacement result and passed it to V8 using ToLocalChecked without checking for the empty MaybeLocal that V8 returns when the resulting string or buffer exceeds V8's…
When was CVE-2026-71430 disclosed?
CVE-2026-71430 was first published in the National Vulnerability Database on August 6, 2026, with the most recent update on August 7, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-71430 actively exploited?
CVE-2026-71430 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 98.5% of all scored CVEs.
What is the CVSS score of CVE-2026-71430?
CVE-2026-71430 has a CVSS v3 base score of 6.2 (NVD).
How do I remediate CVE-2026-71430?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-71430, 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-71430

Explore →

Is Your Infrastructure Affected by CVE-2026-71430?

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

Start Free Scan →Browse All CVEs