-
Notifications
You must be signed in to change notification settings - Fork 1
copy-webpack-plugin-11.0.0.tgz: 7 vulnerabilities (highest severity is: 8.7) #5
Description
Vulnerable Library - copy-webpack-plugin-11.0.0.tgz
Path to dependency file: /package.json
Path to vulnerable library: /node_modules/picomatch/package.json
Vulnerabilities
| Vulnerability | Severity | Dependency | Type | Fixed in (copy-webpack-plugin version) | Remediation Possible** | |
|---|---|---|---|---|---|---|
| CVE-2026-33671 | 8.7 | picomatch-2.3.1.tgz | Transitive | N/A* | ❌ | |
| CVE-2024-4068 | 8.7 | braces-3.0.2.tgz | Transitive | N/A* | ❌ | |
| CVE-2026-34043 | 8.2 | serialize-javascript-6.0.1.tgz | Transitive | N/A* | ❌ | |
| CVE-2026-33672 | 6.9 | picomatch-2.3.1.tgz | Transitive | N/A* | ❌ | |
| CVE-2024-4067 | 6.9 | micromatch-4.0.5.tgz | Transitive | 12.0.0 | ✅ | |
| CVE-2024-11831 | 5.1 | serialize-javascript-6.0.1.tgz | Transitive | N/A* | ❌ | |
| CVE-2025-69873 | 1.2 | ajv-8.12.0.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-2.3.1.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-2.3.1.tgz
Path to dependency file: /package.json
Path to vulnerable library: /node_modules/picomatch/package.json
Dependency Hierarchy:
- copy-webpack-plugin-11.0.0.tgz (Root Library)
- fast-glob-3.3.1.tgz
- micromatch-4.0.5.tgz
- ❌ picomatch-2.3.1.tgz (Vulnerable Library)
- micromatch-4.0.5.tgz
- fast-glob-3.3.1.tgz
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 4 Score Details (8.7)
Base Score Metrics:
- Exploitability Metrics:
- Attack Vector: Network
- Attack Complexity: Low
- Privileges Required: None
- User Interaction: None
- Scope: N/A
- Impact Metrics:
- Confidentiality Impact: N/A
- Integrity Impact: N/A
- Availability Impact: N/A
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
CVE-2024-4068
Vulnerable Library - braces-3.0.2.tgz
Bash-like brace expansion, implemented in JavaScript. Safer than other brace expansion libs, with complete support for the Bash 4.3 braces specification, without sacrificing speed.
Library home page: https://registry.npmjs.org/braces/-/braces-3.0.2.tgz
Path to dependency file: /package.json
Path to vulnerable library: /node_modules/braces/package.json
Dependency Hierarchy:
- copy-webpack-plugin-11.0.0.tgz (Root Library)
- fast-glob-3.3.1.tgz
- micromatch-4.0.5.tgz
- ❌ braces-3.0.2.tgz (Vulnerable Library)
- micromatch-4.0.5.tgz
- fast-glob-3.3.1.tgz
Found in base branch: main
Vulnerability Details
The NPM package "braces", versions prior to 3.0.3, fails to limit the number of characters it can handle, which could lead to Memory Exhaustion. In "lib/parse.js," if a malicious user sends "imbalanced braces" as input, the parsing will enter a loop, which will cause the program to start allocating heap memory without freeing it at any moment of the loop. Eventually, the JavaScript heap limit is reached, and the program will crash. After conducting a further research, it was concluded that CVE-2024-4068 does not contain a high security risk that reflects the NVD score, but should be kept for users' awareness. Users of braces should follow the fix recommendation as noted.
Publish Date: 2024-05-13
URL: CVE-2024-4068
CVSS 4 Score Details (8.7)
Base Score Metrics:
- Exploitability Metrics:
- Attack Vector: Network
- Attack Complexity: Low
- Privileges Required: None
- User Interaction: None
- Scope: N/A
- Impact Metrics:
- Confidentiality Impact: N/A
- Integrity Impact: N/A
- Availability Impact: N/A
Suggested Fix
Type: Upgrade version
Release Date: 2024-05-13
Fix Resolution: braces - 3.0.3
CVE-2026-34043
Vulnerable Library - serialize-javascript-6.0.1.tgz
Library home page: https://registry.npmjs.org/serialize-javascript/-/serialize-javascript-6.0.1.tgz
Path to dependency file: /package.json
Path to vulnerable library: /node_modules/serialize-javascript/package.json
Dependency Hierarchy:
- copy-webpack-plugin-11.0.0.tgz (Root Library)
- ❌ serialize-javascript-6.0.1.tgz (Vulnerable Library)
Found in base branch: main
Vulnerability Details
Impact What kind of vulnerability is it? It is a Denial of Service (DoS) vulnerability caused by CPU exhaustion. When serializing a specially crafted "array-like" object (an object that inherits from "Array.prototype" but has a very large "length" property), the process enters an intensive loop that consumes 100% CPU and hangs indefinitely. Who is impacted? Applications that use "serialize-javascript" to serialize untrusted or user-controlled objects are at risk. While direct exploitation is difficult, it becomes a high-priority threat if the application is also vulnerable to Prototype Pollution or handles untrusted data via YAML Deserialization, as these could be used to inject the malicious object. Patches Has the problem been patched? Yes, the issue has been patched by replacing "instanceof Array" checks with "Array.isArray()" and using "Object.keys()" for sparse array detection. What versions should users upgrade to? Users should upgrade to "v7.0.5" or later. Workarounds Is there a way for users to fix or remediate the vulnerability without upgrading? There is no direct code-level workaround within the library itself. However, users can mitigate the risk by: * Validating and sanitizing all input before passing it to the "serialize()" function. * Ensuring the environment is protected against Prototype Pollution. * Upgrading to "v7.0.5" as soon as possible. Acknowledgements Serialize JavaScript thanks Tomer Aberbach (@TomerAberbach) for discovering and privately disclosing this issue.
Publish Date: 2026-03-27
URL: CVE-2026-34043
CVSS 4 Score Details (8.2)
Base Score Metrics:
- Exploitability Metrics:
- Attack Vector: Network
- Attack Complexity: High
- Privileges Required: None
- User Interaction: None
- Scope: N/A
- Impact Metrics:
- Confidentiality Impact: N/A
- Integrity Impact: N/A
- Availability Impact: N/A
Suggested Fix
Type: Upgrade version
Origin: GHSA-qj8w-gfj5-8c6v
Release Date: 2026-03-27
Fix Resolution: serialize-javascript - 7.0.5
CVE-2026-33672
Vulnerable Library - picomatch-2.3.1.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-2.3.1.tgz
Path to dependency file: /package.json
Path to vulnerable library: /node_modules/picomatch/package.json
Dependency Hierarchy:
- copy-webpack-plugin-11.0.0.tgz (Root Library)
- fast-glob-3.3.1.tgz
- micromatch-4.0.5.tgz
- ❌ picomatch-2.3.1.tgz (Vulnerable Library)
- micromatch-4.0.5.tgz
- fast-glob-3.3.1.tgz
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 4 Score Details (6.9)
Base Score Metrics:
- Exploitability Metrics:
- Attack Vector: Network
- Attack Complexity: Low
- Privileges Required: None
- User Interaction: None
- Scope: N/A
- Impact Metrics:
- Confidentiality Impact: N/A
- Integrity Impact: N/A
- Availability Impact: N/A
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 - 4.0.4,https://github.com/micromatch/picomatch.git - 3.0.2
CVE-2024-4067
Vulnerable Library - micromatch-4.0.5.tgz
Glob matching for javascript/node.js. A replacement and faster alternative to minimatch and multimatch.
Library home page: https://registry.npmjs.org/micromatch/-/micromatch-4.0.5.tgz
Path to dependency file: /package.json
Path to vulnerable library: /node_modules/micromatch/package.json
Dependency Hierarchy:
- copy-webpack-plugin-11.0.0.tgz (Root Library)
- fast-glob-3.3.1.tgz
- ❌ micromatch-4.0.5.tgz (Vulnerable Library)
- fast-glob-3.3.1.tgz
Found in base branch: main
Vulnerability Details
The NPM package "micromatch" prior to 4.0.8 is vulnerable to Regular Expression Denial of Service (ReDoS). The vulnerability occurs in "micromatch.braces()" in "index.js" because the pattern ".*" will greedily match anything. By passing a malicious payload, the pattern matching will keep backtracking to the input while it doesn't find the closing bracket. As the input size increases, the consumption time will also increase until it causes the application to hang or slow down. There was a merged fix but further testing shows the issue persists. This issue should be mitigated by using a safe pattern that won't start backtracking the regular expression due to greedy matching. This issue was fixed in version 4.0.8. After conducting a further research, it was concluded that CVE-2024-4067 should not reflect the security risk score in NVD, but will be kept for users' awareness.
Publish Date: 2024-05-13
URL: CVE-2024-4067
CVSS 4 Score Details (6.9)
Base Score Metrics:
- Exploitability Metrics:
- Attack Vector: Network
- Attack Complexity: Low
- Privileges Required: None
- User Interaction: None
- Scope: N/A
- Impact Metrics:
- Confidentiality Impact: N/A
- Integrity Impact: N/A
- Availability Impact: N/A
Suggested Fix
Type: Upgrade version
Release Date: 2024-05-13
Fix Resolution (micromatch): 4.0.8
Direct dependency fix Resolution (copy-webpack-plugin): 12.0.0
⛑️ Automatic Remediation will be attempted for this issue.
CVE-2024-11831
Vulnerable Library - serialize-javascript-6.0.1.tgz
Library home page: https://registry.npmjs.org/serialize-javascript/-/serialize-javascript-6.0.1.tgz
Path to dependency file: /package.json
Path to vulnerable library: /node_modules/serialize-javascript/package.json
Dependency Hierarchy:
- copy-webpack-plugin-11.0.0.tgz (Root Library)
- ❌ serialize-javascript-6.0.1.tgz (Vulnerable Library)
Found in base branch: main
Vulnerability Details
A flaw was found in npm-serialize-javascript. The vulnerability occurs because the serialize-javascript module does not properly sanitize certain inputs, such as regex or other JavaScript object types, allowing an attacker to inject malicious code. This code could be executed when deserialized by a web browser, causing Cross-site scripting (XSS) attacks. This issue is critical in environments where serialized data is sent to web clients, potentially compromising the security of the website or web application using this package.
Publish Date: 2025-02-10
URL: CVE-2024-11831
CVSS 4 Score Details (5.1)
Base Score Metrics:
- Exploitability Metrics:
- Attack Vector: Network
- Attack Complexity: Low
- Privileges Required: Low
- User Interaction: N/A
- Scope: N/A
- Impact Metrics:
- Confidentiality Impact: N/A
- Integrity Impact: N/A
- Availability Impact: N/A
Suggested Fix
Type: Upgrade version
Origin: GHSA-76p7-773f-r4q5
Release Date: 2025-02-10
Fix Resolution: serialize-javascript - 6.0.2
CVE-2025-69873
Vulnerable Library - ajv-8.12.0.tgz
Library home page: https://registry.npmjs.org/ajv/-/ajv-8.12.0.tgz
Path to dependency file: /package.json
Path to vulnerable library: /node_modules/ajv/package.json
Dependency Hierarchy:
- copy-webpack-plugin-11.0.0.tgz (Root Library)
- schema-utils-4.2.0.tgz
- ❌ ajv-8.12.0.tgz (Vulnerable Library)
- schema-utils-4.2.0.tgz
Found in base branch: main
Vulnerability Details
ajv (Another JSON Schema Validator) before 8.18.0 is vulnerable to Regular Expression Denial of Service (ReDoS) when the $data option is enabled. The pattern keyword accepts runtime data via JSON Pointer syntax (
Publish Date: 2026-02-11
URL: CVE-2025-69873
CVSS 4 Score Details (1.2)
Base Score Metrics:
- Exploitability Metrics:
- Attack Vector: Local
- Attack Complexity: High
- Privileges Required: None
- User Interaction: None
- Scope: N/A
- Impact Metrics:
- Confidentiality Impact: N/A
- Integrity Impact: N/A
- Availability Impact: N/A
Suggested Fix
Type: Upgrade version
Origin: GHSA-2g4f-4pwh-qvx6
Release Date: 2026-02-11
Fix Resolution: https://github.com/ajv-validator/ajv.git - v8.18.0,https://github.com/ajv-validator/ajv.git - v6.14.0
⛑️Automatic Remediation will be attempted for this issue.