Skip to main content
EPSS 0.2%top 92%

CVE-2026-67550: CWE-125: Out-of-bounds Read in uhop node-re2

0
Medium
Published: 07/30/2026 (07/30/2026, 19:59:55 UTC)
Source: CVE Database V5
Vendor/Project: uhop
Product: node-re2

Description

CVE-2026-67550 is an out-of-bounds read vulnerability in the node-re2 package, which provides Node.js bindings for Google's RE2 regular expression engine. Versions prior to 1.25.2 improperly validate and use the lastIndex parameter, leading to a heap read beyond allocated memory when processing non-ASCII subjects. This can cause an uncatchable process crash and limited heap information disclosure. The issue is fixed in version 1.25.2.

CVSS v3.1

Score 5.7medium

Attack Vector
Local
Attack Complexity
High
Privileges Required
None
User Interaction
None
Scope
Unchanged
Confidentiality
Low
Integrity
None
Availability
High
CVSS:3.1/AV:L/AC:H/PR:N/UI:N/S:U/C:L/I:N/A:H

Affected software

uhop

node-re2

Affected versions
<1.25.2

AI-Powered Analysis

Machine-generated threat intelligence

AILast updated: 08/07/2026, 14:32:34 UTC

Technical Analysis

The node-re2 package prior to version 1.25.2 validates the lastIndex parameter against the UTF-8 byte length of the input string but 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, resulting in a process crash that cannot be caught and potential limited disclosure of heap memory contents. The vulnerability is identified as CWE-125 (Out-of-bounds Read) and has a CVSS 3.1 base score of 5.7, indicating medium severity. The issue is resolved in node-re2 version 1.25.2.

Potential Impact

An attacker able to influence the lastIndex parameter on non-ASCII input can cause the Node.js process using node-re2 to crash in an uncatchable manner, resulting in denial of service. Additionally, limited heap memory information may be disclosed during the out-of-bounds read. There is no indication of code execution or integrity impact.

Mitigation Recommendations

Upgrade node-re2 to version 1.25.2 or later, where this vulnerability is fixed. No other mitigation or workaround is indicated. Patch status is confirmed fixed in 1.25.2.

Pro Console: star threats, build custom feeds, automate alerts via Slack, email & webhooks.Upgrade to Pro

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

Threat ID: 6a6baf0d9c2644c7f89b9bc5

Added to database: 07/30/2026, 20:07:41 UTC

Last enriched: 08/07/2026, 14:32:34 UTC

Last updated: 09/13/2026, 22:01:36 UTC

Views: 61

Community Reviews

0 reviews

Crowdsource mitigation strategies, share intel context, and vote on the most helpful responses. Sign in to add your voice and help keep defenders ahead.

Sort by
Loading community insights…

Want to contribute mitigation steps or threat intel context? Sign in or create an account to join the community discussion.

Actions

PRO

Updates to AI analysis require Pro Console access. Upgrade inside Console → Billing.

Please log in to the Console to use AI analysis features.

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

Breach by OffSeqOFFSEQFRIENDS — 25% OFF

Check if your credentials are on the dark web

Instant breach scanning across billions of leaked records. Free tier available.

Scan now
OffSeq TrainingCredly Certified

Lead Pen Test Professional

Technical5-day eLearningPECB Accredited
View courses