VulertSecurity VulertSecurity

Vulnerability Database · npm · Package report

urllib: vulnerability history, versions and safety

urllib is a package in the npm ecosystem. Vulert records 1 vulnerability for it across 96 releases, first recorded in Aug 2026. Each vulnerability names the versions it affects, the fixed version to move to, and a workaround where no fix has been published.

i
1 vulnerabilities recorded H1
i
0 with no fix published

Every vulnerability has a patched version to move to.

i
1 in the last 12 months

Most recent disclosure 25 Aug 2026.

See the disclosure history →
i
0 malicious-package vulnerabilities

No published version shipped hostile code.

See all urllib vulnerabilities

Vulert verdict on urllib 4.9.0 i

Updated on 23 Oct 2026

Action needed: 4.9.0 has 1 known vulnerability, but every one of them has a fix. Upgrade to the version listed below and you are clear.

Package health score 76/100
  • Security Minor issues
  • Maintenance Sustainable
  • Popularity Widely used
  • Community Quiet

What to do: Upgrade to the version that resolves each vulnerability below. Fix it, then keep watch: this version is affected today, and the next one may be too — Vulert alerts you when a new vulnerability lands. Monitor it with Vulert →

  • Current release 4.9.0 — affected i
  • Vulnerabilities on record 1 over 1 year · 1 in the last year i
  • Latest disclosure 25 Aug 2026 i
  • Highest CVSS 7.5 i
  • With no published fix 0 i
  • Depended on by 424 packages i
  • Stars 743 i
  • OpenSSF scorecard 4/10 i
  • Last release 10 months ago i
  • Licence MIT 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 urllib, 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
2.44.1 13 Jun 2026 none MIT — Details →
4.9.1 13 Jun 2026 none MIT — Details →
4.9.0 13 Dec 2025 H1 MIT Yes Details →
4.8.2 12 Aug 2025 H1 MIT Yes Details →
4.8.1 06 Aug 2025 H1 MIT Yes Details →
3.27.3 22 Jul 2025 H1 MIT Yes Details →
4.8.0 08 Jul 2025 H1 MIT Yes Details →
4.7.1 07 Jul 2025 H1 MIT Yes Details →
4.7.0 03 Jul 2025 H1 MIT Yes Details →
4.6.12 28 Jun 2025 H1 MIT Yes Details →
3.27.2 13 Feb 2025 H1 MIT Yes Details →
4.6.11 20 Dec 2024 H1 MIT Yes Details →
4.6.10 19 Dec 2024 H1 MIT Yes Details →
4.6.9 17 Dec 2024 H1 MIT Yes Details →
4.6.8 11 Dec 2024 H1 MIT Yes Details →
4.6.7 11 Dec 2024 H1 MIT Yes Details →
4.6.6 07 Dec 2024 H1 MIT Yes Details →
4.6.5 07 Dec 2024 H1 MIT Yes Details →
4.6.4 06 Dec 2024 H1 MIT Yes Details →
4.6.3 05 Dec 2024 H1 MIT Yes Details →
4.6.2 04 Dec 2024 H1 MIT Yes Details →
4.6.1 04 Dec 2024 H1 MIT Yes Details →
4.6.0 04 Dec 2024 H1 MIT Yes Details →
4.5.1 02 Dec 2024 H1 MIT Yes Details →
4.5.0 30 Nov 2024 H1 MIT Yes Details →
4.5.0-beta.3 29 Nov 2024 H1 MIT Yes Details →
4.5.0-beta.2 29 Nov 2024 H1 MIT Yes Details →
4.5.0-beta.1 29 Nov 2024 H1 MIT Yes Details →
4.4.0 08 Oct 2024 H1 MIT Yes Details →
4.3.1 19 Sep 2024 H1 MIT Yes Details →
3.27.1 14 Sep 2024 H1 MIT Yes Details →
4.3.0 14 Sep 2024 H1 MIT Yes Details →
4.2.2 14 Sep 2024 H1 MIT Yes Details →
4.2.1 11 Sep 2024 H1 MIT Yes Details →
2.44.0 08 Jul 2024 none MIT — Details →
3.27.0 08 Jul 2024 H1 MIT Yes Details →
4.2.0 08 Jul 2024 H1 MIT Yes Details →
4.1.0 27 Jun 2024 H1 MIT Yes Details →
3.26.0 26 Jun 2024 H1 MIT Yes Details →
4.0.0 23 Jun 2024 H1 MIT Yes Details →
2.43.0 18 Jun 2024 none MIT — Details →
2.42.0 13 Jun 2024 none MIT — Details →
3.25.1 01 Jun 2024 H1 MIT Yes Details →
3.25.0 07 May 2024 H1 MIT Yes Details →
3.24.0 22 Apr 2024 H1 MIT Yes Details →
3.23.0 09 Mar 2024 H1 MIT Yes Details →
3.22.5 29 Feb 2024 H1 MIT Yes Details →
3.22.4 22 Feb 2024 H1 MIT Yes Details →
3.22.3 20 Feb 2024 H1 MIT Yes Details →
3.22.2 15 Jan 2024 H1 MIT Yes Details →
3.22.1 22 Dec 2023 H1 MIT Yes Details →
3.22.0 21 Dec 2023 H1 MIT Yes Details →
3.21.0 04 Dec 2023 H1 MIT Yes Details →
3.20.0 04 Dec 2023 H1 MIT Yes Details →
3.19.3 21 Sep 2023 H1 MIT Yes Details →
3.19.2 19 Sep 2023 H1 MIT Yes Details →
3.19.1 17 Sep 2023 H1 MIT Yes Details →
3.19.0 14 Sep 2023 H1 MIT Yes Details →
3.18.1-beta.0 14 Sep 2023 H1 MIT Yes Details →
3.18.1 11 Sep 2023 H1 MIT Yes Details →
3.18.0 18 Aug 2023 H1 MIT Yes Details →
3.17.2 17 Aug 2023 H1 MIT Yes Details →
2.41.0 28 Jul 2023 none MIT — Details →
3.17.1 15 Jun 2023 H1 MIT Yes Details →
3.17.0 15 Jun 2023 H1 MIT Yes Details →
3.16.1 24 May 2023 H1 MIT Yes Details →
3.16.0 21 May 2023 H1 MIT Yes Details →
3.15.0 21 May 2023 H1 MIT Yes Details →
3.14.1 17 May 2023 H1 MIT Yes Details →
3.14.0 07 May 2023 H1 MIT Yes Details →
3.13.2 24 Apr 2023 H1 MIT Yes Details →
3.13.1 25 Mar 2023 H1 MIT Yes Details →
3.13.0 25 Mar 2023 H1 MIT Yes Details →
3.12.0 21 Mar 2023 H1 MIT Yes Details →
3.11.0 18 Feb 2023 H1 MIT Yes Details →
3.10.2 13 Feb 2023 H1 MIT Yes Details →
3.10.1 14 Jan 2023 H1 MIT Yes Details →
3.10.0 18 Dec 2022 H1 MIT Yes Details →
3.9.0 17 Dec 2022 H1 MIT Yes Details →
3.8.1 16 Dec 2022 H1 MIT Yes Details →
3.8.0 14 Dec 2022 H1 MIT Yes Details →
3.7.0 05 Dec 2022 H1 MIT Yes Details →
3.6.0 05 Dec 2022 H1 MIT Yes Details →
3.5.2 25 Nov 2022 H1 MIT Yes Details →
3.5.1 18 Nov 2022 H1 MIT Yes Details →
3.5.0 31 Oct 2022 H1 MIT Yes Details →
3.4.0 29 Oct 2022 H1 MIT Yes Details →
2.40.0 22 Oct 2022 none MIT — Details →
3.3.1 15 Oct 2022 H1 MIT Yes Details →
2.39.1 09 Oct 2022 none MIT — Details →
2.39.0 08 Oct 2022 none MIT — Details →
3.3.0 05 Oct 2022 H1 MIT Yes Details →
3.2.3 29 Sep 2022 H1 MIT Yes Details →
3.2.2 28 Sep 2022 H1 MIT Yes Details →
3.2.1 27 Sep 2022 H1 MIT Yes Details →
3.2.0 26 Sep 2022 H1 MIT Yes Details →
3.1.3 09 Sep 2022 H1 MIT Yes Details →
3.1.2 24 Aug 2022 H1 MIT Yes Details →
3.1.1 23 Aug 2022 H1 MIT Yes Details →
3.1.0 01 Aug 2022 H1 MIT Yes Details →
3.0.4 18 Jul 2022 H1 — Yes Details →
3.0.3 17 Jul 2022 H1 — Yes Details →
3.0.2 17 Jul 2022 H1 — Yes Details →
3.0.1 17 Jul 2022 H1 — Yes Details →
3.0.0 16 Jul 2022 H1 — Yes Details →
2.38.1 05 Jul 2022 none — — Details →
3.0.0-alpha.1 25 Jun 2022 none — — Details →
3.0.0-alpha.0 19 Jun 2022 none — — Details →
2.38.0 24 Nov 2021 none — — Details →
2.37.4 07 Sep 2021 none — — Details →
2.37.3 05 Jul 2021 none — — Details →
2.37.2 07 Jun 2021 none — — Details →
2.37.1 15 Apr 2021 none — — Details →
2.37.0 02 Apr 2021 none — — Details →
2.36.1 09 Jun 2020 none — — Details →
2.36.0 08 Jun 2020 none — — Details →
2.35.0 15 May 2020 none — — Details →
2.34.2 07 Jan 2020 none — — Details →
2.34.1 02 Sep 2019 none — — Details →
2.34.0 07 May 2019 none — — Details →

The newest 120 of 250 versions Vulert tracks. Severity counts are the vulnerabilities recorded against that exact release.

02 Disclosure history

How often vulnerabilities are recorded

  • 2026 1

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

03 Vulnerabilities

Recorded vulnerabilities for urllib

The 1 most severe of 1 vulnerabilities recorded for this package

Search all 1 in the database →
Vulnerability Severity Fixed version ↓ Disclosed ↓
CVE-2026-55553: urllib Cross-Origin Redirects Lead to Credential Leakage 7.5 high 4.9.1 25 Aug 2026

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

Updated: 23/Oct/2026 · Vulnerabilities in our DB: 524315

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 urllib

Is urllib safe to use?

Vulert records 1 vulnerabilities for urllib in npm: 0 critical, 1 high, 0 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 urllib's Vulert package health score?

Vulert scores urllib 76/100, which reads as in good shape. 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 urllib affected?

Yes. 4.9.0, the version you would install today, has 1 known vulnerability, and every one of them has a published fix. Upgrade to the version listed for each.

Which version of urllib should I use?

4.9.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 urllib have?

1 vulnerability is recorded for urllib in the npm ecosystem: 0 critical, 1 high, 0 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 urllib vulnerabilities disclosed?

1 vulnerability was recorded for urllib in the last 12 months, and the oldest entry in this database dates to 25 Aug 2026. 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 urllib 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 urllib for upcoming vulnerabilities?

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