-
-
Notifications
You must be signed in to change notification settings - Fork 4
Description
Vulnerable Library - react-multi-crop-0.43.19.tgz
Path to dependency file: /package.json
Path to vulnerable library: /.yarn/cache/glob-npm-10.4.5-8c63175f05-698dfe1182.zip
Found in HEAD commit: 1a5ab1ea534c60892478a09868946226dba391a2
Vulnerabilities
| Vulnerability | Severity | Dependency | Type | Fixed in (react-multi-crop version) | Remediation Possible** | |
|---|---|---|---|---|---|---|
| CVE-2026-33671 | 7.5 | picomatch-4.0.3.tgz | Transitive | N/A* | ❌ | |
| CVE-2026-27904 | 7.5 | minimatch-9.0.5.tgz | Transitive | N/A* | ❌ | |
| CVE-2026-27903 | 7.5 | minimatch-9.0.5.tgz | Transitive | N/A* | ❌ | |
| CVE-2026-26996 | 7.5 | minimatch-9.0.5.tgz | Transitive | N/A* | ❌ | |
| CVE-2025-64756 | 7.5 | glob-10.4.5.tgz | Transitive | N/A* | ❌ | |
| CVE-2026-33750 | 6.5 | brace-expansion-2.0.2.tgz | Transitive | N/A* | ❌ | |
| CVE-2026-33672 | 5.3 | picomatch-4.0.3.tgz | Transitive | N/A* | ❌ |
*For some transitive vulnerabilities, there is no version of direct dependency with a fix. Check the "Details" section below to see if there is a version of transitive dependency where vulnerability is fixed.
**In some cases, Remediation PR cannot be created automatically for a vulnerability despite the availability of remediation
Details
CVE-2026-33671
Vulnerable Library - picomatch-4.0.3.tgz
Blazing fast and accurate glob matcher written in JavaScript, with no dependencies and full support for standard and extended Bash glob features, including braces, extglobs, POSIX brackets, and regular expressions.
Library home page: https://registry.npmjs.org/picomatch/-/picomatch-4.0.3.tgz
Path to dependency file: /package.json
Path to vulnerable library: /.yarn/cache/picomatch-npm-4.0.3-0a647b87cc-57b99055f4.zip
Dependency Hierarchy:
- react-multi-crop-0.43.19.tgz (Root Library)
- canvas-3.2.1.tgz
- node-gyp-11.5.0.tgz
- tinyglobby-0.2.15.tgz
- ❌ picomatch-4.0.3.tgz (Vulnerable Library)
- tinyglobby-0.2.15.tgz
- node-gyp-11.5.0.tgz
- canvas-3.2.1.tgz
Found in HEAD commit: 1a5ab1ea534c60892478a09868946226dba391a2
Found in base branch: main
Vulnerability Details
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.
Publish Date: 2026-03-26
URL: CVE-2026-33671
CVSS 3 Score Details (7.5)
Base Score Metrics:
- Exploitability Metrics:
- Attack Vector: Network
- Attack Complexity: Low
- Privileges Required: None
- User Interaction: None
- Scope: Unchanged
- Impact Metrics:
- Confidentiality Impact: None
- Integrity Impact: None
- Availability Impact: High
Suggested Fix
Type: Upgrade version
Release Date: 2026-03-25
Fix Resolution: https://github.com/micromatch/picomatch.git - 3.0.2,https://github.com/micromatch/picomatch.git - 4.0.4,https://github.com/micromatch/picomatch.git - 2.3.2
Step up your Open Source Security Game with Mend here
CVE-2026-27904
Vulnerable Library - minimatch-9.0.5.tgz
Library home page: https://registry.npmjs.org/minimatch/-/minimatch-9.0.5.tgz
Path to dependency file: /package.json
Path to vulnerable library: /.yarn/cache/minimatch-npm-9.0.5-9aa93d97fa-dd6a8927b0.zip
Dependency Hierarchy:
- react-multi-crop-0.43.19.tgz (Root Library)
- canvas-3.2.1.tgz
- node-gyp-11.5.0.tgz
- make-fetch-happen-14.0.3.tgz
- cacache-19.0.1.tgz
- glob-10.4.5.tgz
- ❌ minimatch-9.0.5.tgz (Vulnerable Library)
- glob-10.4.5.tgz
- cacache-19.0.1.tgz
- make-fetch-happen-14.0.3.tgz
- node-gyp-11.5.0.tgz
- canvas-3.2.1.tgz
Found in HEAD commit: 1a5ab1ea534c60892478a09868946226dba391a2
Found in base branch: main
Vulnerability Details
minimatch is a minimal matching utility for converting glob expressions into JavaScript RegExp objects. Prior to version 10.2.3, 9.0.7, 8.0.6, 7.4.8, 6.2.2, 5.1.8, 4.2.5, and 3.1.4, nested "()" extglobs produce regexps with nested unbounded quantifiers (e.g. "(?:(?:a|b))"), which exhibit catastrophic backtracking in V8. With a 12-byte pattern "(((a|b)))" and an 18-byte non-matching input, "minimatch()" stalls for over 7 seconds. Adding a single nesting level or a few input characters pushes this to minutes. This is the most severe finding: it is triggered by the default "minimatch()" API with no special options, and the minimum viable pattern is only 12 bytes. The same issue affects "+()" extglobs equally. Versions 10.2.3, 9.0.7, 8.0.6, 7.4.8, 6.2.2, 5.1.8, 4.2.5, and 3.1.4 fix the issue.
Publish Date: 2026-02-26
URL: CVE-2026-27904
CVSS 3 Score Details (7.5)
Base Score Metrics:
- Exploitability Metrics:
- Attack Vector: Network
- Attack Complexity: Low
- Privileges Required: None
- User Interaction: None
- Scope: Unchanged
- Impact Metrics:
- Confidentiality Impact: None
- Integrity Impact: None
- Availability Impact: High
Suggested Fix
Type: Upgrade version
Origin: GHSA-23c5-xmqv-rm74
Release Date: 2026-02-26
Fix Resolution: minimatch - 7.4.8,minimatch - 10.2.3,minimatch - 8.0.6,minimatch - 4.2.5,minimatch - 6.2.2,minimatch - 9.0.7,minimatch - 5.1.8,minimatch - 3.1.4
Step up your Open Source Security Game with Mend here
CVE-2026-27903
Vulnerable Library - minimatch-9.0.5.tgz
Library home page: https://registry.npmjs.org/minimatch/-/minimatch-9.0.5.tgz
Path to dependency file: /package.json
Path to vulnerable library: /.yarn/cache/minimatch-npm-9.0.5-9aa93d97fa-dd6a8927b0.zip
Dependency Hierarchy:
- react-multi-crop-0.43.19.tgz (Root Library)
- canvas-3.2.1.tgz
- node-gyp-11.5.0.tgz
- make-fetch-happen-14.0.3.tgz
- cacache-19.0.1.tgz
- glob-10.4.5.tgz
- ❌ minimatch-9.0.5.tgz (Vulnerable Library)
- glob-10.4.5.tgz
- cacache-19.0.1.tgz
- make-fetch-happen-14.0.3.tgz
- node-gyp-11.5.0.tgz
- canvas-3.2.1.tgz
Found in HEAD commit: 1a5ab1ea534c60892478a09868946226dba391a2
Found in base branch: main
Vulnerability Details
minimatch is a minimal matching utility for converting glob expressions into JavaScript RegExp objects. Prior to version 10.2.3, 9.0.7, 8.0.6, 7.4.8, 6.2.2, 5.1.8, 4.2.5, and 3.1.3, "matchOne()" performs unbounded recursive backtracking when a glob pattern contains multiple non-adjacent "**" (GLOBSTAR) segments and the input path does not match. The time complexity is O(C(n, k)) -- binomial -- where "n" is the number of path segments and "k" is the number of globstars. With k=11 and n=30, a call to the default "minimatch()" API stalls for roughly 5 seconds. With k=13, it exceeds 15 seconds. No memoization or call budget exists to bound this behavior. Any application where an attacker can influence the glob pattern passed to "minimatch()" is vulnerable. The realistic attack surface includes build tools and task runners that accept user-supplied glob arguments (ESLint, Webpack, Rollup config), multi-tenant systems where one tenant configures glob-based rules that run in a shared process, admin or developer interfaces that accept ignore-rule or filter configuration as globs, and CI/CD pipelines that evaluate user-submitted config files containing glob patterns. An attacker who can place a crafted pattern into any of these paths can stall the Node.js event loop for tens of seconds per invocation. The pattern is 56 bytes for a 5-second stall and does not require authentication in contexts where pattern input is part of the feature. Versions 10.2.3, 9.0.7, 8.0.6, 7.4.8, 6.2.2, 5.1.8, 4.2.5, and 3.1.3 fix the issue.
Publish Date: 2026-02-26
URL: CVE-2026-27903
CVSS 3 Score Details (7.5)
Base Score Metrics:
- Exploitability Metrics:
- Attack Vector: Network
- Attack Complexity: Low
- Privileges Required: None
- User Interaction: None
- Scope: Unchanged
- Impact Metrics:
- Confidentiality Impact: None
- Integrity Impact: None
- Availability Impact: High
Suggested Fix
Type: Upgrade version
Origin: GHSA-7r86-cg39-jmmj
Release Date: 2026-02-26
Fix Resolution: https://github.com/isaacs/minimatch.git - v9.0.7,https://github.com/isaacs/minimatch.git - v6.2.2,https://github.com/isaacs/minimatch.git - v4.2.5,https://github.com/isaacs/minimatch.git - v7.4.8,https://github.com/isaacs/minimatch.git - v5.1.8,https://github.com/isaacs/minimatch.git - v10.2.3,https://github.com/isaacs/minimatch.git - v8.0.6,https://github.com/isaacs/minimatch.git - v3.1.3
Step up your Open Source Security Game with Mend here
CVE-2026-26996
Vulnerable Library - minimatch-9.0.5.tgz
Library home page: https://registry.npmjs.org/minimatch/-/minimatch-9.0.5.tgz
Path to dependency file: /package.json
Path to vulnerable library: /.yarn/cache/minimatch-npm-9.0.5-9aa93d97fa-dd6a8927b0.zip
Dependency Hierarchy:
- react-multi-crop-0.43.19.tgz (Root Library)
- canvas-3.2.1.tgz
- node-gyp-11.5.0.tgz
- make-fetch-happen-14.0.3.tgz
- cacache-19.0.1.tgz
- glob-10.4.5.tgz
- ❌ minimatch-9.0.5.tgz (Vulnerable Library)
- glob-10.4.5.tgz
- cacache-19.0.1.tgz
- make-fetch-happen-14.0.3.tgz
- node-gyp-11.5.0.tgz
- canvas-3.2.1.tgz
Found in HEAD commit: 1a5ab1ea534c60892478a09868946226dba391a2
Found in base branch: main
Vulnerability Details
minimatch is a minimal matching utility for converting glob expressions into JavaScript RegExp objects. Versions prior to 10.2.1, 3.1.3, 4.2.4, 5.1.7, 6.2.1, 7.4.7, 8.0.5, and 9.0.6 are vulnerable to Regular Expression Denial of Service (ReDoS) when a glob pattern contains many consecutive * wildcards followed by a literal character that doesn't appear in the test string. Each * compiles to a separate [^/]*? regex group, and when the match fails, V8's regex engine backtracks exponentially across all possible splits. The time complexity is O(4^N) where N is the number of * characters. With N=15, a single minimatch() call takes ~2 seconds. With N=34, it hangs effectively forever. Any application that passes user-controlled strings to minimatch() as the pattern argument is vulnerable to DoS.
This issue has been fixed in versions 10.2.1, 3.1.3, 4.2.4, 5.1.7, 6.2.1, 7.4.7, 8.0.5, and 9.0.6.
Mend Note: The description of this vulnerability differs from MITRE.
Publish Date: 2026-02-20
URL: CVE-2026-26996
CVSS 3 Score Details (7.5)
Base Score Metrics:
- Exploitability Metrics:
- Attack Vector: Network
- Attack Complexity: Low
- Privileges Required: None
- User Interaction: None
- Scope: Unchanged
- Impact Metrics:
- Confidentiality Impact: None
- Integrity Impact: None
- Availability Impact: High
Suggested Fix
Type: Upgrade version
Origin: GHSA-3ppc-4f35-3m26
Release Date: 2026-02-19
Fix Resolution: https://github.com/isaacs/minimatch.git - v10.2.1,https://github.com/isaacs/minimatch.git - v7.4.7,https://github.com/isaacs/minimatch.git - v6.2.1,https://github.com/isaacs/minimatch.git - v3.1.3,https://github.com/isaacs/minimatch.git - v9.0.6,https://github.com/isaacs/minimatch.git - v4.2.4,https://github.com/isaacs/minimatch.git - v8.0.5,https://github.com/isaacs/minimatch.git - v5.1.7
Step up your Open Source Security Game with Mend here
CVE-2025-64756
Vulnerable Library - glob-10.4.5.tgz
Library home page: https://registry.npmjs.org/glob/-/glob-10.4.5.tgz
Path to dependency file: /package.json
Path to vulnerable library: /.yarn/cache/glob-npm-10.4.5-8c63175f05-698dfe1182.zip
Dependency Hierarchy:
- react-multi-crop-0.43.19.tgz (Root Library)
- canvas-3.2.1.tgz
- node-gyp-11.5.0.tgz
- make-fetch-happen-14.0.3.tgz
- cacache-19.0.1.tgz
- ❌ glob-10.4.5.tgz (Vulnerable Library)
- cacache-19.0.1.tgz
- make-fetch-happen-14.0.3.tgz
- node-gyp-11.5.0.tgz
- canvas-3.2.1.tgz
Found in HEAD commit: 1a5ab1ea534c60892478a09868946226dba391a2
Found in base branch: main
Vulnerability Details
Glob matches files using patterns the shell uses. Starting in version 10.2.0 and prior to versions 10.5.0 and 11.1.0, the glob CLI contains a command injection vulnerability in its -c/--cmd option that allows arbitrary command execution when processing files with malicious names. When glob -c are used, matched filenames are passed to a shell with shell: true, enabling shell metacharacters in filenames to trigger command injection and achieve arbitrary code execution under the user or CI account privileges. This issue has been patched in versions 10.5.0 and 11.1.0.
Mend Note: The description of this vulnerability differs from MITRE.
Publish Date: 2025-11-17
URL: CVE-2025-64756
CVSS 3 Score Details (7.5)
Base Score Metrics:
- Exploitability Metrics:
- Attack Vector: Network
- Attack Complexity: High
- Privileges Required: Low
- User Interaction: None
- Scope: Unchanged
- Impact Metrics:
- Confidentiality Impact: High
- Integrity Impact: High
- Availability Impact: High
Suggested Fix
Type: Upgrade version
Origin: GHSA-5j98-mcp5-4vw2
Release Date: 2025-11-17
Fix Resolution: https://github.com/isaacs/node-glob.git - v10.5.0,glob - 11.1.0,https://github.com/isaacs/node-glob.git - v11.1.0,glob - 10.5.0
Step up your Open Source Security Game with Mend here
CVE-2026-33750
Vulnerable Library - brace-expansion-2.0.2.tgz
Brace expansion as known from sh/bash
Library home page: https://registry.npmjs.org/brace-expansion/-/brace-expansion-2.0.2.tgz
Path to dependency file: /package.json
Path to vulnerable library: /.yarn/cache/brace-expansion-npm-2.0.2-bc7f134bbc-01dff195e3.zip
Dependency Hierarchy:
- react-multi-crop-0.43.19.tgz (Root Library)
- canvas-3.2.1.tgz
- node-gyp-11.5.0.tgz
- make-fetch-happen-14.0.3.tgz
- cacache-19.0.1.tgz
- glob-10.4.5.tgz
- minimatch-9.0.5.tgz
- ❌ brace-expansion-2.0.2.tgz (Vulnerable Library)
- minimatch-9.0.5.tgz
- glob-10.4.5.tgz
- cacache-19.0.1.tgz
- make-fetch-happen-14.0.3.tgz
- node-gyp-11.5.0.tgz
- canvas-3.2.1.tgz
Found in HEAD commit: 1a5ab1ea534c60892478a09868946226dba391a2
Found in base branch: main
Vulnerability Details
Impact A brace pattern with a zero step value (e.g., "{1..2..0}") causes the sequence generation loop to run indefinitely, making the process hang for seconds and allocate heaps of memory. The loop in question: https://github.com/juliangruber/brace-expansion/blob/daa71bcb4a30a2df9bcb7f7b8daaf2ab30e5794a/src/index.ts#L184 "test()" is one of https://github.com/juliangruber/brace-expansion/blob/daa71bcb4a30a2df9bcb7f7b8daaf2ab30e5794a/src/index.ts#L107-L113 The increment is computed as "Math.abs(0) = 0", so the loop variable never advances. On a test machine, the process hangs for about 3.5 seconds and allocates roughly 1.9 GB of memory before throwing a "RangeError". Setting max to any value has no effect because the limit is only checked at the output combination step, not during sequence generation. This affects any application that passes untrusted strings to expand(), or by error sets a step value of "0". That includes tools built on minimatch/glob that resolve patterns from CLI arguments or config files. The input needed is just 10 bytes. Patches Upgrade to versions - 5.0.5+ A step increment of 0 is now sanitized to 1, which matches bash behavior. Workarounds Sanitize strings passed to "expand()" to ensure a step value of "0" is not used.
Publish Date: 2026-03-26
URL: CVE-2026-33750
CVSS 3 Score Details (6.5)
Base Score Metrics:
- Exploitability Metrics:
- Attack Vector: Network
- Attack Complexity: Low
- Privileges Required: None
- User Interaction: Required
- Scope: Unchanged
- Impact Metrics:
- Confidentiality Impact: None
- Integrity Impact: None
- Availability Impact: High
Suggested Fix
Type: Upgrade version
Origin: GHSA-f886-m6hf-6m8v
Release Date: 2026-03-26
Fix Resolution: brace-expansion - 5.0.5
Step up your Open Source Security Game with Mend here
CVE-2026-33672
Vulnerable Library - picomatch-4.0.3.tgz
Blazing fast and accurate glob matcher written in JavaScript, with no dependencies and full support for standard and extended Bash glob features, including braces, extglobs, POSIX brackets, and regular expressions.
Library home page: https://registry.npmjs.org/picomatch/-/picomatch-4.0.3.tgz
Path to dependency file: /package.json
Path to vulnerable library: /.yarn/cache/picomatch-npm-4.0.3-0a647b87cc-57b99055f4.zip
Dependency Hierarchy:
- react-multi-crop-0.43.19.tgz (Root Library)
- canvas-3.2.1.tgz
- node-gyp-11.5.0.tgz
- tinyglobby-0.2.15.tgz
- ❌ picomatch-4.0.3.tgz (Vulnerable Library)
- tinyglobby-0.2.15.tgz
- node-gyp-11.5.0.tgz
- canvas-3.2.1.tgz
Found in HEAD commit: 1a5ab1ea534c60892478a09868946226dba391a2
Found in base branch: main
Vulnerability Details
Picomatch is a glob matcher written JavaScript. Versions prior to 4.0.4, 3.0.2, and 2.3.2 are vulnerable to a method injection vulnerability affecting the "POSIX_REGEX_SOURCE" object. Because the object inherits from "Object.prototype", specially crafted POSIX bracket expressions (e.g., "[[:constructor:]]") can reference inherited method names. These methods are implicitly converted to strings and injected into the generated regular expression. This leads to incorrect glob matching behavior (integrity impact), where patterns may match unintended filenames. The issue does not enable remote code execution, but it can cause security-relevant logic errors in applications that rely on glob matching for filtering, validation, or access control. All users of affected "picomatch" versions that process untrusted or user-controlled glob patterns are potentially impacted. 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 sanitizing or rejecting untrusted glob patterns, especially those containing POSIX character classes like "[[:...:]]"; avoiding the use of POSIX bracket expressions if user input is involved; and manually patching the library by modifying "POSIX_REGEX_SOURCE" to use a null prototype.
Publish Date: 2026-03-26
URL: CVE-2026-33672
CVSS 3 Score Details (5.3)
Base Score Metrics:
- Exploitability Metrics:
- Attack Vector: Network
- Attack Complexity: Low
- Privileges Required: None
- User Interaction: None
- Scope: Unchanged
- Impact Metrics:
- Confidentiality Impact: None
- Integrity Impact: Low
- Availability Impact: None
Suggested Fix
Type: Upgrade version
Release Date: 2026-03-25
Fix Resolution: https://github.com/micromatch/picomatch.git - 2.3.2,https://github.com/micromatch/picomatch.git - 3.0.2,https://github.com/micromatch/picomatch.git - 4.0.4
Step up your Open Source Security Game with Mend here