Skip to main content
VulnerabilityPublished

CVE-2026-71498: uhop node-re2 · Out-of-bounds Read

Affects uhop node-re2Source CVE Database V5

0
Compare

Not known to be exploited · CVSS 5.1 Medium : upgrade to 1.26.1 when convenient.

Data as of 5 Nov 2026, 00:01 UTC

CVSS 3.1 base score
5.1Medium
How severe the flaw is on the 0–10 CVSS scale.
EPSS
0.1% chance of exploitation in 30 days – higher than 6% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
Patch
Available – fixed in 1.26.1
CVSS:3.1/AV:L/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:L

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 6 Aug 2026

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponized: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 5 Nov 2026.

What to do

Upgrade uhop node-re2 to 1.26.1.

Affected software

ProductAffectedFixed in
uhopnode-re2Affected
  • <1.26.1
Fixed in
  • 1.26.1
npmnode-re2pkg:npm/node-re2Other threatsAffected
  • <1.26.1
Fixed in
  • 1.26.1

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

AI-suggested

Upgrade node-re2 to version 1.26.1 or later, where this vulnerability is fixed. No other mitigation is indicated or required.

Description

node-re2 provides RE2 regular expression bindings for Node.js. Prior to version 1.26.1, passing a Buffer whose final bytes form a truncated (incomplete) multi-byte UTF-8 sequence could cause the native binding to read past the end of the allocated buffer while attempting to decode the final, incomplete code point. This could result in an out-of-bounds read and potential disclosure of adjacent memory contents. This issue is fixed in version 1.26.1.

References

Community reviews

Loading reviews…