Skip to main content
VulnerabilityPublished

CVE-2026-68499: uhop node-re2 · Infinite Loop

Affects uhop node-re2Source CVE Database V5

0
Compare

Not known to be exploited · CVSS 6.2 Medium : upgrade to 1.25.2 when convenient.

Data as of 29 Oct 2026, 07:15 UTC

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

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 30 Jul 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 29 Oct 2026.

What to do

Upgrade uhop node-re2 to 1.25.2.

Affected software

ProductAffectedFixed in
uhopnode-re2Affected
  • <1.25.2
Fixed in
  • 1.25.2

AI-suggested

A fix is available in node-re2 version 1.25.2. Users should upgrade to version 1.25.2 or later to resolve this issue. No other mitigations are indicated by the vendor advisory.

Description

CVE-2026-68499 is a vulnerability in the node-re2 package, which provides Node.js bindings for Google's RE2 regular expression engine. Versions prior to 1.25.2 have a flaw in the String.prototype.match implementation when using a global RE2 pattern that can match the empty string. This causes an infinite loop due to failure to advance the matching cursor, leading to unbounded native memory growth, blocking the event loop and potentially exhausting host memory. The issue is fixed in version 1.25.2.

References

Community reviews

Loading reviews…