Changeset vulnerable to prototype pollution

Exploitation

No confirmed exploitation recorded. Patch Next marks exploitation only from CISA KEV.

CVSS

9.8 · CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H

EPSS

• CVE-2021-25915: 3.51% estimated exploitation activity in the next 30 days; percentile 89.20 (FIRST EPSS, 2026-11-03). This is a model estimate, not proof of exploitation or customer exposure.

As published by the source; long descriptions are shortened.

Overview Prototype pollution vulnerability in 'changeset' versions 0.0.1 through 0.2.5 allows attackers to cause a denial of service and may lead to remote code execution. Details The npm module 'changeset' can be abused by Prototype Pollution vulnerability since the function 'apply()' does not check for the type of object before assigning value to the property. Due to this flaw an attacker could create a non-existent property or able to manipulate the property which leads to Denial of Service or potentially Remote code execution. PoC Details The 'apply()' function accepts 'changes, target, modify' as argument. Due to the absence of validation on the values passed into the 'changes' argument, an attacker can supply a malicious value by adjusting the value to include the 'proto' property. Since there is no validation before assigning the property to check whether the assigned argument is the Object's own property or not, the property 'polluted' will be directly be assigned to the new…

Published by the source

24 May 2022, 17:44 UTC

Last modified by the source

8 Nov 2023, 04:05 UTC

Source last checked

26 Oct 2026, 12:26 UTC

1. Revision 2 · amended · 26 Oct 2026

   Amended from ghsa record GHSA-2gqw-q9r9-7f79

2. Revision 1 · created · 24 Oct 2026

   Published from osv record GHSA-2gqw-q9r9-7f79

Preview the exact text before you copy it. Commands are read-only suggestions; review them before running anything.

# Patch Next advisory brief: CVE-2021-25915

Advisory: Changeset vulnerable to prototype pollution
IDs: CVE-2021-25915, GHSA-2gqw-q9r9-7f79
Record: https://patchnext.com/advisories/cve-2021-25915 (revision 2, source checked 26 Oct 2026, 12:26 UTC)
Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected.
Severity: Critical (CVSS 9.8)
Exploitation: no confirmed exploitation recorded. Patch Next confirms exploitation only from CISA KEV.
Vendor response: Vendor fix available; fixed versions by package: changeset 0.2.5. A vendor fix does not mean a deployment is fixed.

## Affected components
- npm changeset: affected >= 0.0.1, < 0.2.5; fixed in 0.2.5

## Suggested inspection (read-only)
- `npm ls changeset --all`: lists every installed copy and version, including transitive ones. Run in the project root after `npm ci`.

## Supported action
Upgrade each affected component to a fixed version on its release line. For a transitive dependency, upgrade the parent package or add an override or constraint, then regenerate the lockfile. Redeploy every environment that ran an affected version.

## Required regression checks
- Run the test suite and a production build.
- Exercise the features that depend on changeset.
- Repeat the inspection and confirm that only fixed versions remain installed.

## Rollback considerations
- Keep the previous lockfile and deployment artifact. Rolling back reinstates the vulnerable version, so apply any documented mitigation while you fix forward.

## Unresolved questions
- Which deployments run an affected version?
- Exploitation status can change. Check again before lowering the priority.
- Mark the work resolved only after the fixed version is verified in production.

## Sources
- Verified: https://osv.dev/vulnerability/GHSA-2gqw-q9r9-7f79 (OSV record GHSA-2gqw-q9r9-7f79 lists affected ranges: npm changeset >=0.0.1 <0.2.5 (fixed))
- Verified: https://github.com/advisories/GHSA-2gqw-q9r9-7f79 (GitHub-reviewed advisory GHSA-2gqw-q9r9-7f79 lists affected ranges: npm changeset >=0.0.1 <0.2.5)

Commands are suggestions: review each one before running it.