Picomatch is a glob matcher written JavaScript. Versions prior to 4.0.4, 3.0.2, and 2.3.2 are vulnerable to Regular Expression Denial of Service (ReDoS) when processing crafted extglob patterns. Certain patterns using extglob quantifiers such as +() and *(), especially when combined with overlapping alternatives or nested extglobs, are compiled into regular expressions that can exhibit catastrophic backtracking on non-matching input. Applications are impacted when they allow untrusted users to supply glob patterns that are passed to picomatch for compilation or matching. In those cases, an attacker can cause excessive CPU consumption and block the Node.js event loop, resulting in a denial of service. Applications that only use trusted, developer-controlled glob patterns are much less likely to be exposed in a security-relevant way. This issue is fixed in picomatch 4.0.4, 3.0.2 and 2.3.2. Users should upgrade to one of these versions or later, depending on their supported release line. If upgrading is not immediately possible, avoid passing untrusted glob patterns to picomatch. Possible mitigations include disabling extglob support for untrusted patterns by using noextglob: true, rejecting or sanitizing patterns containing nested extglobs or extglob quantifiers such as +() and *(), enforcing strict allowlists for accepted pattern syntax, running matching in an isolated worker or separate process with time and resource limits, and applying application-level request throttling and input validation for any endpoint that accepts glob patterns.
CVE-2026-33671
This high-severity CVE scores 7.5 under a secondary CVSS source (NVD's own analysis pending). EPSS exploit probability: 0.4%, top 66% of all CVEs by exploit prediction. GitHub Security Advisory data not yet ingested — confidence will rise once GHSA publishes (typical lag: hours to days for open-source ecosystem CVEs; never for infrastructure-only CVEs).
- High severity, but no confirmed exploitation yet
A fix is available — apply it.
- CVSS v3
- 7.5
- EG Score
- 7.5(medium)
- EG Risk
- 49(Track)EG Risk 49/100SSVC: Track
EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).
How it’s computedSeverity75% × 45%Exploitation0% × 40%Automatability100% × 15%Action: Routine — remediate on your standard cadence. - EPSS PROB
- 0%
- EPSS %ILE
- 34%
- KEV
- Not listed
Published
March 26, 2026
Last Modified
June 17, 2026
Advisory Details (2)
Auto-updated Aug 2, 2026ReDoS via Extglob Quantifiers in picomatch · Advisory · micromatch/picomatch · GitHub
https://github.com/micromatch/picomatch/security/advisories/GHSA-c2c7-rcm5-vvqjcommit 5eceecd27543 (micromatch/picomatch)
Patch available: micromatch/picomatch 4.0.4 (contains commit 5eceecd27543)
https://github.com/micromatch/picomatch/commit/5eceecd27543b8e056b9307d69e105ea03618a7dVendor Advisories for CVE-2026-33671(4)
These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.
- RHSA-2026:56928Red Hat Product SecurityHigh
Red Hat Security Advisory: Red Hat OpenShift Data Foundation 4.22.2 security, enhancement & bug fix update
- RHSA-2026:56431Red Hat Product SecurityHigh
Red Hat Security Advisory: Red Hat OpenShift Data Foundation 4.18.27 security, enhancement & bug fix update
- RHSA-2026:34342Red Hat Product SecurityCritical
Red Hat Security Advisory: Cluster Observability Operator 1.5.0
- CVE-2026-33671Microsoft Security Response Center (MSRC)High
Picomatch has a ReDoS vulnerability via extglob quantifiers
Patch Availability(1)
| Vendor / Ecosystem | Fixed in / Patch | Released | Source |
|---|---|---|---|
| redhat | cluster-observability-operator/troubleshooting-panel-console-plugin-pf6-rhel9:1782839996 | 2026-07-01 | redhat |
Patches are aggregated from vendor advisories (Red Hat, Microsoft, Cisco, GitHub) and package ecosystems (OSV, GHSA). Multiple rows for the same upstream release have been deduplicated.
Affected Packages
(5 across 5 ecosystems)
Debian:11(1)
| Package | Vulnerable range | Fixed in | Dependents |
|---|---|---|---|
| node-anymatch | 3.1.1+~2.2.2-1 ... 3.1.3+~cs8.0.6-1 (7 versions) | — | — |
Debian:12(1)
| Package | Vulnerable range | Fixed in | Dependents |
|---|---|---|---|
| node-anymatch | 3.1.3+~cs4.6.1-2, 3.1.3+~cs8.0.5-1, 3.1.3+~cs8.0.6-1 | — | — |
Debian:13(1)
| Package | Vulnerable range | Fixed in | Dependents |
|---|---|---|---|
| node-anymatch | 3.1.3+~cs4.6.1-2, 3.1.3+~cs8.0.5-1, 3.1.3+~cs8.0.6-1 | — | — |
Debian:14(1)
| Package | Vulnerable range | Fixed in | Dependents |
|---|---|---|---|
| node-anymatch | 3.1.3+~cs4.6.1-2, 3.1.3+~cs8.0.5-1 | 3.1.3+~cs8.0.6-1 | — |
npm(1)
| Package | Vulnerable range | Fixed in | Dependents |
|---|---|---|---|
| picomatch | — | 2.3.2 | — |
Weakness Classification(1)
MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.
Data Freshness Timeline
(refreshed 8× in last 7d / 31× in last 30d)
Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.
- 2026-09-18 19:28 UTCEPSS rescore
- 2026-09-18 19:28 UTCEPSS rescore
- 2026-09-17 19:30 UTCEPSS rescore
- 2026-09-16 14:08 UTCEPSS rescore
- 2026-09-16 05:15 UTCEPSS rescore
- 2026-09-15 03:11 UTCEPSS rescore
- 2026-09-13 16:47 UTCEPSS rescore
- 2026-09-12 15:01 UTCEPSS rescore
- 2026-09-11 14:53 UTCEPSS rescore
- 2026-09-11 09:37 UTCEPSS rescore
- 2026-09-10 09:34 UTCEPSS rescore
- 2026-09-08 22:00 UTCEPSS rescore
- 2026-09-07 16:01 UTCEPSS rescore
- 2026-09-06 13:47 UTCEPSS rescore
- 2026-09-04 05:06 UTCEPSS rescore
- 2026-09-02 14:11 UTCEPSS rescore
- 2026-09-02 13:26 UTCOSV refresh
- 2026-09-01 13:53 UTCEPSS rescore
- 2026-09-01 04:39 UTCEPSS rescore
- 2026-09-01 04:39 UTCEPSS rescore
- 2026-08-30 19:17 UTCEPSS rescore
- 2026-08-30 01:22 UTCEPSS rescore
- 2026-08-28 21:41 UTCEPSS rescore
- 2026-08-27 14:25 UTCEPSS rescore
- 2026-08-26 14:46 UTCEPSS rescore
Show 56 moreShow fewer
- 2026-08-25 13:49 UTCEPSS rescore
- 2026-08-24 14:17 UTCEPSS rescore
- 2026-08-23 00:19 UTCEPSS rescore
- 2026-08-21 23:49 UTCEPSS rescore
- 2026-08-20 22:55 UTCEPSS rescore
- 2026-08-20 22:55 UTCEPSS rescore
- 2026-08-19 17:03 UTCEPSS rescore
- 2026-08-18 13:48 UTCEPSS rescore
- 2026-08-17 13:47 UTCEPSS rescore
- 2026-08-16 14:56 UTCEPSS rescore
- 2026-08-16 10:05 UTCEG score recompute
- 2026-08-16 10:05 UTCVendor advisory
- 2026-08-16 02:14 UTCEPSS rescore
- 2026-08-15 01:30 UTCEPSS rescore
- 2026-08-14 19:26 UTCVendor advisory
- 2026-08-14 06:23 UTCEG score recompute
- 2026-08-14 06:23 UTCVendor advisory
- 2026-08-13 22:00 UTCEPSS rescore
- 2026-08-12 20:40 UTCEG score recompute
- 2026-08-12 20:40 UTCVendor advisory
- 2026-08-12 13:50 UTCEPSS rescore
- 2026-08-11 20:48 UTCEG score recompute
- 2026-08-11 20:48 UTCVendor advisory
- 2026-08-11 03:50 UTCEG score recompute
- 2026-08-11 03:50 UTCVendor advisory
- 2026-08-11 00:00 UTCEPSS rescore
- 2026-08-10 07:24 UTCVendor advisory
- 2026-08-09 18:40 UTCEG score recompute
- 2026-08-09 18:40 UTCVendor advisory
- 2026-08-09 13:46 UTCEPSS rescore
- 2026-08-09 05:56 UTCEG score recompute
- 2026-08-09 05:56 UTCVendor advisory
- 2026-08-08 16:37 UTCEPSS rescore
- 2026-08-08 05:06 UTCEG score recompute
- 2026-08-08 05:06 UTCVendor advisory
- 2026-08-07 16:22 UTCVendor advisory
- 2026-08-06 18:45 UTCEG score recompute
- 2026-08-06 18:45 UTCVendor advisory
- 2026-08-06 13:46 UTCEPSS rescore
- 2026-08-06 00:50 UTCEG score recompute
- 2026-08-06 00:50 UTCVendor advisory
- 2026-08-05 19:17 UTCEPSS rescore
- 2026-08-04 15:10 UTCEPSS rescore
- 2026-08-04 10:38 UTCEPSS rescore
- 2026-08-03 23:14 UTCEG score recompute
- 2026-08-03 23:14 UTCVendor advisory
- 2026-08-03 10:36 UTCEPSS rescore
- 2026-08-02 15:16 UTCEG score recompute
- 2026-08-02 15:16 UTCVendor advisory
- 2026-08-02 02:27 UTCEPSS rescore
- 2026-08-01 04:16 UTCEPSS rescore
- 2026-07-30 16:28 UTCEPSS rescore
- 2026-07-30 01:30 UTCEPSS rescore
- 2026-07-27 14:13 UTCEPSS rescore
- 2026-07-27 12:50 UTCEG score recompute
- 2026-07-27 12:50 UTCVendor advisory
Frequently asked(5)
What is CVE-2026-33671?
When was CVE-2026-33671 disclosed?
Is CVE-2026-33671 actively exploited?
What is the CVSS score of CVE-2026-33671?
How do I remediate CVE-2026-33671?
Dependency Blast Radius
See which npm, PyPI, Go, and Maven packages are affected by CVE-2026-33671
Is Your Infrastructure Affected by CVE-2026-33671?
EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.