CVE-2026-67550: re2 Denial of Service Vulnerability

MODERATE
Advisory Identifier: GHSA-ff84-5f28-78qj
CVSS 5.7
CWE-125
Published
Advisory Summary

CVE-2026-67550 is a MODERATE (CVSS 5.7) denial of service vulnerability (CWE-125: Out-of-bounds Read) affecting re2 libraries in the npm ecosystem. The issue involves out-of-bounds heap read in `exec`/`test`/`match` via attacker-influenced `lastindex` on a non-ascii subject → uncatchable process crash (dos). Remediation is available by upgrading affected packages to version 1.25.2.

CVE-2026-67550 at a Glance

CVE Identifier CVE-2026-67550
GHSA Identifier GHSA-ff84-5f28-78qj
Severity MODERATE
CVSS v3.1 Base Score 5.7
CWE Classification CWE-125: Out-of-bounds Read
Affected Product re2
Package Ecosystem npm
Published Date
Last Updated

Security Impact

CVSS: 5.7

The security impact metrics below are parsed directly from the CVSS v3.1 vector string (CVSS:3.1/AV:L/AC:H/PR:N/UI:N/S:U/C:L/I:N/A:H).

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

How to Fix CVE-2026-67550

To remediate this vulnerability, upgrade all affected re2 dependencies to a patched release. Both direct and transitive dependencies should be checked, as frameworks or security libraries may pull in vulnerable versions transitively.

re2 fixed: 1.25.2
npm install re2@1.25.2
Verify Direct and Transitive Dependencies

Run the following command in your project directory to verify that all resolved dependencies use the patched release:

npm ls re2

How to Check if You Are Affected

To determine whether your Node.js application is affected by CVE-2026-67550, inspect your project dependencies using npm:

npm ls re2

Analyze the terminal output to locate any version of re2 in your dependency tree. If any resolved version matches the vulnerable ranges listed in the table below (for example, versions earlier than 1.25.2), your application is affected.

Note: The npm ls re2 command inspects dependencies declared in your package.json and lockfile; it does not perform automated runtime dynamic scanning.

Technical Details

Vulnerability Mechanism & Technical Analysis

This vulnerability is classified under CWE-125: Out-of-bounds Read, where the product reads data past the end, or before the beginning, of the intended buffer. In re2, software state validation or input boundaries are circumvented during processing. Review the official source advisory statement below for specific affected components, classes, and reproduction details.

Source Advisory Statement

## Summary `re2` validates the user-settable `lastIndex` against the subject's **UTF-8 byte length** but then uses it as a **UTF-16 code-unit count** to walk the subject buffer, with no bounds check. For any non-ASCII subject, the byte length is larger than the true character count, so a `lastIndex` between those two values passes validation while pointing past the end of the buffer. The subsequent walk reads out of bounds. With a large subject the read marches into unmapped memory and the process dies with **SIGABRT/SIGSEGV** — an uncatchable crash (`try/catch` cannot stop it), i.e. a denial of service for any worker/process that runs the match. In some cases the out-of-bounds bytes are copied into the returned value (a bounded, best-effort heap information leak). ## Root cause The subject wrapper stores the UTF-8 **byte** length in `StrVal::length`: - `lib/addon.cc:200` `auto argLength = utf8Length(s, isolate);` — UTF-8 **byte** count - `lib/addon.cc:209` `lastStringValue.reset(buffer, argSize, argLength, startFrom, false, isAscii);` `setIndex` then validates the (UTF-16) `lastIndex` against that byte length and walks the buffer by character count: ```cpp // lib/addon.cc:229 void StrVal::setIndex(size_t newIndex) { isValidIndex = newIndex <= length; // length == UTF-8 BYTE length, not UTF-16 length if (!isValidIndex) { index = newIndex; byteIndex = 0; return; } ... // addon.cc:263 byteIndex = index < newIndex ? getUtf16PositionByCounter(data, byteIndex, newIndex - index) : getUtf16PositionByCounter(data, 0, newIndex); index = newIndex; } ``` `getUtf16PositionByCounter` reads `data[from]` and advances by the UTF-8 char size with **no check of `from` against the buffer size**: ```cpp // lib/wrapped_re2.h:264 inline size_t getUtf16PositionByCounter(const char *data, size_t from, size_t n) { for (; n > 0; --n) { size_t s = getUtf8CharSize(data[from]); // <-- OOB read once `from` passes the buffer end from += s; if (s == 4 && n >= 2) --n; } return from; } ``` `lastIndex` is user-settable to any positive integer (capped only at `>= 0`, no upper bound): ```cpp // lib/accessors.cc:166 NAN_SETTER(WrappedRE2::SetLastIndex) { ... int n = value->NumberValue(...).FromMaybe(0); re2->lastIndex = n <= 0 ? 0 : n; // no upper bound relative to the subject } ``` For an ASCII subject the byte length equals the UTF-16 length, so the guard is correct — this only triggers on non-ASCII subjects. The out-of-bounds read happens inside `prepareArgument` for any `global`/`sticky` regex, reached by `exec`, `test`, `String.prototype.match`, `replace`, and `split`. ## Proof of concept **Minimal (AddressSanitizer, deterministic OOB read):** ```js const RE2 = require('re2'); const re = new RE2('a', 'y'); // sticky; 'g' also works re.lastIndex = 3; // 3 <= byteLen(4) passes the guard; only 2 real chars exist re.exec('éé'); // U+00E9 = 2 bytes each ``` Built with `-fsanitize=address`, this aborts with: ``` ERROR: AddressSanitizer: heap-buffer-overflow ... READ of size 1 #0 getUtf16PositionByCounter wrapped_re2.h:268 #1 StrVal::reset addon.cc:277 #2 WrappedRE2::prepareArgument addon.cc:209 #3 WrappedRE2::Exec exec.cc:17 ``` The overflowed region is the subject buffer allocated by `node::Buffer::New` at `addon.cc:205`. **Real-world impact on the shipped prebuilt binary (no ASAN) — uncatchable crash:** ```js const RE2 = require('re2'); const s = '中'.repeat(40000000); // UTF-16 length 40M, UTF-8 bytes 120M const re = new RE2('a', 'y'); re.lastIndex = Buffer.byteLength(s) - 1; // passes the byte-length guard, far exceeds real char count re.exec(s); // walks into unmapped memory -> SIGSEGV (exit 139) ``` `try { ... } catch (e) {}` around the call does **not** prevent termination — it is a native fault, not a JS exception. Validated on a clean `npm install re2@1.25.1` (latest): stock prebuilt → SIGSEGV; ASAN build → the heap-buffer-overflow read above. ## Impact - **Denial of service (primary):** an uncatchable native crash that terminates the Node process/worker. Reachable remotely and without authentication wherever an application (a) uses a `global` or `sticky` `RE2`, (b) applies it to a non-ASCII subject, and (c) sets `lastIndex` from attacker-influenced data (e.g. resuming a scan/pagination at a client-supplied offset). - **Information disclosure (secondary, best-effort):** the out-of-bounds `byteIndex` can cause adjacent heap bytes to be copied into the returned value (e.g. the leading segment of a `replace` result). This is bounded and unreliable — the subject buffer is `calloc`-allocated (zero-filled) and the over-read distance depends on interpreting out-of-bounds bytes as UTF-8 sizes — so it is noted for completeness, not as a dependable primitive. This is distinct from GHSA-8hcv-x26h-mcgp (the global `replace()` output-amplification abort), which was fixed in 1.25.1. This `lastIndex` out-of-bounds read is a separate defect and remains present in 1.25.1. ## Suggested fix Two independent hardenings; either closes the crash, both is safest: 1. **Bound the walk** so it can never read past the buffer: ```cpp inline size_t getUtf16PositionByCounter(const char *data, size_t size, size_t from, size_t n) { for (; n > 0 && from < size; --n) { size_t s = getUtf8CharSize(data[from]); from += s; if (s == 4 && n >= 2) --n; } return from > size ? size : from; } ``` (thread `size` through the two call sites in `StrVal::setIndex`). 2. **Validate `lastIndex` against the true UTF-16 length**, not the UTF-8 byte length — e.g. store `s->Length()` (UTF-16 units) as the value compared in `isValidIndex = newIndex <= <utf16Length>`, so an out-of-range `lastIndex` takes the existing `!isValidIndex` early-return path. ## Resolution Fixed in re2 1.25.2. `lastIndex` is now validated against the subject's UTF-16 length instead of its UTF-8 byte length (`lib/addon.cc`), so an out-of-range `lastIndex` is rejected before the buffer is walked. As defense in depth, the code-unit walk (`getUtf16PositionByCounter` in `lib/wrapped_re2.h`) is now bounded by the buffer size and can no longer read past the end. **Remediation:** upgrade to `re2@1.25.2` or later. **Workaround** (if you cannot upgrade): do not assign `lastIndex` from untrusted input, or clamp it to the subject's string length (`str.length`) before calling `exec`/`test`/`match`/`replace`/`split` on a non-ASCII subject.

CVE-2026-67550 Affected re2 Versions

1 component(s)
Fixed Versions:
1.25.2
Product / Package Ecosystem Affected Versions Fixed Version
re2
npm
< 1.25.2
1.25.2

References

Frequently Asked Questions

What is CVE-2026-67550?
CVE-2026-67550 is a security vulnerability in re2 involving Out-of-bounds heap read in `exec`/`test`/`match` via attacker-influenced `lastIndex` on a non-ASCII subject → uncatchable process crash (DoS) under CWE-125: Out-of-bounds Read.
Which re2 versions are affected?
Affected versions include releases prior to 1.25.2 across affected packages: re2.
What version fixes CVE-2026-67550?
Upgrading to 1.25.2 (or the latest patched release for your respective branch) resolves the vulnerability.
Is re2 affected?
Yes, re2 is affected in releases prior to 1.25.2. Upgrade your dependency to 1.25.2 or later.
What is the CVSS score of CVE-2026-67550?
CVE-2026-67550 has a CVSS v3.1 base score of 5.7 (MODERATE) with vector string CVSS:3.1/AV:L/AC:H/PR:N/UI:N/S:U/C:L/I:N/A:H.
What CWE is associated with CVE-2026-67550?
CVE-2026-67550 is classified under CWE-125: Out-of-bounds Read (The product reads data past the end, or before the beginning, of the intended buffer.).
How can I check npm dependencies for CVE-2026-67550?
Run the dependency tree command: 'npm ls re2'. This command lists direct and transitive dependencies in your build configuration so you can verify if a vulnerable version is resolved.
Machine-readable OSV JSON OSV v1.5 Schema
Normalized schema output
{
  "schema_version" : "1.4.0",
  "id" : "GHSA-ff84-5f28-78qj",
  "modified" : "2026-07-31T16:53:16Z",
  "published" : "2026-07-31T16:53:16Z",
  "aliases" : [ "CVE-2026-67550" ],
  "summary" : "re2: Out-of-bounds heap read in `exec`/`test`/`match` via attacker-influenced `lastIndex` on a non-ASCII subject → uncatchable process crash (DoS)",
  "details" : "## Summary\n\n`re2` validates the user-settable `lastIndex` against the subject's **UTF-8 byte length** but then uses it as a **UTF-16 code-unit count** to walk the subject buffer, with no bounds check. For any non-ASCII subject, the byte length is larger than the true character count, so a `lastIndex` between those two values passes validation while pointing past the end of the buffer. The subsequent walk reads out of bounds. With a large subject the read marches into unmapped memory and the process dies with **SIGABRT/SIGSEGV** — an uncatchable crash (`try/catch` cannot stop it), i.e. a denial of service for any worker/process that runs the match. In some cases the out-of-bounds bytes are copied into the returned value (a bounded, best-effort heap information leak).\n\n## Root cause\n\nThe subject wrapper stores the UTF-8 **byte** length in `StrVal::length`:\n\n- `lib/addon.cc:200` `auto argLength = utf8Length(s, isolate);` — UTF-8 **byte** count\n- `lib/addon.cc:209` `lastStringValue.reset(buffer, argSize, argLength, startFrom, false, isAscii);`\n\n`setIndex` then validates the (UTF-16) `lastIndex` against that byte length and walks the buffer by character count:\n\n```cpp\n// lib/addon.cc:229\nvoid StrVal::setIndex(size_t newIndex) {\n    isValidIndex = newIndex <= length;   // length == UTF-8 BYTE length, not UTF-16 length\n    if (!isValidIndex) { index = newIndex; byteIndex = 0; return; }\n    ...\n    // addon.cc:263\n    byteIndex = index < newIndex\n        ? getUtf16PositionByCounter(data, byteIndex, newIndex - index)\n        : getUtf16PositionByCounter(data, 0, newIndex);\n    index = newIndex;\n}\n```\n\n`getUtf16PositionByCounter` reads `data[from]` and advances by the UTF-8 char size with **no check of `from` against the buffer size**:\n\n```cpp\n// lib/wrapped_re2.h:264\ninline size_t getUtf16PositionByCounter(const char *data, size_t from, size_t n) {\n    for (; n > 0; --n) {\n        size_t s = getUtf8CharSize(data[from]);   // <-- OOB read once `from` passes the buffer end\n        from += s;\n        if (s == 4 && n >= 2) --n;\n    }\n    return from;\n}\n```\n\n`lastIndex` is user-settable to any positive integer (capped only at `>= 0`, no upper bound):\n\n```cpp\n// lib/accessors.cc:166\nNAN_SETTER(WrappedRE2::SetLastIndex) {\n    ...\n    int n = value->NumberValue(...).FromMaybe(0);\n    re2->lastIndex = n <= 0 ? 0 : n;   // no upper bound relative to the subject\n}\n```\n\nFor an ASCII subject the byte length equals the UTF-16 length, so the guard is correct — this only triggers on non-ASCII subjects. The out-of-bounds read happens inside `prepareArgument` for any `global`/`sticky` regex, reached by `exec`, `test`, `String.prototype.match`, `replace`, and `split`.\n\n## Proof of concept\n\n**Minimal (AddressSanitizer, deterministic OOB read):**\n\n```js\nconst RE2 = require('re2');\nconst re = new RE2('a', 'y');   // sticky; 'g' also works\nre.lastIndex = 3;               // 3 <= byteLen(4) passes the guard; only 2 real chars exist\nre.exec('éé');                  // U+00E9 = 2 bytes each\n```\n\nBuilt with `-fsanitize=address`, this aborts with:\n\n```\nERROR: AddressSanitizer: heap-buffer-overflow ... READ of size 1\n  #0 getUtf16PositionByCounter   wrapped_re2.h:268\n  #1 StrVal::reset               addon.cc:277\n  #2 WrappedRE2::prepareArgument addon.cc:209\n  #3 WrappedRE2::Exec            exec.cc:17\n```\n\nThe overflowed region is the subject buffer allocated by `node::Buffer::New` at `addon.cc:205`.\n\n**Real-world impact on the shipped prebuilt binary (no ASAN) — uncatchable crash:**\n\n```js\nconst RE2 = require('re2');\nconst s = '中'.repeat(40000000);        // UTF-16 length 40M, UTF-8 bytes 120M\nconst re = new RE2('a', 'y');\nre.lastIndex = Buffer.byteLength(s) - 1; // passes the byte-length guard, far exceeds real char count\nre.exec(s);                              // walks into unmapped memory -> SIGSEGV (exit 139)\n```\n\n`try { ... } catch (e) {}` around the call does **not** prevent termination — it is a native fault, not a JS exception. Validated on a clean `npm install re2@1.25.1` (latest): stock prebuilt → SIGSEGV; ASAN build → the heap-buffer-overflow read above.\n\n## Impact\n\n- **Denial of service (primary):** an uncatchable native crash that terminates the Node process/worker. Reachable remotely and without authentication wherever an application (a) uses a `global` or `sticky` `RE2`, (b) applies it to a non-ASCII subject, and (c) sets `lastIndex` from attacker-influenced data (e.g. resuming a scan/pagination at a client-supplied offset).\n- **Information disclosure (secondary, best-effort):** the out-of-bounds `byteIndex` can cause adjacent heap bytes to be copied into the returned value (e.g. the leading segment of a `replace` result). This is bounded and unreliable — the subject buffer is `calloc`-allocated (zero-filled) and the over-read distance depends on interpreting out-of-bounds bytes as UTF-8 sizes — so it is noted for completeness, not as a dependable primitive.\n\nThis is distinct from GHSA-8hcv-x26h-mcgp (the global `replace()` output-amplification abort), which was fixed in 1.25.1. This `lastIndex` out-of-bounds read is a separate defect and remains present in 1.25.1.\n\n## Suggested fix\n\nTwo independent hardenings; either closes the crash, both is safest:\n\n1. **Bound the walk** so it can never read past the buffer:\n\n```cpp\ninline size_t getUtf16PositionByCounter(const char *data, size_t size, size_t from, size_t n) {\n    for (; n > 0 && from < size; --n) {\n        size_t s = getUtf8CharSize(data[from]);\n        from += s;\n        if (s == 4 && n >= 2) --n;\n    }\n    return from > size ? size : from;\n}\n```\n(thread `size` through the two call sites in `StrVal::setIndex`).\n\n2. **Validate `lastIndex` against the true UTF-16 length**, not the UTF-8 byte length — e.g. store `s->Length()` (UTF-16 units) as the value compared in `isValidIndex = newIndex <= <utf16Length>`, so an out-of-range `lastIndex` takes the existing `!isValidIndex` early-return path.\n\n## Resolution\n\nFixed in re2 1.25.2.\n\n`lastIndex` is now validated against the subject's UTF-16 length instead of its\nUTF-8 byte length (`lib/addon.cc`), so an out-of-range `lastIndex` is rejected\nbefore the buffer is walked. As defense in depth, the code-unit walk\n(`getUtf16PositionByCounter` in `lib/wrapped_re2.h`) is now bounded by the\nbuffer size and can no longer read past the end.\n\n**Remediation:** upgrade to `re2@1.25.2` or later.\n\n**Workaround** (if you cannot upgrade): do not assign `lastIndex` from untrusted\ninput, or clamp it to the subject's string length (`str.length`) before calling\n`exec`/`test`/`match`/`replace`/`split` on a non-ASCII subject.",
  "severity" : [ {
    "type" : "CVSS_V3",
    "score" : "CVSS:3.1/AV:L/AC:H/PR:N/UI:N/S:U/C:L/I:N/A:H"
  } ],
  "affected" : [ {
    "package" : {
      "ecosystem" : "npm",
      "name" : "re2"
    },
    "ranges" : [ {
      "type" : "ECOSYSTEM",
      "events" : [ {
        "introduced" : "0"
      }, {
        "fixed" : "1.25.2"
      } ]
    } ],
    "database_specific" : {
      "last_known_affected_version_range" : "<= 1.25.1"
    }
  } ],
  "references" : [ {
    "type" : "WEB",
    "url" : "https://github.com/uhop/node-re2/security/advisories/GHSA-ff84-5f28-78qj"
  }, {
    "type" : "ADVISORY",
    "url" : "https://nvd.nist.gov/vuln/detail/CVE-2026-67550"
  }, {
    "type" : "WEB",
    "url" : "https://github.com/uhop/node-re2/commit/56293de4fc0914d7bc35f92e98de25b0d9bb417d"
  }, {
    "type" : "PACKAGE",
    "url" : "https://github.com/uhop/node-re2"
  }, {
    "type" : "WEB",
    "url" : "https://github.com/uhop/node-re2/releases/tag/1.25.2"
  } ],
  "database_specific" : {
    "cwe_ids" : [ "CWE-125" ],
    "severity" : "MODERATE",
    "github_reviewed" : true,
    "github_reviewed_at" : "2026-07-31T16:53:16Z",
    "nvd_published_at" : "2026-07-30T20:18:15Z"
  }
}