VulertSecurity VulertSecurity

Vulnerability Database · Go · Package report

github.com/malfunkt/iprange: vulnerability history, versions and safety

github.com/malfunkt/iprange is a package in the Go ecosystem. Vulert records 2 vulnerabilities for it across 5 releases, first recorded in Jul 2023. Each vulnerability names the versions it affects, the fixed version to move to, and a workaround where no fix has been published.

i
2 vulnerabilities recorded M1 U1
i
2 with no fix published

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

See the unfixed vulnerabilities →
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 github.com/malfunkt/iprange vulnerabilities

Vulert verdict on github.com/malfunkt/iprange v0.9.0 i

Updated on 23 Oct 2026

Careful: v0.9.0 has 2 known vulnerabilities, and 2 have no fix yet. Use an earlier safe version, or the workaround listed for each one.

Package health score 52/100
  • Security Some issues to review
  • Maintenance Slowing
  • Popularity Niche
  • Community Inactive

The current release has a vulnerability with no published fix, which caps this score.

What to do: Pin an earlier, unaffected release if you can, and apply the workaround each vulnerability lists until a fix is published. No fix yet: Vulert alerts you the moment one is published. Monitor it with Vulert →

  • Current release v0.9.0 — affected i
  • Vulnerabilities on record 2 over 1 year · 0 in the last year i
  • Latest disclosure 12 Jul 2023 i
  • Highest CVSS n/a i
  • With no published fix 2 i
  • Stars 69 i
  • OpenSSF scorecard 1/10 i
  • Last release 104 months ago i
  • Licence MIT i

Version list, release dates, licence and dependants published by the Go module proxy, 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 github.com/malfunkt/iprange, 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
v0.9.1-0.20241222224025-b572fb9ea929 22 Dec 2024 M1 U1 MIT No Details →
v0.9.1-0.20241222050134-987074d12485 22 Dec 2024 M1 U1 MIT No Details →
v0.0.0-20180210233524-3a31f5ed42d2 10 Feb 2018 M1 U1 MIT No Details →
v0.9.0 10 Feb 2018 M1 U1 MIT No Details →
v0.0.0-20161020235422-b9c6ae1046bc 20 Oct 2016 M1 U1 MIT No Details →

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

02 Disclosure history

How often vulnerabilities are recorded

  • 2023 2

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

03 Vulnerabilities

Recorded vulnerabilities for github.com/malfunkt/iprange

The 2 most severe of 2 vulnerabilities recorded for this package

Search all 2 in the database →
Vulnerability Severity Fixed version ↓ Disclosed ↓
CVE-GO-2023-1857: Panic when parsing ranges with invalid masks in github.com/malfunkt/iprange N/A unrated No fix published 11 Jul 2023
Panic Vulnerability in iprange Package N/A medium No fix published 12 Jul 2023

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 github.com/malfunkt/iprange

Is github.com/malfunkt/iprange safe to use?

Vulert records 2 vulnerabilities for github.com/malfunkt/iprange in Go: 0 critical, 0 high, 1 medium and 0 low, plus 1 not yet rated. 2 of them have no published fix yet, so those are the ones to avoid or mitigate.

What is github.com/malfunkt/iprange's Vulert package health score?

Vulert scores github.com/malfunkt/iprange 52/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). The current release has a vulnerability with no published fix, which caps this score.

Is the latest version of github.com/malfunkt/iprange affected?

Yes. v0.9.0, the version you would install today, has 2 known vulnerabilities, and 2 has no published fix yet. Use an earlier unaffected release, or the workaround each vulnerability lists.

Which version of github.com/malfunkt/iprange should I use?

v0.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 github.com/malfunkt/iprange have?

2 vulnerabilities are recorded for github.com/malfunkt/iprange in the Go ecosystem: 0 critical, 0 high, 1 medium and 0 low, plus 1 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 github.com/malfunkt/iprange vulnerabilities disclosed?

0 vulnerabilities were recorded for github.com/malfunkt/iprange in the last 12 months, and the oldest entry in this database dates to 11 Jul 2023. 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 github.com/malfunkt/iprange 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 github.com/malfunkt/iprange for upcoming vulnerabilities?

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