CVE-2026-67550: CWE-125: Out-of-bounds Read in uhop node-re2
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.
AI Analysis
Technical Summary
The node-re2 package, which provides Node.js bindings for Google's RE2 regular expression engine, improperly validates the lastIndex property by comparing it against the UTF-8 byte length of the input string but then uses it as a UTF-16 code-unit offset in functions like exec, test, match, replace, and split. This mismatch allows an attacker-controlled lastIndex on non-ASCII input to trigger an out-of-bounds heap read, leading to a process crash that cannot be caught and may disclose limited heap information. The vulnerability is identified as CWE-125 (Out-of-bounds Read) and has a CVSS v3.1 score of 5.7 (medium severity). The issue is resolved in node-re2 version 1.25.2.
Potential Impact
Exploitation of this vulnerability can cause an uncatchable crash of the Node.js process using node-re2, resulting in denial of service. Additionally, limited heap information disclosure may occur, potentially aiding further attacks. There is no indication of privilege escalation or code execution. The attack requires local access (AV:L) and high attack complexity (AC:H), with no privileges or user interaction required.
Mitigation Recommendations
Upgrade node-re2 to version 1.25.2 or later, where this vulnerability is fixed. Since no official patch links or advisories are provided, users should verify the version in use and update accordingly. Patch status is confirmed by the description stating the issue is fixed in 1.25.2. No alternative mitigations are indicated.
CVE-2026-67550: CWE-125: Out-of-bounds Read in uhop node-re2
Description
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.1
Score 5.7medium
Affected software
Weaknesses
AI-Powered Analysis
Machine-generated threat intelligence
Technical Analysis
The node-re2 package, which provides Node.js bindings for Google's RE2 regular expression engine, improperly validates the lastIndex property by comparing it against the UTF-8 byte length of the input string but then uses it as a UTF-16 code-unit offset in functions like exec, test, match, replace, and split. This mismatch allows an attacker-controlled lastIndex on non-ASCII input to trigger an out-of-bounds heap read, leading to a process crash that cannot be caught and may disclose limited heap information. The vulnerability is identified as CWE-125 (Out-of-bounds Read) and has a CVSS v3.1 score of 5.7 (medium severity). The issue is resolved in node-re2 version 1.25.2.
Potential Impact
Exploitation of this vulnerability can cause an uncatchable crash of the Node.js process using node-re2, resulting in denial of service. Additionally, limited heap information disclosure may occur, potentially aiding further attacks. There is no indication of privilege escalation or code execution. The attack requires local access (AV:L) and high attack complexity (AC:H), with no privileges or user interaction required.
Mitigation Recommendations
Upgrade node-re2 to version 1.25.2 or later, where this vulnerability is fixed. Since no official patch links or advisories are provided, users should verify the version in use and update accordingly. Patch status is confirmed by the description stating the issue is fixed in 1.25.2. No alternative mitigations are indicated.
Technical Details
- Data Version
- 5.2
- Assigner Short Name
- GitHub_M
- Date Reserved
- 2026-07-29T18:47:17.075Z
- Cvss Version
- 3.1
- State
- PUBLISHED
- Remediation Level
- null
Threat ID: 6a6baf0d9c2644c7f89b9bc5
Added to database: 07/30/2026, 20:07:41 UTC
Last enriched: 07/30/2026, 20:25:01 UTC
Last updated: 07/31/2026, 00:23:58 UTC
Views: 11
Community Reviews
0 reviewsCrowdsource mitigation strategies, share intel context, and vote on the most helpful responses. Sign in to add your voice and help keep defenders ahead.
Want to contribute mitigation steps or threat intel context? Sign in or create an account to join the community discussion.
Actions
Updates to AI analysis require Pro Console access. Upgrade inside Console → Billing.
Need more coverage?
Upgrade to Pro Console for AI refresh and higher limits.
For incident response and remediation, OffSeq services can help resolve threats faster.
Latest Threats
Check if your credentials are on the dark web
Instant breach scanning across billions of leaked records. Free tier available.