Skip to main content
VulnerabilityPublished Updated

CVE-2026-112366: picomatch vulnerable to ReDoS through single-branch repeated extglobs

Affects picomatchSource GCVE Database

0
Compare
Authoritative record:CVE-2026-112366· High 8.7

Not known to be exploited · CVSS 8.7 High.

Data as of 17 Nov 2026, 16:50 UTC

CVSS 4.0 base score
8.7High
How severe the flaw is on the 0–10 CVSS scale.
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

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 19 Oct 2026

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponized: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 16 Nov 2026.

What to do

Affected software

ProductAffectedFixed in
npmpicomatchAffected
  • <=4.0.7
Fixed in–

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

AI-suggested

Until a fix is available, avoid processing untrusted input with single-branch repeated extglob patterns or implement input validation to reject such patterns.

Description

Picomatch versions up to 4.0.7 are affected by a regular expression denial of service (ReDoS) vulnerability. This flaw arises from single-branch repeated extglob patterns that cause exponential backtracking, allowing attackers to block the Node.js event loop and cause denial of service.

References

Community reviews

Loading reviews…