depath and cool-path vulnerable to Prototype Pollution via set() Method

Exploitation

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

CVSS 4.0

8.9 · CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:H/VA:H/SC:L/SI:L/SA:N/E:P · score source

EPSS

• CVE-2024-38985: 0.81% estimated exploitation activity in the next 30 days; percentile 56.94 (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.

janryWang products depath v1.0.6 and cool-path v1.1.2 were discovered to contain a prototype pollution via the set() method at setIn (lib/index.js:90). This vulnerability allows attackers to execute arbitrary code or cause a Denial of Service (DoS) via injecting arbitrary properties.

Published by the source

28 Mar 2025, 21:30 UTC

Last modified by the source

31 Mar 2025, 16:24 UTC

Source last checked

26 Oct 2026, 12:36 UTC

1. Revision 3 · amended · 26 Oct 2026

   Amended from ghsa record GHSA-4h4x-4m75-47j4

2. Revision 2 · amended · 24 Oct 2026

   Reviewed OSV alias/range/CVSS4 correction; package source scopes and original publication preserved. No customer finding resolved.

3. Revision 1 · created · 24 Oct 2026

   Published from osv record GHSA-4h4x-4m75-47j4

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

# Patch Next advisory brief: CVE-2024-38985

Advisory: depath and cool-path vulnerable to Prototype Pollution via `set()` Method
IDs: CVE-2024-38985, GHSA-4h4x-4m75-47j4
Record: https://patchnext.com/advisories/cve-2024-38985 (revision 3, source checked 26 Oct 2026, 12:36 UTC)
Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected.
Severity: High (CVSS 8.9)
Exploitation: no confirmed exploitation recorded. Patch Next confirms exploitation only from CISA KEV.
Vendor response: Vendor response not established. A vendor fix does not mean a deployment is fixed.

## Affected components
- npm cool-path: affected <= 1.1.2
- npm depath: affected <= 1.0.6

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

## Supported action
No complete vendor fix is recorded. Follow the primary source's mitigation guidance and check this record again before closing anything.

## Required regression checks
- Run the test suite and a production build.
- Exercise the features that depend on cool-path, depath.
- 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-4h4x-4m75-47j4 (OSV record GHSA-4h4x-4m75-47j4 lists affected ranges: npm depath >=0 =0 <=1.1.2)
- Verified: https://github.com/advisories/GHSA-4h4x-4m75-47j4 (GitHub-reviewed advisory GHSA-4h4x-4m75-47j4 lists affected ranges: npm depath >=0 =0 <=1.1.2)

Commands are suggestions: review each one before running it.