ETK-2026-4199Zero's internal tracking ID, independent of the CVE number.

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

GHSA-6jwq-xf8q-xcwh ↗

no check availablenot proven exploitable
awaiting cvepublic pocExploit code has been published by someone. Source signals can also carry a PoC (Proof of Concept).kevAttacks confirmed in the real world.
npm:brace-expansion < 1.1.22; >= 2.0.0 < 2.1.8; >= 3.0.0 < 3.0.10; >= 4.0.0 < 5.0.13
fixed in 5.0.13, 3.0.10, 2.1.8, 1.1.22
CWE-400 Uncontrolled Resource Consumption
ETK-2026-4199Zero's internal tracking ID, independent of the CVE number., no cve assigned
pkg:npm/brace-expansion
2h 06msince last run
13mAI analysisAnalysis: how long the AI spent reversing this signal.
timeline
0 = cve.org, not yet published
trigger signal −8h22mwaiting for further signals−2h06m
−8h
−6h
−4h
0

description

brace-expansion can spend excessive CPU time processing specially formed untrusted brace patterns, blocking a Node.js event loop. Applications are affected when they expand attacker-supplied patterns directly or through minimatch or glob with brace expansion enabled.

mitigation

Upgrade brace-expansion to 5.0.13, 3.0.10, 2.1.8, 1.1.22 or later.

fixed in 5.0.13, 3.0.10, 2.1.8, 1.1.22

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.
–
agent run time
13m
cve.org record, t = 0The moment cve.org publishes the CVE in full.
not published yet
Δ 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, not validated: no deterministic check could cover this one, and no technique passed our review.

source signals

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

  1. 2026-11-11 12:33Z

this entry in the feed

GET /api/v1/feed/ETK-2026-4199

{
  "etk_id": "ETK-2026-4199",
  "cve_id": null,
  "display_id": "ETK-2026-4199",
  "ghsa_id": "GHSA-6jwq-xf8q-xcwh",
  "euvd_id": null,
  "status": "published",
  "anchor_state": "awaiting_cve",
  "title": "Algorithmic denial of service in brace-expansion",
  "summary": "brace-expansion can spend excessive CPU time processing specially formed untrusted brace patterns, blocking a Node.js event loop. Applications are affected when they expand attacker-supplied patterns directly or through minimatch or glob with brace expansion enabled.",
  "mitigation": "Upgrade brace-expansion to 5.0.13, 3.0.10, 2.1.8, 1.1.22 or later.",
  "vendor": "npm",
  "product": "npm:brace-expansion",
  "affected": [
    {
      "affected_notes": [],
      "affected_ranges": [
        "< 1.1.22",
        ">= 2.0.0 < 2.1.8",
        ">= 3.0.0 < 3.0.10",
        ">= 4.0.0 < 5.0.13"
      ],
      "ecosystem": "npm",
      "fixed_versions": [
        "5.0.13",
        "3.0.10",
        "2.1.8",
        "1.1.22"
      ],
      "package_name": "brace-expansion",
      "purl": "pkg:npm/brace-expansion"
    }
  ],
  "cwes": [
    400
  ],
  "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": false,
  "check_confidence_basis": null,
  "exploit": false,
  "pipeline_minutes": 12.975819116666667,
  "t0_at": null,
  "signals": {
    "trigger_signal": {
      "at": "2026-11-11T12:33:35+00:00",
      "days": -0.34828028658564814,
      "is_lower_bound": true,
      "measured_at": "2026-11-11T20:55:06.458331+00:00",
      "url": "https://github.com/juliangruber/brace-expansion/security/advisories/GHSA-6jwq-xf8q-xcwh"
    }
  }
}

published 2026-11-11 18:41Z
last change 2026-11-11 20:44Z

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.