Skip to content
Fencer Intel
high 7.5

CVE-2018-16472 json

Prototype Pollution in cached-path-relative

published 8y ago modified 4mo ago also GHSA-hc9w-4p87-j549 , EUVD-2018-0754

cvss
7.5
version 3.1, NVD
cisa kev
Not listed
not in CISA's catalog
epss
2.1%
EPSS 2.1% chance of exploitation in 30 days, percentile 82%
public exploits
0
none known

Summary

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.

Patch / fix

  • npm cached-path-relative 1.0.2
  • node-cached-path-relative Debian 14, Debian 13, Debian 12 1.0.2-1

debian advisories DEBIAN-CVE-2018-16472

Is CVE-2018-16472 in your dependencies? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.

Check with Fencer

Vendor advisories

What the vendors themselves say about their products: affected, fixed or not affected, and what to do.

red hat product security vex CVE-2018-16472 updated cvss 5.3

nodejs-cached-path-relative: prototype pollution due to injected properties on Object.prototype

  • Red Hat Mobile Application Platform 4 nodejs-cached-path-relative
    affected: no fix planned “Out of support scope”

Red Hat CSAF VEX © Red Hat, Inc., from https://security.access.redhat.com/data/csaf/v2/vex/; changed: reduced to product statuses and remediations. CC BY 4.0 · csaf

Exploit prediction

2.14% chance of exploitation in the next 30 days, higher than 82% of all scored CVEs (FIRST EPSS, 2026-11-09).

CVSS scores

assigned by version score vector
NVD 3.1 7.5 CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H
NVD 2.0 5.0 AV:N/AC:L/Au:N/C:N/I:N/A:P
GitHub 3.1 7.5 CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H

Affected packages

ecosystem package affected fixed in
npm cached-path-relative
<1.0.2
1.0.2

Affected products

  • npm cached-path-relative

Classification

Weakness
  • CWE-400 Uncontrolled Resource Consumption
  • CWE-20 Improper Input Validation

References

Sources

Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.