CVSS 4.0
8.7 highCVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:N/VI:N/VA:H/SC:N/SI:N/SA:NHigh (8.7) in micromatch picomatch. EPSS 0.3% estimated probability of exploitation activity in the next 30 days.
CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:N/VI:N/VA:H/SC:N/SI:N/SA:NCVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:HExplain CVE-2026-112366 for an engineer deciding whether to act. Use https://cve.bz/api/public/cves/CVE-2026-112366?via=ask-ai-copy and https://cve.bz/cve/CVE-2026-112366?via=ask-ai-copy as the source of truth: what is affected and which versions fix it, whether it is in CISA KEV, public exploits, and its EPSS (an internet-wide 30-day estimate of exploitation activity, not a forecast for my systems). If they give no fixed versions, use the CVE record https://cveawg.mitre.org/api/cve/CVE-2026-112366 or the vendor advisory, not third-party mirrors. Tell me how to check whether I am affected and how to verify a fix. Cite the sources and say where they are uncertain.Opens a third-party assistant; its answer is its own, not cve.bz's. The prompt holds only this CVE's id and public links.
From the CNA's record in the CVE List.
| Product | Affected |
|---|---|
| micromatch picomatch | through 4.0.7 |
| Advisory | Ecosystem | Package | Affected | Fixed in |
|---|---|---|---|---|
| GHSA-fc5q-39xc-vjpf | npm | picomatch | <=4.0.7 | no fix published |
| Distribution | Release | Package | Fixed in | Advisory |
|---|---|---|---|---|
| Debian | 12, 13, 14 | node-anymatch | no fix listed | DEBIAN-CVE-2026-112366 |
| Ubuntu | 18.04:LTS, 20.04:LTS, 22.04:LTS and 3 more | node-anymatch | no fix listed | UBUNTU-CVE-2026-112366 |
| openSUSE | Tumbleweed | git-bug | 0.11.0-3.1 | openSUSE-SU-2026:12261-1 |
| openSUSE | Tumbleweed | pi-coding-agent | 1.5.0-1.1 | openSUSE-SU-2026:12421-1 |
| Azure Linux | 3 | nodejs | no fix listed | AZL-110055 |
| Azure Linux | 3 | nodejs-nodemon | no fix listed | AZL-109833 |
| Azure Linux | 3 | python-tensorboard | no fix listed | AZL-110085 |
From the distributions' data via OSV.dev: the Debian Security Tracker; Ubuntu Security Notices © Canonical Ltd., CC BY-SA 4.0; SUSE security data, CC BY 4.0; Microsoft's Azure Linux vulnerability data, MIT. Modified: reformatted and linked to CVE records. Credits. On the distributions' own pages: Debian · Ubuntu · openSUSE.
Red Hat rates this Important.
This vulnerability is rated as having an Important severity for Red Hat products because an unauthenticated remote attacker can completely stall the single-threaded Node.js runtime without requiring specialized privileges. In Red Hat environments, picomatch is embedded as a dependency within containerized services and development tooling to evaluate file paths and route expressions. When applications accept untrusted glob patterns, the resulting algorithmic complexity blocks event processing across all concurrent connections handled by the affected process.
--- CME Mitigation Guidance (2026-10-20) ---
Disclaimer: The following mitigation solutions are provided as a courtesy, pending the application of an official patch. This content was generated utilizing AI tools in conjunction with data from https://cmetaxonomy.org. Customers are advised to independently evaluate and test these temporary mitigations within their own infrastructure.
The highest-value action is to enforce execution timeouts and step limits on pattern-matching operations, or reject untrusted single-branch repeated extglob expressions before evaluating them with picomatch: upgrade to the fixed Llvm/Swift Lang/Grafana/Prometheus/Ruff/Dotnet/Rust/Yarnpkg builds, which mark mixed wildcards as risky across all branch counts within analyzeRepeatedExtglob, closing all 2 injection vectors (crafted single-branch repeated extglob patterns, crafted input strings triggering catastrophic backtracking). Until patched, this is a concern on Applications evaluating attacker-controlled glob patterns or matching untrusted inputs against repeated extglobs, so Validate and reject untrusted glob patterns containing single-branch repeated extglobs such as +(*) or +(*a) before passing them to picomatch, and avoid evaluating untrusted input strings against repeated extglob patterns. These controls limit blast radius and contain exploitation, but they do not fix the underlying regular expression catastrophic backtracking defect — apply the upstream patch to fully remediate.
Highest-impact CME: CME-1316 Algorithmic Complexity Safeguards (Pattern/Regex Execution Limits) (high)
| Product | Package | State | Advisory |
|---|---|---|---|
| Red Hat Hardened Images | dotnet8.0 | Not affected | |
| Red Hat Hardened Images | grafana12.4 | Affected | |
| Red Hat Hardened Images | grafana13.1 | Affected | |
| Red Hat Hardened Images | grafana13.2 | Affected | |
| Red Hat Hardened Images | llvm21 | Not affected | |
| Red Hat Hardened Images | prometheus3.13 | Affected | |
| Red Hat Hardened Images | prometheus3.5 | Will not fix | |
| Red Hat Hardened Images | ruff | Not affected | |
| Red Hat Hardened Images | rust | Not affected | |
| Red Hat Hardened Images | swift-lang | Not affected | |
| Red Hat Hardened Images | yarnpkg | Not affected |
Contains Red Hat Security Data © Red Hat, Inc., licensed under CC BY 4.0. Source: https://access.redhat.com/security/data. Modified: reformatted. Red Hat's page for CVE-2026-112366.
The attack patterns MITRE's CAPEC relates to this record's weaknesses, as MITRE names them. Credits.