Skip to content
Fencer Intel
high 7.5

CVE-2026-112366 json

Picomatch through 4.0.7 ReDoS via single-branch repeated extglob patterns

published 21d ago modified 21d ago also EUVD-2026-104404

cvss
7.5
version 3.1, CNA
cisa kev
Not listed
not in CISA's catalog
epss
0.3%
EPSS 0.3% chance of exploitation in 30 days, percentile 27%
public exploits
0
none known

Summary

Picomatch through 4.0.7 contains a regular expression denial of service vulnerability that allows attackers to block the event loop by supplying single-branch repeated extglob patterns. Attackers can provide globs like +(*) or +(*a), which analyzeRepeatedExtglob in lib/parse.js skips, causing exponential backtracking against short crafted strings and denying service to Node.js applications.

Patch / fix

  • pi-coding-agent openSUSE Tumbleweed 1.5.0-1.1
  • git-bug openSUSE Tumbleweed 0.11.0-3.1

opensuse advisories openSUSE-SU-2026:12421-1openSUSE-SU-2026:12261-1

Is CVE-2026-112366 in your stack? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.

Check with Fencer

Vendor advisories

What the vendors themselves say about their products: affected, fixed or not affected, and what to do.

red hat product security vex CVE-2026-112366 updated cvss 7.5

picomatch: picomatch: Denial of Service via single-branch repeated extglob patterns

  • Red Hat Hardened Images grafana13.1 13.1.7-0.2.hum1, grafana13.2 13.2.3-0.2.hum1, grafana12.4 12.4.12-0.5.hum1, prometheus3.5 3.5.5-0.8.hum1, prometheus3.13 3.13.4-0.1.hum1
    affected: workaround, no fix available, no fix planned “Will not fix”
  • Red Hat Hardened Images rust 1.99.1-1.1.hum1, ruff 0.15.11-1.1.hum1, llvm21 21.1.8-10.1.hum1, swift-lang 6.4.1-0.1.hum1, yarnpkg 1.22.22-18.1.hum1, dotnet8.0 8.0.131-0.2.hum1
    not affected: component not present

Red Hat CSAF VEX © Red Hat, Inc., from https://security.access.redhat.com/data/csaf/v2/vex/; changed: reduced to product statuses and remediations. CC BY 4.0 · csaf

CISA SSVC

Exploitation
none
Automatable
yes
Technical impact
partial
Assessed
21d ago

Exploit prediction

0.34% chance of exploitation in the next 30 days, higher than 27% of all scored CVEs (FIRST EPSS, 2026-11-09).

CVSS scores

assigned by version score vector
CNA 4.0 8.7 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
CNA 3.1 7.5 CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H
CNA 4.0 8.7 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/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X

Affected products

  • micromatch picomatch

Classification

Weakness
  • CWE-1333 Inefficient Regular Expression Complexity

References

Sources

Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.

CPEs and fixed versions use Anchore's correction of NVD's data: Added CPE configurations because not yet analyzed by NVD.