Vulnerability Database · PyPI · Package report

netaddr: vulnerability history, versions and safety

netaddr is a package in the PyPI ecosystem. Vulert holds no vulnerabilities for it yet.

i
0 vulnerabilities recorded

Nothing recorded for this package in the PyPI ecosystem.

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.

Vulert verdict on netaddr 1.3.0 i

Updated on 23 Oct 2026

Good news: 1.3.0, the version you would install today, has no known vulnerabilities.

Package health score 67/100
  • Security Minor issues
  • Maintenance Slowing
  • Popularity Widely used
  • Community Quiet

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

  • Current release 1.3.0 — unaffected i
  • Vulnerabilities on record 0 i
  • Highest CVSS n/a i
  • With no published fix 0 i
  • Depended on by 1,668 packages i
  • Stars 831 i
  • OpenSSF scorecard 3/10 i
  • Last release 28 months ago i
  • Licence non-standard i

Version list, release dates, licence and dependants published by PyPI, refreshed 23 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 netaddr, 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.3.0 28 May 2024 none non-standard — Details →
1.2.1 17 Feb 2024 none non-standard — Details →
1.2.0 17 Feb 2024 none non-standard — Details →
1.1.0 14 Feb 2024 none non-standard — Details →
1.0.0 10 Feb 2024 none non-standard — Details →
0.10.1 02 Jan 2024 none non-standard — Details →
0.10.0 31 Dec 2023 none non-standard — Details →
0.9.0 18 Sep 2023 none non-standard — Details →
0.8.0 03 Jul 2020 none non-standard — Details →
0.7.20 18 Jun 2020 none non-standard — Details →
0.7.19 13 Jan 2017 none non-standard — Details →
0.7.18 03 Sep 2015 none non-standard — Details →
0.7.17 31 Aug 2015 none non-standard — Details →
0.7.16 30 Aug 2015 none non-standard — Details →
0.7.15 29 Jun 2015 none non-standard — Details →
0.7.14 31 Mar 2015 none non-standard — Details →
0.7.13 31 Dec 2014 none non-standard — Details →
0.7.12 06 Jul 2014 none non-standard — Details →
0.7.11 19 Mar 2014 none non-standard — Details →
0.7.10 08 Jan 2014 none non-standard — Details →
0.7.3 15 Sep 2009 none non-standard — Details →
0.7.2 20 Aug 2009 none non-standard — Details →
0.7.1 14 Aug 2009 none non-standard — Details →
0.7.0 12 Aug 2009 none non-standard — Details →
0.6.4 12 Aug 2009 none non-standard — Details →
0.6.3 24 Jun 2009 none non-standard — Details →
0.6.2 13 Apr 2009 none non-standard — Details →
0.6.1 07 Apr 2009 none non-standard — Details →
0.6.0 22 Jan 2009 none non-standard — Details →
0.5.2 30 Sep 2008 none non-standard — Details →
0.5.1 22 Sep 2008 none non-standard — Details →
0.5.0 20 Sep 2008 none non-standard — Details →
0.4.0 07 Aug 2008 none non-standard — Details →
0.3.1 15 Jul 2008 none non-standard — Details →
0.3.1.win32 — none — — Details →
0.4.win32 — none — — Details →
0.5.1.win32 — none — — Details →
0.5.2.win32 — none — — Details →
0.5.win32 — none — — Details →
0.6-py2.5 — none — — Details →
0.6.1-py2.4 — none — — Details →
0.6.1-py2.5 — none — — Details →
0.6.1-py2.6 — none — — Details →
0.6.1.win32 — none — — Details →
0.6.2-py2.4 — none — — Details →
0.6.2-py2.5 — none — — Details →
0.6.2-py2.6 — none — — Details →
0.6.2.win32 — none — — Details →
0.6.3-py2.4 — none — — Details →
0.6.3-py2.5 — none — — Details →
0.6.3-py2.6 — none — — Details →
0.6.3.win32 — none — — Details →
0.6.4-py2.4 — none — — Details →
0.6.4-py2.5 — none — — Details →
0.6.4-py2.6 — none — — Details →
0.6.4.win32 — none — — Details →
0.6.win32 — none — — Details →
0.7-py2.4 — none — — Details →
0.7-py2.5 — none — — Details →
0.7-py2.6 — none — — Details →
0.7.1-py2.4 — none — — Details →
0.7.1-py2.5 — none — — Details →
0.7.1-py2.6 — none — — Details →
0.7.1.win32 — none — — Details →
0.7.10-py2.7 — none — — Details →
0.7.11-py2.7 — none — — Details →
0.7.12-py2.7 — none — — Details →
0.7.13-py2.7 — none — — Details →
0.7.14-py2.7 — none — — Details →
0.7.15-py2.7 — none — — Details →
0.7.16-py2.7 — none — — Details →
0.7.17-py2.7 — none — — Details →
0.7.18-py3.4 — none — — Details →
0.7.2-py2.4 — none — — Details →
0.7.2-py2.5 — none — — Details →
0.7.2-py2.6 — none — — Details →
0.7.2.win32 — none — — Details →
0.7.3-py2.4 — none — — Details →
0.7.3-py2.5 — none — — Details →
0.7.3-py2.6 — none — — Details →
0.7.3.win32 — none — — Details →
0.7.win32 — none — — Details →

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

02 Disclosure history

How often vulnerabilities are recorded

No dated vulnerabilities are recorded for this package yet.

03 Vulnerabilities

Recorded vulnerabilities for netaddr

No vulnerability write-ups match this view

Search all 0 in the database →

No vulnerabilities match this view.

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 netaddr

Is netaddr safe to use?

Vulert has no vulnerabilities on record for netaddr in PyPI at this point. That is a good signal rather than a guarantee: new vulnerabilities are published for packages all the time, so the versions you actually run are still worth monitoring.

What is netaddr's Vulert package health score?

Vulert scores netaddr 67/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 netaddr affected?

No. 1.3.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 netaddr should I use?

1.3.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 netaddr have?

0 vulnerabilities are recorded for netaddr in the PyPI ecosystem: 0 critical, 0 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 netaddr vulnerabilities disclosed?

0 vulnerabilities were recorded for netaddr in the last 12 months. 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 netaddr 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 netaddr for upcoming vulnerabilities?

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