CVE-2018-16472: Prototype Pollution in cached-path-relative

cached-path-relative Updated 02 Oct 2025

Summary

07/11/2018
Yes i
High
7.5

CVE-2018-16472: Prototype Pollution in cached-path-relative. Affects cached-path-relative versions < 1.0.2. Fixed in 1.0.2. How to fix ↓

Also tracked for

The same CVE-2018-16472 is tracked separately for each ecosystem and vendor. Its fix information is the same; the package and affected versions differ.

Free scan

Check if this vulnerability affects your application

Upload a manifest or SBOM and we'll show whether you're affected, plus every other risky package in the same scan.

Check my app free

No signup required · Results in about 60 seconds

Sponsored Devnack Your last release was probably never penetration tested Manual testing by engineers who build software, not an auditor's checklist. Trusted by teams at Swift and Google Talk to Devnack

Background

cached-path-relative is an npm package that provides a utility function for resolving relative paths. It is commonly used in Node.js applications to handle file paths. However, versions of cached-path-relative before 1.0.2 are vulnerable to prototype pollution.

Vulnerability Detail

Prototype pollution is a vulnerability that allows an attacker to modify the prototype of an object, leading to unexpected behavior or the ability to execute arbitrary code. In the case of cached-path-relative, an attacker can manipulate the prototype of the resolved path object, potentially leading to security issues or application crashes.

How To Fix

Latest published version: 1.1.0 as of 22 Oct 2026

npm install cached-path-relative@1.1.0

Upgrading to it may include breaking changes; the version below is the minimum fixed release for this vulnerability.

If you need the minimum change

1.0.2

This is the first release that contains the fix.

npm install cached-path-relative@1.0.2

Tip — Not sure which version your app runs? Vulert can match this fix to it. Scan free →

Conclusion

In conclusion, the cached-path-relative package before version 1.0.2 is vulnerable to prototype pollution. To mitigate this vulnerability, it is important to update to version 1.0.2 or later. For further support on vulnerability remediation, please contact DevNack.com.

See every vulnerability recorded for cached-path-relative →

Share this vulnerability

FAQ

Prototype pollution is a vulnerability that allows an attacker to modify the prototype of an object, leading to unexpected behavior or the ability to execute arbitrary code.

The vulnerability in cached-path-relative allows an attacker to manipulate the prototype of the resolved path object, potentially leading to security issues or application crashes.

The impact of this vulnerability depends on how cached-path-relative is used in the application. It could potentially lead to security issues or unexpected behavior.

To fix this vulnerability, update to version 1.0.2 or later of cached-path-relative.

No workaround is available for this vulnerability. It is recommended to update to the latest version of cached-path-relative.

Related vulnerabilities

Recent vulnerabilities recorded for cached-path-relative.

How To Fix

Latest published version: 1.1.0 as of 22 Oct 2026

npm install cached-path-relative@1.1.0

Upgrading to it may include breaking changes; the version below is the minimum fixed release for this vulnerability.

If you need the minimum change

1.0.2

This is the first release that contains the fix.

npm install cached-path-relative@1.0.2

Tip — Not sure which version your app runs? Vulert can match this fix to it. Scan free →

Subscribe to Vulert on Telegram
Daily digest of new CVEs, critical and high severity, affected packages and fixes — plus a weekly roundup.
Join the channel →
Help improve this record
Report an issue or send feedback