Skip to main content

Prototype Pollution CVE-2026-33672

MEDIUM
Improperly Controlled Modification of Object Prototype Attributes (Prototype Pollution) (CWE-1321)
2026-03-25 https://github.com/micromatch/picomatch
5.3
CVSS 3.1 · GitHub Advisory
View

Vulnerability Assessment

Weakness
CWE
OWASP Top 10:2025
A03:2021 - Injection
ASVS 5.0
V3 - Web Frontend Security Prototype pollution prevention
MITRE ATT&CK

2 techniques across 2 tactics: Execution, Initial Access

The technique list with ATT&CK links and the kill-chain view is part of the Basic plan and up.

Impact

The CVSS 3.1 score of 5.3 with vector CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:N indicates a network-accessible vulnerability with low attack complexity and low integrity impact but no confidentiality or availability impact. The attack vector is network-based with no authentication required, making exploitation straightforward for any attacker who can control glob pattern input. However, the real-world impact is constrained by the requirement that applications must (1) accept untrusted glob patterns and (2) rely on glob matching results for security decisions. The vulnerability does not lead to remote code execution, significantly limiting its severity compared to typical RCE vulnerabilities. EPSS data is not provided in the intelligence, but the low CVSS score combined with the requirement for specific application architecture (reliance on glob filtering for security) suggests moderate real-world risk rather than critical risk. Organizations using picomatch in file-filtering, access control, or validation workflows with user-controlled patterns face the highest risk; applications with trusted-input-only glob patterns face minimal risk. The availability of patches in multiple release lines (2.3.2, 3.0.2, 4.0.4) from the vendor reduces remediation friction.

Exploit ScenarioDerived

An attacker controls glob patterns in a file filtering application—for example, a file upload service that uses picomatch to validate filenames against a whitelist pattern. The attacker submits a filename matching a malicious POSIX bracket expression like config[[:constructor:]]backup.json. Due to the method injection vulnerability, this pattern causes the injected method string to be embedded into the regex, altering the matching logic and allowing the malicious filename to bypass validation and pass through the filter. The attacker's file is then stored or processed when it should have been rejected, potentially leading to configuration file overwrite, privilege escalation, or other security violations depending on application logic. Exploitation requires only network access and the ability to control glob pattern input; no user interaction or special privileges are needed.

This Month Plan within 30 days. Why: MEDIUM severity (CVSS 4.0-6.9).
Patch available 0.1% exploitation probability (EPSS)

Get an e-mail when this CVE is exploited, patched or re-scored. Free account.

Alert me

AnalysisAIv1 – Mar 25, 2026

picomatch is vulnerable to a method injection vulnerability (CWE-1321) in its POSIX_REGEX_SOURCE object that allows specially crafted POSIX bracket expressions like [[:constructor:]] to reference inherited Object.prototype methods, causing these methods to be stringified and injected into generated regular expressions. This affects all versions of the npm package picomatch prior to 2.3.2, 3.0.2, and 4.0.4, and can cause incorrect glob matching behavior leading to integrity violations where patterns match unintended filenames; while this does not enable remote code execution, it can compromise security-relevant logic in applications using glob matching for filtering, validation, or access control. The vulnerability is not listed in CISA KEV and has no widely published proof-of-concept, but patches are available from the vendor.

RemediationAI

Upgrade picomatch to version 2.3.2 or later (2.x line), 3.0.2 or later (3.x line), or 4.0.4 or later (4.x line) depending on the currently deployed release line. See the official vendor advisory at https://github.com/micromatch/picomatch/security/advisories/GHSA-3v7f-55p6-f55p for patch details and the fix commit at https://github.com/micromatch/picomatch/commit/4516eb521f13a46b2fe1a1d2c9ef6b20ddc0e903. If immediate patching is not possible, implement input validation by sanitizing or rejecting untrusted glob patterns that contain POSIX character class syntax (e.g., patterns matching /\[\[:[^:]+:\]\]/), or avoid using POSIX bracket expressions for user-controlled input. As a temporary manual patch, modify the POSIX_REGEX_SOURCE object to use a null prototype (__proto__: null) to prevent prototype chain traversal, though this should only serve as a stopgap until the vendor patch is deployed.

Affected Packages

npm picomatch fix: 2.3.2, 3.0.2, 4.0.4

Source: OSV (Open Source Vulnerabilities)

Affects your stack

Affects 1 package in npm

Checking this CVE against your own stacks and servers is part of the Basic plan and up.

Technical ContextAI · show details

picomatch is a popular npm package (CPE: pkg:npm/picomatch) used for glob pattern matching and file path filtering in Node.js applications. The vulnerability stems from CWE-1321 (Improper Validation of Unsafe Equivalence in Regular Expression) combined with prototype pollution concepts. The POSIX_REGEX_SOURCE object, which maps POSIX character class names (like alnum, alpha, digit) to their regex equivalents, inherits from Object.prototype due to standard JavaScript object construction. When processing user-supplied glob patterns containing malicious POSIX bracket expressions such as [[:constructor:]], the library does not sanitize these inputs before interpolating them into regex patterns. JavaScript's prototype chain allows access to inherited properties and methods, and when these method references are stringified and embedded into the regular expression source code, they alter the matching behavior in unintended ways. This is a direct result of insufficient input validation of POSIX character class syntax.

Know when Prototype Pollution gets its next vulnerability

  • Watch products and get an email when something new is published
  • Check this CVE against your own stack and servers
  • Exploit and PoC references, threat intelligence from 22 sources

No credit card · 7-day full trial

Severity by source

GitHub Advisory PRIMARY 5.3 MEDIUM
AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:N
Red Hat 5.3 MEDIUM

Primary rating from GitHub Advisory.

CVSS VectorGitHub Advisory

Attack Vector
Network
Attack Complexity
Low
Privileges Required
None
User Interaction
None
Scope
Unchanged
Confidentiality
None
Integrity
Low
Availability
None

Lifecycle Timeline

2
Patch released
Mar 25, 2026 - 21:17 nvd
Patch available
CVE Published
Mar 25, 2026 - 21:13 nvd
MEDIUM 5.3

DescriptionGitHub Advisory

Impact

picomatch is vulnerable to a method injection vulnerability (CWE-1321) 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.

Patches

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.

Workarounds

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.
  • Manually patching the library by modifying POSIX_REGEX_SOURCE to use a null prototype:
js
  const POSIX_REGEX_SOURCE = {
    __proto__: null,
    alnum: 'a-zA-Z0-9',
    alpha: 'a-zA-Z',
    // ... rest unchanged
  };
### Resources

- fix for similar issue: https://github.com/micromatch/picomatch/pull/144
- picomatch repository https://github.com/micromatch/picomatch

Blast Radius

ecosystem impact
† from your stack dependencies † transitive graph · vuln.today resolves 4-path depth
  • 1 npm packages depend on picomatch (1 direct, 0 indirect)

Ecosystem-wide dependent count for version 4.0.0.

Executive ViewAI

Why It Matters

Organizations using picomatch should be aware of moderate risk from CVE-2026-33672, a prototype pollution vulnerability rated CVSS 5.3. Exploitation could compromise the security of affected deployments. A patch is available and should be applied during regular vulnerability management.

Business Impact: Low
Compensating Controls

Apply vendor patch. If patching is delayed: restrict network access and enable monitoring.

Threat Intelligence Overview

EPSS Score
0.1%
Top 68% exploitable
Data Quality
4 sources
Confidence: Medium
NVD CVE.org EPSS Vulnrichment Vendor GitHub

How this decision was reached

The engine reads each signal below and applies a fixed list of rules from top to bottom. The first rule that matches sets the recommended action – like a statement, every line is shown.

SignalValue
Severity MEDIUM
CISA KEV No
Public POC No
EPSS 0.1%
Patch available Yes
Active threat No
Deciding rule
MEDIUM severity (CVSS 4.0-6.9)
What every action level means
Emergency Immediate action required. Criteria: CRITICAL + in CISA KEV (actively exploited) without patch, OR CRITICAL + EPSS > 30% without patch, OR CRITICAL + active threat signals without patch.
Act Now Prioritize within 24-48h. Criteria: in KEV with patch available, OR CRITICAL + public POC, OR HIGH + EPSS > 10%, OR CRITICAL + active threat, OR any CRITICAL severity.
This Week Schedule remediation this week. Criteria: HIGH severity (CVSS 7.0-8.9). Patch within normal change window.
This Month Plan within 30 days. Criteria: MEDIUM severity (CVSS 4.0-6.9), lower exploitation probability. Include in regular patch cycle.
Monitor Track and reassess. Criteria: LOW severity (CVSS 0.1-3.9), minimal exploitation risk. No immediate action needed.

SSVC AssessmentENISA

SSVC Decision
Scheduled
Exploitation
None
System Exposure· derived
Open
Automatable
Yes
Human Impact
Low
Technical Impact
Partial

Priority Score

26
Low Medium High Critical
KEV: 0
EPSS: 0
CVSS: +26
PoC: 0
Weaponized: 0
Threat intel: 0
Gov advisory: 0

Attack Technique

Remote Code Execution represents the critical moment when an attacker successfully runs arbitrary code on a target system without physical access.

Affected Products (CPE)GitHub Advisory

pkg:npm/picomatch
pkg:npm/picomatch
pkg:npm/picomatch

Related Vulnerabilities in picomatch ReDoS and Injection Vulnerabilities

View all 2
CVE-2026-34621 HIGH POC
8.6 Apr 11

Prototype pollution in Adobe Acrobat Reader versions 24.001.30356, 26.001.21367 and earlier enables arbitrary code execu

CVE-2021-23450 CRITICAL POC
9.8 Dec 17

All versions of package dojo are vulnerable to Prototype Pollution via the setObject function. Rated critical severity (

CVE-2024-56059 CRITICAL
9.8 Dec 18

Prototype pollution in the farinspace Partners WordPress plugin (versions up to and including 0.2.0) enables remote unau

CVE-2021-23383 CRITICAL POC
9.8 May 04

The package handlebars before 4.7.7 are vulnerable to Prototype Pollution when selecting certain compiling options to co

CVE-2020-7788 CRITICAL POC
9.8 Dec 11

This affects the package ini before 1.3.6. Rated critical severity (CVSS 9.8), this vulnerability is remotely exploitabl

CVE-2020-28271 CRITICAL POC
9.8 Nov 12

Prototype pollution vulnerability in 'deephas' versions 1.0.0 through 1.0.5 allows attacker to cause a denial of service

CVE-2023-38894 CRITICAL POC
9.8 Aug 16

A Prototype Pollution issue in Cronvel Tree-kit v.0.7.4 and before allows a remote attacker to execute arbitrary code vi

CVE-2024-24292 CRITICAL POC
9.8 Mar 28

A Prototype Pollution issue in Aliconnect /sdk v.0.0.6 allows an attacker to execute arbitrary code via the aim function

CVE-2023-26121 CRITICAL POC
10.0 Apr 11

All versions of the package safe-eval are vulnerable to Prototype Pollution via the safeEval function, due to improper s

CVE-2021-23449 CRITICAL POC
10.0 Oct 18

This affects the package vm2 before 3.9.4 via a Prototype Pollution attack vector, which can lead to execution of arbitr

CVE-2024-39011 CRITICAL POC
9.8 Jul 30

Prototype Pollution in chargeover redoc v2.0.9-rc.69 allows attackers to execute arbitrary code or cause a Denial of Ser

CVE-2024-38988 CRITICAL POC
9.8 Mar 28

alizeait unflatto <= 1.0.2 was discovered to contain a prototype pollution via the method exports.unflatto at /dist/inde

Vendor StatusVendor

This site uses cookies essential for authentication and security. No tracking or analytics cookies are used. Privacy Policy