CVE-2026-68499

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 97% 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.

re2 provides Node.js bindings for Google's RE2 regular expression engine. Prior to 1.25.2, re2's String.prototype.match implementation with a global RE2 pattern that can match the empty string fails to advance its native matching cursor in lib/match.cc, causing an infinite loop and unbounded native memory growth that blocks the event loop and can exhaust host memory. This issue is fixed in 1.25.2.

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
3%
KEV
Not listed

Published

July 30, 2026

Last Modified

July 31, 2026

Advisory Details (3)

Auto-updated Jul 30, 2026
🔬 Proof of concept available. Patch available. Sources: github, github_commit, github_release.
github_release Patch Available

Release 1.25.2

Patch available: uhop/node-re2 1.25.2

https://github.com/uhop/node-re2/releases/tag/1.25.2
github_commit

commit 56293de4fc09 (uhop/node-re2)

Fix landed in uhop/node-re2 commit 56293de4fc09 — awaiting tagged release

https://github.com/uhop/node-re2/commit/56293de4fc0914d7bc35f92e98de25b0d9bb417d
github Patch Available🟡 PoC Available

Global `String.prototype.match` with an empty-matchable pattern never advances → infinite loop with unbounded native memory growth (DoS) · Advisory · uhop/node-re2 · GitHub

https://github.com/uhop/node-re2/security/advisories/GHSA-6hxr-mr5r-9836

Vendor Advisories for CVE-2026-68499(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.2—

Weakness Classification(1)

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

Data Freshness Timeline

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

Frequently asked(5)

What is CVE-2026-68499?
CVE-2026-68499 is a medium vulnerability published on July 30, 2026. re2 provides Node.js bindings for Google's RE2 regular expression engine. Prior to 1.25.2, re2's String.prototype.match implementation with a global RE2 pattern that can match the empty string fails to advance its native matching cursor in lib/match.cc, causing an infinite loop and unbounded native…
When was CVE-2026-68499 disclosed?
CVE-2026-68499 was first published in the National Vulnerability Database on July 30, 2026, with the most recent update on July 31, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-68499 actively exploited?
CVE-2026-68499 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 97.0% of all scored CVEs.
What is the CVSS score of CVE-2026-68499?
CVE-2026-68499 has a CVSS v3 base score of 6.2 (NVD).
How do I remediate CVE-2026-68499?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-68499, 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-68499

Explore →

Is Your Infrastructure Affected by CVE-2026-68499?

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

Start Free Scan →Browse All CVEs