CVE-2026-112366

waiting for further signalsZero needs more public information before it can validate it.

GHSA-fc5q-39xc-vjpf ↗EUVD-2026-104404 ↗

no check availablenot proven exploitable
cve.orgpublic pocExploit code has been published by someone. Source signals can also carry a PoC (Proof of Concept).kevAttacks confirmed in the real world.
micromatch picomatch <= 4.0.7
CWE-1333 Inefficient Regular Expression Complexity
ETK-2026-2064Zero's internal tracking ID, independent of the CVE number., permanent identifier
1d 18h 24msince last run
16mAI analysisAnalysis: how long the AI spent reversing this signal.
timeline
0 = cve.org publication
trigger signal (cve.org) +0hwaiting for further signals+1h06m
0
+2h
+4h
+6h
+8h
+10h
+12h

description

Picomatch versions through 4.0.7 can consume excessive processing time when handling certain glob patterns, blocking the Node.js event loop. An attacker can deny service if an application passes attacker-controlled glob input to the affected library.

mitigation

Do not process untrusted glob patterns with affected Picomatch versions; enforce restrictive input validation and length or complexity limits before matching. Monitor for an upstream fixed release, as no fixed version is recorded.

check
no
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.
0.34%25th percentile
agent run time
16m
cve.org record, t = 0The moment cve.org publishes the CVE in full.
2026-10-19 15:29Z
Δ to public pocExploit code has been published by someone. Source signals can also carry a PoC (Proof of Concept).
–
Δ to kevAttacks confirmed in the real world.
–

outcome

Contextual: an exploit technique exists, 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-19 15:29Z
    cve_org: trigger signal, started the run

this entry in the feed

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

{
  "etk_id": "ETK-2026-2064",
  "cve_id": "CVE-2026-112366",
  "display_id": "CVE-2026-112366",
  "ghsa_id": "GHSA-fc5q-39xc-vjpf",
  "euvd_id": "EUVD-2026-104404",
  "status": "published",
  "anchor_state": "anchored",
  "title": "Regular expression denial of service in picomatch",
  "summary": "Picomatch versions through 4.0.7 can consume excessive processing time when handling certain glob patterns, blocking the Node.js event loop. An attacker can deny service if an application passes attacker-controlled glob input to the affected library.",
  "mitigation": "Do not process untrusted glob patterns with affected Picomatch versions; enforce restrictive input validation and length or complexity limits before matching. Monitor for an upstream fixed release, as no fixed version is recorded.",
  "vendor": "micromatch",
  "product": "picomatch",
  "affected": [
    {
      "affected_notes": [],
      "affected_ranges": [
        ">= 0, <= 4.0.7"
      ],
      "ecosystem": null,
      "fixed_versions": [],
      "package_name": "picomatch",
      "purl": null
    }
  ],
  "cwes": [
    1333
  ],
  "cvss_score": 8.7,
  "cvss_src": "cna_vendor",
  "cvss_vector": "CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:N/VI:N/VA:H/SC:N/SI:N/SA:N",
  "epss_score": 0.0034,
  "epss_percentile": 0.2588,
  "epss_asof": "2026-10-20",
  "automation": "contextual",
  "check": false,
  "check_confidence_basis": null,
  "exploit": false,
  "pipeline_minutes": 16.038781516666667,
  "t0_at": "2026-10-19T15:29:00.491000+00:00",
  "signals": {
    "trigger_signal": {
      "at": "2026-10-19T15:29:00.491000+00:00",
      "days": 0,
      "is_lower_bound": false,
      "measured_at": "2026-10-19T15:29:00.491000+00:00",
      "url": "https://www.cve.org/CVERecord?id=CVE-2026-112366"
    }
  }
}

published 2026-10-19 16:19Z
last change 2026-10-21 05:31Z

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.