VulertSecurity VulertSecurity

Vulnerability Database · npm · Package report

parse-url: vulnerability history, versions and safety

parse-url is a package in the npm ecosystem. Vulert records 6 vulnerabilities for it across 40 releases, from Jun 2022 to Sep 2022. Each vulnerability names the versions it affects, the fixed version to move to, and a workaround where no fix has been published.

i
6 vulnerabilities recorded C2 H1 M3
i
0 with no fix published

Every vulnerability has a patched version to move to.

i
0 in the last 12 months

Nothing new recorded in the last year.

See the disclosure history →
i
0 malicious-package vulnerabilities

No published version shipped hostile code.

See all parse-url vulnerabilities

Vulert verdict on parse-url 11.1.0 i

Updated on 22 Oct 2026

Good news: 11.1.0, the version you would install today, has no known vulnerabilities. Older releases do — the table below lists all 6.

Package health score 65/100
  • Security Some issues to review
  • Maintenance Sustainable
  • Popularity Niche
  • Community Quiet

What to do: Stay on 11.1.0 or newer. This can change: a vulnerability disclosed tomorrow can affect 11.1.0 too — Vulert watches the package and alerts you if that happens. Monitor it with Vulert →

  • Current release 11.1.0 — unaffected i
  • Vulnerabilities on record 6 over 1 year · 0 in the last year i
  • Latest disclosure 16 Sep 2022 i
  • Highest CVSS 9.8 i
  • With no published fix 0 i
  • Depended on by 7 packages i
  • Stars 62 i
  • OpenSSF scorecard 3/10 i
  • Last release 7 months ago i
  • Licence MIT i
  • Similar names parseurl, url-parse i

Version list, release dates, licence and dependants published by the npm registry, refreshed 22 Oct 2026. 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 Versions

Which versions are affected

Every version Vulert tracks for parse-url, newest first, with the vulnerabilities recorded against each one. A version showing none has no vulnerability in the Vulert database — open it for the full picture on that release.

i
Version Released Vulert vulnerabilities Licence Fix published Details
11.1.0 04 Mar 2026 none MIT — Details →
11.0.0 04 Mar 2026 none MIT — Details →
10.0.3 17 Aug 2025 none MIT — Details →
10.0.2 06 Aug 2025 none MIT — Details →
10.0.0 29 Apr 2025 none MIT — Details →
9.2.0 03 Apr 2024 none MIT — Details →
9.0.1 02 Jan 2024 none MIT — Details →
9.0.0 02 Jan 2024 none MIT — Details →
8.1.0 30 Aug 2022 none MIT — Details →
8.0.0 03 Aug 2022 C1 M1 MIT Yes Details →
6.0.5 25 Jul 2022 C1 M1 MIT Yes Details →
6.0.4 25 Jul 2022 C1 M1 MIT Yes Details →
6.0.3 25 Jul 2022 C1 M1 MIT Yes Details →
7.0.2 27 Jun 2022 C1 M1 MIT Yes Details →
7.0.1 27 Jun 2022 C1 M1 MIT Yes Details →
7.0.0 27 Jun 2022 C1 M1 MIT Yes Details →
6.0.2 27 Jun 2022 C1 M1 MIT Yes Details →
6.0.1 27 Jun 2022 C1 M1 MIT Yes Details →
5.0.8 06 Jun 2022 C2 H1 M3 MIT Yes Details →
5.0.7 29 Jun 2021 C2 H1 M3 MIT Yes Details →
6.0.0 29 Jun 2021 C2 H1 M3 MIT Yes Details →
5.0.6 25 Jun 2021 C2 H1 M3 MIT Yes Details →
5.0.5 23 Jun 2021 C2 H1 M3 MIT Yes Details →
5.0.4 23 Jun 2021 C2 H1 M3 MIT Yes Details →
5.0.3 02 Jun 2021 C2 H1 M3 MIT Yes Details →
5.0.2 09 Aug 2020 C2 H1 M3 MIT Yes Details →
5.0.1 03 Jan 2019 C2 H1 M3 MIT Yes Details →
5.0.0 28 Oct 2018 C2 H1 M3 MIT Yes Details →
4.0.0 28 Oct 2018 C2 H1 M3 MIT Yes Details →
3.0.2 08 Sep 2017 C2 H1 M3 MIT Yes Details →
3.0.1 21 Aug 2017 C2 H1 M3 MIT Yes Details →
3.0.0 21 Aug 2017 C2 H1 M3 MIT Yes Details →
1.3.11 12 Jun 2017 C2 H1 M3 MIT Yes Details →
1.3.10 12 Jun 2017 C2 H1 M3 MIT Yes Details →
1.3.9 12 Jun 2017 C2 H1 M3 MIT Yes Details →
1.3.8 12 Jun 2017 C2 H1 M3 MIT Yes Details →
1.3.7 23 Mar 2017 C2 H1 M3 MIT Yes Details →
1.3.6 20 Mar 2017 C2 H1 M3 MIT Yes Details →
1.3.5 11 Oct 2016 C2 H1 M3 MIT Yes Details →
1.3.4 11 Oct 2016 C2 H1 M3 MIT Yes Details →
1.3.3 15 Jun 2016 C2 H1 M3 MIT Yes Details →
1.3.2 25 May 2016 C2 H1 M3 MIT Yes Details →
1.3.1 26 Apr 2016 C2 H1 M3 MIT Yes Details →
1.3.0 18 Jan 2016 C2 H1 M3 MIT Yes Details →
1.2.1 14 Jan 2016 C2 H1 M3 MIT Yes Details →
1.2.0 03 Dec 2015 C2 H1 M3 MIT Yes Details →
1.1.0 12 Nov 2015 C2 H1 M3 non-standard Yes Details →
1.0.0 06 Aug 2015 C2 H1 M3 non-standard Yes Details →
0.2.0 05 Aug 2015 C2 H1 M3 non-standard Yes Details →

All 49 versions Vulert tracks for this package. Severity counts are the vulnerabilities recorded against that exact release.

02 Disclosure history

How often vulnerabilities are recorded

  • 2022 6

Counted by the year Vulert recorded each vulnerability — the same date the table below shows as disclosed. 0 of the 6 were recorded in the last 12 months.

03 Vulnerabilities

Recorded vulnerabilities for parse-url

The 5 most severe of 6 vulnerabilities recorded for this package

Search all 6 in the database →
Vulnerability Severity Fixed version ↓ Disclosed ↓
CVE-2022-2216: Server-Side Request Forgery in parse-url 9.8 critical 6.0.1 28 Jun 2022
CVE-2022-2900: Server-Side Request Forgery (SSRF) in parse-url 9.1 critical 8.1.0 15 Sep 2022
CVE-2022-0722: Hostname confusion in parse-url 7.5 high 6.0.1 28 Jun 2022
CVE-2022-2218: Cross-Site Scripting in parse-url 6.1 medium 6.0.1 28 Jun 2022
CVE-2022-2217: Cross-Site Scripting in parse-url 6.1 medium 6.0.1 28 Jun 2022

Vulnerability wrong, a fix missing, or a package we should cover? Report it and we will fix the record. Report Vulnerability Provide Feedback

Updated: 22/Oct/2026 · Vulnerabilities in our DB: 524173

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 parse-url

Is parse-url safe to use?

Vulert records 6 vulnerabilities for parse-url in npm: 2 critical, 1 high, 3 medium and 0 low. Every one of them has a published fix, so the practical answer is to run a supported release and keep it patched.

What is parse-url's Vulert package health score?

Vulert scores parse-url 65/100, which reads as usable, but worth attention. The score weighs the vulnerability record (40), maintenance and release cadence (25), adoption from dependents and stars (20) and community signals such as the OpenSSF scorecard and forks (15).

Is the latest version of parse-url affected?

No. 11.1.0, the version you would install today, has no vulnerabilities on record against it. Earlier releases do — the version table above lists each release with what affects it.

Which version of parse-url should I use?

11.1.0 is the version Vulert recommends for the affected releases. The version table above lists every release with the vulnerabilities recorded against it, so you can confirm the range you actually run.

How many vulnerabilities does parse-url have?

6 vulnerabilities are recorded for parse-url in the npm ecosystem: 2 critical, 1 high, 3 medium and 0 low. The ledger on this page lists the same counts next to the date of the most recent disclosure.

How often are new parse-url vulnerabilities disclosed?

0 vulnerabilities were recorded for parse-url in the last 12 months, and the oldest entry in this database dates to 28 Jun 2022. Recency matters more than a lifetime total: it shows how actively new issues are being disclosed for the package you are considering.

Which versions of parse-url are affected?

Each vulnerability on this page lists the affected version range and the fixed version to move to. Open the vulnerability for the version you actually run — fixes are specific to a release line, not to the package as a whole.

How do I monitor parse-url for upcoming vulnerabilities?

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