Your RSA-2048 keys break in 2030. Find every one of them before attackers do.
📦
📦 npm
Not in CISA KEV
HIGH severity

CVE-2018-16472 — cached-path-relative

HIGH

CVE-2018-16472 is a high-severity (CVSS 7.5) Uncontrolled Resource Consumption vulnerability in cached-path-relative. A fix is available for cached-path-relative — see the affected versions and patch details below.

Prototype Pollution in cached-path-relative

Also known asGHSA-hc9w-4p87-j549
Published
Updated
Affected
1 pkg
Patched
1 / 1
Exploits
None indexed
Exploitation data as of Oct 11, 2026 · OSV.dev, NVD, FIRST.org (EPSS)

EPSS Exploitation Probability

via FIRST.org ↗
2.1%probability of exploitation in next 30 days
Lower Risk0.00%
Lower risk than most CVEs82th percentile — riskier than 82% of all scored CVEsHighest risk
0.02%0.89%1.77%2.64%0.5%2.1%Apr 26Jul 26Oct 26

Probability of exploitation in the next 30 days, from FIRST.org EPSS.

How urgent is this, really

CVE-2018-16472 by exploitation likelihood (EPSS) against impact (CVSS). Outside the shaded patch-first corner.

Where this sits among everything scored

Of 385,738 CVEs with a current EPSS score, this one falls in the < 10% band (highlighted). Counts from FIRST.org, log-scaled.

Real-World Exposure

1 pkg affected

How broadly this vulnerability is actually deployed: weekly install volume shows current usage, and reverse-dependency count shows how many other packages break if it stays unpatched.

90other npm packages depend on this — each one inherits the vulnerability until it's patched upstream
cached-path-relativenpm
1.0Mdownloads / week

Description

A prototype pollution attack in cached-path-relative versions <=1.0.1 allows an attacker to inject properties on Object.prototype which are then inherited by all the JS objects through the prototype chain causing a DoS attack.

Affected Packages

1 total 1 fixed
EcosystemPackageVulnerable rangeFix
📦npmcached-path-relativeall versions1.0.2npm install cached-path-relative@1.0.2

Affected Products

2 products · 2 configurations
Application
cached-path-relativecached-path-relative_project
≤ 1.0.1
range
OS
debian linuxdebian
1 version
10.0

Detection & mitigation playbook

Open-source dependency

  1. Detect

    Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for cached-path-relative, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.

  2. Fix

    Update cached-path-relative to 1.0.2 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2018-16472 is resolved across your whole dependency graph.

  3. Workarounds

    Cap what an attacker can consume: apply request size, rate and timeout limits in front of the affected component, and run it with memory and CPU limits so exhaustion degrades one worker rather than the whole service.

Frequently Asked Questions

A prototype pollution attack in cached-path-relative versions <=1.0.1 allows an attacker to inject properties on Object.prototype which are then inherited by all the JS objects through the prototype chain causing a DoS attack.
O3 Security · Impact-Aware SCA

Is CVE-2018-16472 in your dependencies?

Find it across npm, including transitive dependencies.

Scan my dependencies How O3 SCA works
CVE-2018-16472: cached-path-relative DoS — Fixed in 1.0.2