CVE-2026-67550

What it is

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.

At a glance

Exploitability

Can be exploited locally on the machine without logging in. High risk of service disruption.

Exploit odds

0.2% chance of exploitation in the next 30 days (EPSS).

Fix

A patch, advisory or fixed version is referenced. Upgrade or apply it.

Timeline

1. 2026-07-30 20:18 UTC PublishedDisclosed publicly on CVE.org and NVD
2. 2026-10-23 22:10 UTC Last updatedMost recent change to the record

Why it ranks here

• Exploited in the wild: no, CISA does not list it.
• Exploit odds: 0.2% in the next 30 days (EPSS).
• Severity: 5.7 MEDIUM (CVSS).
• Fix: a patch or advisory is linked.

Details

Published

2026-07-30 20:18 UTC

Last modified

2026-10-23 22:10 UTC

Exploit probability

0.2% · EPSS, next 30 days

Weakness

CWE-125 · Out-of-bounds read

Record status

Awaiting Analysis

Attack profile CVSS 3.1 · 5.7

Attack vector

Local

Complexity

High

Privileges needed

None

User interaction

None

Scope

Unchanged

Confidentiality

Low

Integrity

None

Availability

High

Is it in your code?

Hand this to your coding agent. It searches your project for the affected products and checks versions. Nothing leaves your machine.

Read https://cve-list.com/agent/cve/CVE-2026-67550.md and follow it. Check whether this project is affected by CVE-2026-67550. Read only. Don't change anything and don't upload my code. Tell me yes, no or not sure, with the file as proof.

Copy as ticket · More options · Status badge