Skip to content

Applications

CVE-2026-112366

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

CVSS
8.7Highscored by the publisher (CNA)
Exploited in the wild
Not knownnot in CISA KEV as of our last sync
EPSS
0.34%chance of exploitation in the next 30 daystop 73% of scored CVEsFIRST score of 13 Nov 2026
Fix
Not stated by the vendorno fixed release in the CVE record
Published
19 Oct 2026analysed here 20 Oct 2026

Summary

Impact

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

Triage

Exploitable
At runtime
Attack vector
network
Weakness
Can a WAF block it?
Partly. See why

Executive summary (AI-written)

A significant vulnerability (CVE-2026-112366) has been identified in the picomatch library, which is prevalent in Node.js applications and their dependencies. The vulnerability allows for a denial of service (DoS) through crafted extglob patterns, resulting in severe performance degradation as affected applications struggle to process these inputs. This could lead to prolonged outages for businesses relying on these applications, impacting their operations and customer satisfaction. While the severity is classified as standard with a CVSS score of 8.7, it represents a serious risk given its potential to disrupt application performance under certain conditions. Given that patching is not currently available, it is essential for organizations to take immediate action to mitigate this risk. Businesses should prioritize reviewing their applications for usage of the picomatch library and validate any user input that may leverage these glob patterns. When a patch becomes available, organizations must ensure that it is applied promptly to safeguard their systems from this vulnerability and maintain operational integrity.

Technical analysis (AI-written)

CVE-2026-112366 presents a ReDoS (Regular Expression Denial of Service) vulnerability in picomatch versions 4.0.7 or earlier, specifically applicable to Node.js applications utilizing this library. This vulnerability exploits the way certain crafted extglob patterns, such as '+(*)', can cause exponential backtracking within regular expression processing. Consequently, applications that make use of the picomatch library can experience significant performance degradation under the right conditions, effectively blocking the Node.js event loop and rendering the application unresponsive. The CVSS score of 8.7 indicates that while this vulnerability is serious, it does not represent a complete infrastructure failure akin to incidents like Log4Shell. The attack vector primarily involves sending crafted requests to an application that uses picomatch to process user-supplied glob patterns. Given the nature of the vulnerability, the exploitation complexity is rated as low; even users with moderate technical skills can potentially craft inputs that will trigger the backtracking issue. This makes it a considerable threat for any Node.js applications that accept user-generated glob patterns without appropriate validation. Mitigation strategies currently involve validating or sanitizing user input to prevent malicious glob patterns from being processed. It is recommended that organizations immediately assess their exposure by identifying all dependencies on picomatch and understanding where user input may include extglob patterns. Implementing input validation that limits or sanitizes these patterns can help mitigate the risk until a patched version of picomatch is available. In the absence of an immediate patch, maintaining an active inventory of npm packages and their versions is critical. Organizations should subscribe to updates or mailing lists associated with picomatch to stay informed about announcements regarding a fixed release. Additionally, testing applications for potential impacts, particularly those dependent on micromatch, is prudent to ensure that existing functionalities do not become a vector for Denial of Service. Post-mitigation, continuous monitoring of the application’s performance and user input handling will be crucial in minimizing the risk of exploitation until a complete resolution is implemented.

The summary, impact and action text on this page are written by our AI analysis pipeline, or taken from the NVD description when a CVE was imported from NVD. They are not the vendor's wording: check them against the sources.

Affected products

ProductAffected versions
micromatch picomatch<= 4.0.7Vendor says fixed in: not stated

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.

Products named in our analysis

  • picomatch <= 4.0.7
  • Node.js applications using picomatch/micromatch
  • npm packages depending on picomatch

Fix and mitigation

Action required

Patch when possible

WAF and other mitigations

Can a WAF block it? Partly. The bug can be reached over the network, so generic WAF rules may stop some attacks. Its weakness type is unknown, so we cannot be more precise.

Also consider: patch

Based on the weakness type only; no CVE-specific evidence yet. We check Cloudflare, AWS, Google Cloud Armor and Azure; for Akamai, Imperva, Fastly, F5, ask your vendor.

Remediation steps (AI-written)

Step-by-step remediation is generated for accounts on the Max plan, for CVEs that match a technology in their stack. Add this technology to your stack to see the fix checklist.

Exploitation evidence

CISA KEV catalog
Not listed as of our last sync.
Public exploit code
None on record in Exploit-DB, Metasploit, Nuclei templates or PoC-in-GitHub.
CISA SSVC
exploitation none, automatable yes, technical impact partialAssessed by CISA 19 Oct 2026 (SSVC 2.0.3). Exploitation is none, poc (public proof of concept) or active.

Timeline

  1. 19 Oct 2026Published
  2. 19 Oct 2026CISA SSVC assessment: exploitation nonesame day later
  3. 19 Oct 2026CVE record last updatedsame day later
  4. 20 Oct 2026Analysed by vulneraibility.com1 day later

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. EPSS currently estimates a 0.34% probability of exploitation in the next 30 days.

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.

References

NVDCVE.orgCVE DetailsSource

3 references in the CVE record, grouped by the tags the record gives them.

Advisories (1)

  • vulncheck.com /advisories/picomatch-through-4.0.7-redos-via-single-branch-repeated-extglob-pat

Patches (1)

Other links (1)

  • github.com /micromatch/picomatch/blob/4.0.7/lib/parse.js#L287-L307

Where the data on this page comes from

Summary, impact and triage tags: written by our AI analysis pipeline from the sources above. Check them against the sources.

Similar CVEs

Get CVEs like this by email. Join the free digest: the CVEs we flag as major, all CVSS 8.0 or higher, in up to three emails a day (sent at 05:00, 11:00 and 15:00 UTC). Matching alerts to the products you run needs an account, and accounts are invite-only during the beta.

© 2026 vulneraibility.com