Is netaddr 2.0 vulnerable?

RubyGems · 5 releases from 2.0.1 to 2.0.6 · latest netaddr is 2.0.6 · checked 18 Nov 2026

No known advisories in the last release

netaddr 2.0.6, the last 2.0 release, has no known advisories. 1 advisory affects earlier 2.0.x releases, so update to 2.0.6.

Update within 2.0:bundle update --conservative netaddr # Gemfile: '>= 2.0.6'

Is your project on an affected netaddr?

Private repo? Upload its lockfile instead, or connect GitHub to check every repo.

Look after several Rails or Ruby apps? Indie watches up to 15 repos, private ones too, for $5 a month. See Indie

Fixed within 2.0.x, affecting earlier releases

  • CriticalCVE-2019-17383GHSA-49pj-69vf-c68914 Oct 2019

    netaddr before 1.5.3 and 2.0.4 has Incorrect Default Permissions

    Affected
    >=2.0.0 <2.0.4 · <1.5.3
    Fixed in
    1.5.3, 2.0.4

Every netaddr 2.0.x release

Affected: 2.0.1 to 2.0.3. 2.0.4 and later are not affected.

VersionKnown advisories
netaddr 2.0.6None
netaddr 2.0.5None
netaddr 2.0.4None
netaddr 2.0.3CVE-2019-17383
netaddr 2.0.1CVE-2019-17383

Which of your client projects are still on netaddr 2.0?

NPMscan reads the lockfiles in every GitHub repo you pick, finds the exact netaddr version each one installs, and checks it against these advisories. Each finding comes with the command that fixes it.

Other netaddr versions

Advisory data from OSV.dev (opens OSV.dev in a new tab), which includes the GitHub Advisory Database. Release list from the RubyGems registry. Refreshed daily.