VulertSecurity VulertSecurity

Vulnerability Database · Debian · Package report

node-url-parse: vulnerability history, versions and safety

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

i
16 vulnerabilities recorded U16
i
1 with no fix published

No patched version yet — these are the ones to plan around.

See the unfixed vulnerabilities →
i
1 in the last 12 months

Most recent disclosure 16 Dec 2025.

See the disclosure history →
i
0 malicious-package vulnerabilities

No published version shipped hostile code.

See all node-url-parse vulnerabilities

Vulert verdict on node-url-parse i

Updated on 22 Oct 2026

Careful: one of the 16 vulnerabilities Vulert records for this package has no fix yet. Plan around that one, or apply its workaround. The rest have a fixed version to move to.

Long-term outlook: usable, but needs attention 16 vulnerabilities on record across 7 years, 1 in the last year.

What to do: Plan around the 1 vulnerability with no published fix: each lists the affected range and any workaround that reduces exposure. No fix yet: Vulert alerts you the moment one is published. Monitor it with Vulert →

  • Vulnerabilities on record 16 over 7 years · 1 in the last year i
  • Latest disclosure 16 Dec 2025 i
  • Highest CVSS 10.0 i
  • With no published fix 1 i

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 holds for node-url-parse, newest first, with the vulnerabilities that name it. A version with a count of zero has no recorded vulnerabilities; open a version to see the vulnerabilities it is exposed to.

Newest 8 of 8 versions on record. Severity counts are the vulnerabilities recorded against that exact release.

02 Disclosure history

How often vulnerabilities are recorded

  • 2018 2
  • 2020 2
  • 2021 4
  • 2022 7
  • 2025 1

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

03 Vulnerabilities

Recorded vulnerabilities for node-url-parse

The 5 most severe of 16 vulnerabilities recorded for this package

Search all 16 in the database →
Vulnerability Severity Fixed version ↓ Disclosed ↓
Critical SSRF and Open Redirect Vulnerability in node-url-parse Package 10.0 critical 1.2.0-2 12 Aug 2018
Critical Authorization Bypass in node-url-parse: CVE-2022-0691 9.8 critical 1.5.3-1+deb11u1 21 Feb 2022
Authorization Bypass Vulnerability in node-url-parse: CVE-2022-0686 9.1 critical 1.5.3-1+deb11u1 20 Feb 2022
Authorization Bypass Vulnerability in node-url-parse: CVE-2022-0512 5.3 medium 1.5.3-1+deb11u2 14 Feb 2022
URL Redirection Vulnerability in node-url-parse Package 5.3 medium 1.5.3-1 26 Jul 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 node-url-parse

Is node-url-parse safe to use?

Vulert records 16 vulnerabilities for node-url-parse in Debian: 0 critical, 0 high, 0 medium and 0 low, plus 16 not yet rated. 1 of them has no published fix yet, so that is the one to avoid or mitigate.

How many vulnerabilities does node-url-parse have?

16 vulnerabilities are recorded for node-url-parse in the Debian ecosystem: 0 critical, 0 high, 0 medium and 0 low, plus 16 not yet rated. The ledger on this page lists the same counts next to the date of the most recent disclosure.

How often are new node-url-parse vulnerabilities disclosed?

1 vulnerability was recorded for node-url-parse in the last 12 months, and the oldest entry in this database dates to 12 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 node-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 node-url-parse for upcoming vulnerabilities?

Upload the manifest or SBOM for your application at vulert.com/scanner and Vulert keeps checking the node-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.