Vulnerability Database · npm · doc-path · Version

doc-path 2.0.1

2.0.1 is affected by 1 vulnerability.

The vulnerabilities that cover this exact version are listed below with the fixed version to move to. The upgrade Vulert recommends: 4.1.4.

Critical 1 High 0 Medium 0 Low 0 Unrated 0

Released 31 Mar 2019 Status deprecated release Licence MIT Also known from other sources 1 Newer releases 46 Database updated 23/Oct/2026

Release and licence data published by the npm registry. Licence information is not legal advice.

Concerned about your application's security?

Vulert continues monitoring your dependencies and alerts you when new vulnerabilities are disclosed. No installation and no source-code access required.

01 Vulnerabilities affecting this version

doc-path 2.0.1 vulnerabilities

1 vulnerability cover doc-path 2.0.1. Open the full list in the database.

Vulnerability Severity Fixed version Disclosed
CVE-2020-7772: Prototype Pollution in doc-path 9.8 critical 2.1.2 10 May 2021

Looking for another version, or everything Vulert holds for doc-path?

All versions → Full vulnerability list →

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 →

Questions

About doc-path 2.0.1

Is doc-path 2.0.1 vulnerable?

Yes. 1 vulnerability in the Vulert database cover doc-path 2.0.1: 1 critical, 0 high, 0 medium and 0 low. The upgrade Vulert recommends is 4.1.4, and each entry above names the fixed version to move to.

Which version of doc-path should I use instead of 2.0.1?

4.1.4 is the version Vulert recommends for this release line. The version table on the package page lists every release with the vulnerabilities recorded against it.

Is 2.0.1 the latest release of doc-path?

No. 2.0.1 was published 31 Mar 2019, and newer releases exist. Newer is not automatically safer — the version table on the package page shows what each release carries.

How do I monitor doc-path for upcoming vulnerabilities?

Upload the manifest or SBOM for your application at vulert.com/scanner and Vulert keeps checking the doc-path version you actually run against new disclosures, then alerts you when one affects it. There is no installation and no source-code access required.