CVE-2026-67550

MEDIUMPre-NVD 5.75.7—
EchelonGraph scoreMEDIUM confidence

This medium-severity CVE scores 5.7 under a secondary CVSS source (NVD's own analysis pending). EPSS exploit probability: 0.1%, top 98% 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.7EG
EchelonGraph verdictMonitorLow exploitation likelihood right now — keep watching.
  • Lower severity and no public exploit yet
CISA-KEV: Not listedEPSS PROB: 0%CVSS: 5.7Exploit: 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 validates lastIndex against the UTF-8 byte length of a subject but uses it as a UTF-16 code-unit offset in exec, test, match, replace, and split, allowing an attacker-influenced lastIndex on a non-ASCII subject to trigger an out-of-bounds heap read and an uncatchable process crash, with limited heap information disclosure in some cases. This issue is fixed in 1.25.2.

CVSS v3
5.7
EG Score
5.7(medium)
EG Risk
42(Track)
EG Risk 42/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
Severity57% × 45%
Exploitation40% × 40%
Automatability0% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
0%
EPSS %ILE
2%
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

Out-of-bounds heap read in `exec`/`test`/`match` via attacker-influenced `lastIndex` on a non-ASCII subject → uncatchable process crash (DoS) · Advisory · uhop/node-re2 · GitHub

Affected: 1.25.1. This

https://github.com/uhop/node-re2/security/advisories/GHSA-ff84-5f28-78qj

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

Frequently asked(5)

What is CVE-2026-67550?
CVE-2026-67550 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 validates lastIndex against the UTF-8 byte length of a subject but uses it as a UTF-16 code-unit offset in exec, test, match, replace, and split, allowing an attacker-influenced lastIndex on a non-ASCII…
When was CVE-2026-67550 disclosed?
CVE-2026-67550 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-67550 actively exploited?
CVE-2026-67550 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.8% of all scored CVEs.
What is the CVSS score of CVE-2026-67550?
CVE-2026-67550 has a CVSS v3 base score of 5.7 (NVD).
How do I remediate CVE-2026-67550?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-67550, 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-67550

Explore →

Is Your Infrastructure Affected by CVE-2026-67550?

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

Start Free Scan →Browse All CVEs