Skip to content
Applications

CVE-2026-112366

8.7
High
EPSS n/aOct 20, 2026

ReDoS in picomatch <=4.0.7 allows event-loop DoS via crafted extglob patterns

common questions

Is CVE-2026-112366 being exploited?

Not confirmed. CVE-2026-112366 does not appear in CISA's Known Exploited Vulnerabilities catalog, which records only exploitation that has been observed and reported publicly. That is evidence of absence of a report, not evidence the flaw is unattacked.

How severe is CVE-2026-112366?

CVE-2026-112366 is rated High with a CVSS score of 8.7. Severity describes how bad exploitation would be, not how likely it is: pair it with exploitation evidence before deciding what to patch first.

Is there a patch for CVE-2026-112366?

Not known from our data. No patch reference has been recorded for CVE-2026-112366, which is not the same as no patch existing — a fix may have shipped without a tagged reference, or after this record was written. The vendor advisory is the only authority on whether a fix exists, and mitigations may be available regardless.

What does CVE-2026-112366 affect?

CVE-2026-112366 affects picomatch <= 4.0.7, Node.js applications using picomatch/micromatch, npm packages depending on picomatch. Confirm the exact affected versions against the vendor advisory before deciding you are exposed.

What should I do about CVE-2026-112366?

Upgrade to a patched picomatch release when available; validate/sanitize user-supplied glob patterns.

Exploitation status reflects CISA's KEV catalog as we last synced it. Check the catalog directly.

executive summary
technical analysis
affected
picomatch <= 4.0.7Node.js applications using picomatch/micromatchnpm packages depending on picomatch
impact

Exponential regex backtracking from crafted extglobs (e.g., +(*)) blocks Node.js event loop, causing denial of service to affected apps.

action required

Patch when possible

affected versions
micromatch picomatch
  • affected<= 4.0.7

As published in the CVE Program record. A version outside these ranges is not a statement that it is unaffected — vendors sometimes understate a range, and distribution-backported builds carry upstream numbers that do not reflect what was patched into them.

how to fix
Remediation steps are tailored for users whose stack is affected. Add this technology to your stack to see the fix checklist.
references
get alerted

Track only the vulnerabilities that affect your infrastructure.

start for free