CVE-2026-116795

validatedZero produced an exploit or a check.

GHSA-gg6h-894w-4m9c ↗EUVD-2026-112268 ↗

check availableZero validated a working check for it.not proven exploitableZero has a detection check, but hasn't produced a full working exploit yet.
cve.orgpublic pocExploit code has been published by someone. Source signals can also carry a PoC (Proof of Concept).+3h56mkevAttacks confirmed in the real world.
npm:re2js >= 2.2.0, < 2.8.7
fixed in 2.8.7
ETK-2026-2908Zero's internal tracking ID, independent of the CVE number., permanent identifier
pkg:npm/re2js
+4h41mTTV
14mAI analysisAnalysis: how long the AI spent reversing this signal.
Check if you are vulnerable
timeline
0 = trigger signal
trigger signal (cve.org) +0hpublic poc+3h56mcheck available+4h41magent stopped
0
+1h
+2h
+3h
+5h

description

re2js before 2.8.7 can consume excessive CPU when lookbehind matching is enabled and repeated-match APIs process attacker-controlled text. An attacker may use this condition to block a Node.js worker and disrupt service; applications are affected when they enable LOOKBEHINDS and use operations such as repeated searches, splitting, or replacement on untrusted input.

mitigation

Upgrade re2js to version 2.8.7 or later. Until upgraded, disable lookbehind use for untrusted input and limit the size of text sent to repeated-matching operations.

fixed in 2.8.7

check
available
exploit
no
automationDeterministic: a check that runs on its own, the same request on every target. Contextual: an agentic technique that needs to be applied per target, for bugs that depend on contextual flows.
contextual
auth requiredWhether an attacker needs an account first, based on the CVSS vector's Privileges Required.
no
EPSSEstimate of the chance this CVE is exploited in the next 30 days. Refreshed daily.
–
agent run time
14m
cve.org record, t = 0The moment cve.org publishes the CVE in full.
2026-10-28 17:14Z
Δ to public pocExploit code has been published by someone. Source signals can also carry a PoC (Proof of Concept).
+3h56m
Δ to kevAttacks confirmed in the real world.
–

outcome

Contextual check: a technique exists and was validated, but no deterministic check could cover this one.

source signals

Public signals that triggered or updated the pipeline. These are inputs for the deltas above.

  1. 2026-10-28 17:14Z
    ghsa: trigger signal, started the run
  2. 2026-10-28 17:14Z
    public poc, published 2026-10-28 21:10Z
  3. 2026-10-28 17:14Z

this entry in the feed

GET /api/v1/feed/CVE-2026-116795

{
  "etk_id": "ETK-2026-2908",
  "cve_id": "CVE-2026-116795",
  "display_id": "CVE-2026-116795",
  "ghsa_id": "GHSA-gg6h-894w-4m9c",
  "euvd_id": "EUVD-2026-112268",
  "status": "published",
  "anchor_state": "anchored",
  "title": "Quadratic-time denial of service in re2js lookbehind matching",
  "summary": "re2js before 2.8.7 can consume excessive CPU when lookbehind matching is enabled and repeated-match APIs process attacker-controlled text. An attacker may use this condition to block a Node.js worker and disrupt service; applications are affected when they enable `LOOKBEHINDS` and use operations such as repeated searches, splitting, or replacement on untrusted input.",
  "mitigation": "Upgrade re2js to version 2.8.7 or later. Until upgraded, disable lookbehind use for untrusted input and limit the size of text sent to repeated-matching operations.",
  "vendor": "npm",
  "product": "npm:re2js",
  "affected": [
    {
      "affected_notes": [],
      "affected_ranges": [
        ">= 2.2.0, < 2.8.7"
      ],
      "ecosystem": "npm",
      "fixed_versions": [
        "2.8.7"
      ],
      "package_name": "re2js",
      "purl": "pkg:npm/re2js"
    }
  ],
  "cwes": null,
  "cvss_score": 7.5,
  "cvss_src": "cna_vendor",
  "cvss_vector": "CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H",
  "epss_score": null,
  "epss_percentile": null,
  "epss_asof": null,
  "automation": "contextual",
  "check": true,
  "check_confidence_basis": "assessed",
  "exploit": false,
  "pipeline_minutes": 14.256201333333333,
  "t0_at": "2026-10-28T17:14:15.988000+00:00",
  "signals": {
    "check": {
      "at": "2026-10-28T21:55:29.298293+00:00",
      "days": 0.19529294320601853,
      "is_lower_bound": false,
      "measured_at": "2026-10-28T17:14:15.988000+00:00",
      "url": null
    },
    "public_poc": {
      "at": "2026-10-28T21:10:01+00:00",
      "days": 0.16371541666666667,
      "is_lower_bound": false,
      "measured_at": "2026-10-28T17:14:15.988000+00:00",
      "url": "https://github.com/advisories/GHSA-gg6h-894w-4m9c"
    },
    "trigger_signal": {
      "at": "2026-10-28T17:14:15.988000+00:00",
      "days": 0,
      "is_lower_bound": false,
      "measured_at": "2026-10-28T17:14:15.988000+00:00",
      "url": "https://github.com/advisories/GHSA-gg6h-894w-4m9c"
    }
  }
}

published 2026-10-28 21:41Z
last change 2026-10-29 01:16Z

Need the technical details behind an entry?

Every entry here shows what we attempted and when. The technical details, the generated exploit that fired it and the evidence behind the verdict are not public. Tell us about your use case and we’ll get back to you about extended API access.