VulertSecurity VulertSecurity

Vulnerability Database · npm · Package report

url-parse: vulnerability history, versions and safety

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

i
8 vulnerabilities recorded C2 M6
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 url-parse vulnerabilities

Vulert verdict on url-parse 1.5.10 i

Updated on 22 Oct 2026

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

Package health score 64/100
  • Security Some issues to review
  • Maintenance Slowing
  • Popularity Key ecosystem project
  • Community Quiet

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

  • Current release 1.5.10 — unaffected i
  • Vulnerabilities on record 8 over 3 years · 0 in the last year i
  • Latest disclosure 22 Feb 2022 i
  • Highest CVSS 10.0 i
  • With no published fix 0 i
  • Depended on by 110,795 packages i
  • Stars 1,031 i
  • OpenSSF scorecard 3/10 i
  • Last release 56 months ago i
  • Licence MIT i
  • Similar names @aws-sdk/url-parser, @smithy/url-parser, parseurl 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 url-parse, 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
1.5.10 22 Feb 2022 none MIT — Details →
1.5.9 20 Feb 2022 none MIT — Details →
1.5.8 19 Feb 2022 M1 MIT Yes Details →
1.5.7 16 Feb 2022 C1 M1 MIT Yes Details →
1.5.6 13 Feb 2022 C1 M2 MIT Yes Details →
1.5.5 13 Feb 2022 C1 M3 MIT Yes Details →
1.5.4 28 Dec 2021 C1 M3 MIT Yes Details →
1.5.3 25 Jul 2021 C1 M3 MIT Yes Details →
1.5.2 25 Jul 2021 C1 M3 MIT Yes Details →
1.5.1 18 Feb 2021 C1 M4 MIT Yes Details →
1.5.0 17 Feb 2021 C1 M4 MIT Yes Details →
1.4.7 26 Apr 2019 C1 M5 MIT Yes Details →
1.4.6 12 Apr 2019 C1 M5 MIT Yes Details →
1.4.5 11 Apr 2019 C1 M5 MIT Yes Details →
1.4.4 05 Nov 2018 C1 M6 MIT Yes Details →
1.4.3 29 Jul 2018 C1 M6 MIT Yes Details →
1.4.1 05 Jun 2018 C2 M6 MIT Yes Details →
1.4.0 19 Apr 2018 C2 M6 MIT Yes Details →
1.3.0 06 Apr 2018 C2 M6 MIT Yes Details →
1.2.0 02 Nov 2017 C2 M6 MIT Yes Details →
1.1.9 03 May 2017 C2 M6 MIT Yes Details →
1.1.8 18 Feb 2017 C2 M6 MIT Yes Details →
1.1.7 31 Oct 2016 C2 M6 MIT Yes Details →
1.1.6 10 Oct 2016 C2 M6 MIT Yes Details →
1.1.5 10 Oct 2016 C2 M6 MIT Yes Details →
1.1.4 06 Oct 2016 C2 M6 MIT Yes Details →
1.1.3 15 Aug 2016 C2 M6 MIT Yes Details →
1.1.2 15 Aug 2016 C2 M6 MIT Yes Details →
1.1.1 30 Mar 2016 C2 M6 MIT Yes Details →
1.1.0 28 Mar 2016 C2 M6 MIT Yes Details →
1.0.5 30 Oct 2015 C2 M6 MIT Yes Details →
1.0.4 09 Oct 2015 C2 M6 MIT Yes Details →
1.0.3 25 Sep 2015 C2 M6 MIT Yes Details →
1.0.2 03 Jul 2015 C2 M6 MIT Yes Details →
1.0.1 06 May 2015 C2 M6 MIT Yes Details →
1.0.0 18 Jan 2015 C2 M6 MIT Yes Details →
0.2.3 17 Dec 2014 C2 M6 MIT Yes Details →
0.2.2 17 Dec 2014 C2 M6 MIT Yes Details →
0.2.1 16 Dec 2014 C2 M6 MIT Yes Details →
0.2.0 08 Dec 2014 C2 M6 MIT Yes Details →
0.1.5 08 Dec 2014 C2 M6 MIT Yes Details →
0.1.4 27 Nov 2014 C2 M6 MIT Yes Details →
0.1.3 22 Nov 2014 C2 M6 MIT Yes Details →
0.1.2 21 Nov 2014 C2 M6 MIT Yes Details →
0.1.1 21 Nov 2014 C2 M6 MIT Yes Details →
0.1.0 09 Nov 2014 C2 M6 MIT Yes Details →
0.0.4 29 Oct 2014 C2 M6 MIT Yes Details →
0.0.3 17 Oct 2014 C2 M6 MIT Yes Details →
0.0.2 13 Oct 2014 C2 M6 MIT Yes Details →
0.0.1 09 Oct 2014 C2 M6 MIT Yes Details →
0.0.0 08 Oct 2014 C2 M6 MIT Yes Details →

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

02 Disclosure history

How often vulnerabilities are recorded

  • 2018 1
  • 2021 2
  • 2022 5

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

03 Vulnerabilities

Recorded vulnerabilities for url-parse

The 5 most severe of 8 vulnerabilities recorded for this package

Search all 8 in the database →
Vulnerability Severity Fixed version ↓ Disclosed ↓
CVE-2018-3774: Open Redirect in url-parse 10.0 critical 1.4.3 13 Aug 2018
CVE-2022-0686: Authorization Bypass Through User-Controlled Key in url-parse 9.1 critical 1.5.8 21 Feb 2022
CVE-2022-0639: Vulnerability in url-parse package 6.5 medium 1.5.7 18 Feb 2022
CVE-2022-0691: url-parse Incorrectly Parses Hostname/Protocol 6.5 medium 1.5.9 22 Feb 2022
CVE-2021-3664: Open redirect in url-parse 6.1 medium 1.5.2 10 Aug 2021

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

Is url-parse safe to use?

Vulert records 8 vulnerabilities for url-parse in npm: 2 critical, 0 high, 6 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 url-parse's Vulert package health score?

Vulert scores url-parse 64/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 url-parse affected?

No. 1.5.10, 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 url-parse should I use?

1.5.10 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 url-parse have?

8 vulnerabilities are recorded for url-parse in the npm ecosystem: 2 critical, 0 high, 6 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 url-parse vulnerabilities disclosed?

0 vulnerabilities were recorded for url-parse in the last 12 months, and the oldest entry in this database dates to 13 Aug 2018. 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 url-parse 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 url-parse for upcoming vulnerabilities?

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