Prototype pollution in object-path

Exploitation

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

CVSS

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

EPSS

• CVE-2020-15256: 1.55% estimated exploitation activity in the next 30 days; percentile 75.03 (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.

Impact A prototype pollution vulnerability has been found in object-path <= 0.11.4 affecting the set() method. The vulnerability is limited to the includeInheritedProps mode (if version = 0.11.0 is used), which has to be explicitly enabled by creating a new instance of object-path and setting the option includeInheritedProps: true, or by using the default withInheritedProps instance. The default operating mode is not affected by the vulnerability if version = 0.11.0 is used. Any usage of set() in versions < 0.11.0 is vulnerable. Patches Upgrade to version = 0.11.5 Workarounds Don't use the includeInheritedProps: true options or the withInheritedProps instance if using a version = 0.11.0. References Read more about the prototype pollution vulnerability For more information If you have any questions or comments about this advisory: Open an issue in object-path

Published by the source

19 Oct 2020, 20:55 UTC

Last modified by the source

8 Jul 2026, 06:00 UTC

Source last checked

26 Oct 2026, 12:29 UTC

1. Revision 2 · amended · 26 Oct 2026

   Amended from ghsa record GHSA-cwx2-736x-mf6w

2. Revision 1 · created · 24 Oct 2026

   Published from osv record GHSA-cwx2-736x-mf6w

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

# Patch Next advisory brief: CVE-2020-15256

Advisory: Prototype pollution in object-path
IDs: CVE-2020-15256, GHSA-cwx2-736x-mf6w
Record: https://patchnext.com/advisories/cve-2020-15256 (revision 2, source checked 26 Oct 2026, 12:29 UTC)
Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected.
Severity: High (CVSS 7.7)
Exploitation: no confirmed exploitation recorded. Patch Next confirms exploitation only from CISA KEV.
Vendor response: Vendor fix available; fixed versions by package: object-path 0.11.5. A vendor fix does not mean a deployment is fixed.

## Affected components
- npm object-path: affected < 0.11.5; fixed in 0.11.5

## Suggested inspection (read-only)
- `npm ls object-path --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 object-path.
- 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-cwx2-736x-mf6w (OSV record GHSA-cwx2-736x-mf6w lists affected ranges: npm object-path >=0 <0.11.5 (fixed))
- Verified: https://github.com/advisories/GHSA-cwx2-736x-mf6w (GitHub-reviewed advisory GHSA-cwx2-736x-mf6w lists affected ranges: npm object-path >=0 <0.11.5)

Commands are suggestions: review each one before running it.