VulertSecurity VulertSecurity

Vulnerability Database · npm · Package report

ip-address: vulnerability history, versions and safety

ip-address is a package in the npm ecosystem. Vulert records 10 vulnerabilities for it across 67 releases, from May 2026 to Oct 2026. Each vulnerability names the versions it affects, the fixed version to move to, and a workaround where no fix has been published.

i
10 vulnerabilities recorded H1 M9
i
1 with no fix published

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

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

Most recent disclosure 22 Oct 2026.

See the disclosure history →
i
0 malicious-package vulnerabilities

No published version shipped hostile code.

See all ip-address vulnerabilities

Vulert verdict on ip-address 10.7.4 i

Updated on 22 Oct 2026

Careful: 10.7.4 has 1 known vulnerability, and 1 has no fix yet. Use an earlier safe version, or the workaround listed for each one.

Package health score 60/100
  • Security Unfixed issues
  • Maintenance Sustainable
  • Popularity Key ecosystem project
  • Community Quiet

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 10.7.4 — affected i
  • Vulnerabilities on record 10 over 1 year · 10 in the last year i
  • Latest disclosure 22 Oct 2026 i
  • Highest CVSS 7.7 i
  • With no published fix 1 i
  • Depended on by 184,660 packages i
  • Stars 630 i
  • OpenSSF scorecard 5/10 i
  • Last release this month i
  • Licence MIT i

Version list, release dates, licence and dependants published by the npm registry, 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 ip-address, 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
10.7.4 11 Oct 2026 M1 MIT No Details →
10.7.3 01 Oct 2026 M2 MIT No Details →
10.7.2 15 Sep 2026 M2 MIT No Details →
10.7.1 15 Sep 2026 M2 MIT No Details →
10.7.0 29 Aug 2026 M4 MIT No Details →
10.6.0 29 Aug 2026 M4 MIT No Details →
10.5.1 29 Aug 2026 M4 MIT No Details →
10.5.0 10 Aug 2026 M6 MIT No Details →
10.4.0 31 Jul 2026 M6 MIT No Details →
10.3.1 25 Jul 2026 M6 MIT No Details →
10.3.0 25 Jul 2026 H1 M6 MIT No Details →
10.2.2 25 Jul 2026 H1 M6 MIT No Details →
10.2.1 25 Jul 2026 H1 M7 MIT No Details →
10.2.0 01 May 2026 H1 M8 MIT No Details →
10.1.1 27 Apr 2026 H1 M7 MIT No Details →
10.1.0 08 Nov 2025 H1 M6 MIT No Details →
10.0.1 10 Oct 2024 H1 M6 MIT No Details →
10.0.0 04 Oct 2024 H1 M6 MIT No Details →
9.1.0-0 01 Oct 2024 H1 M6 MIT No Details →
9.0.5 25 Sep 2023 H1 M6 MIT No Details →
9.0.4 25 Sep 2023 H1 M6 MIT No Details →
9.0.3 25 Sep 2023 H1 M6 MIT No Details →
9.0.2 25 Sep 2023 H1 M6 MIT No Details →
9.0.1 25 Sep 2023 H1 M6 MIT No Details →
9.0.0 25 Sep 2023 H1 M6 MIT No Details →
8.1.0 19 Jul 2021 H1 M6 MIT No Details →
8.0.0 20 Jun 2021 H1 M6 MIT No Details →
7.1.0 26 Oct 2020 H1 M6 MIT No Details →
7.0.1 03 Oct 2020 H1 M6 MIT No Details →
7.0.0 02 Oct 2020 H1 M6 MIT No Details →
7.0.0-beta.1 24 Sep 2020 H1 M6 MIT No Details →
7.0.0-beta.0 24 Sep 2020 H1 M6 MIT No Details →
6.4.0 13 Sep 2020 H1 M6 MIT No Details →
6.3.0 01 Apr 2020 H1 M6 MIT No Details →
6.2.0 30 Dec 2019 H1 M6 MIT No Details →
6.1.0 29 Jul 2019 H1 M6 MIT No Details →
6.0.0 29 Jul 2019 H1 M6 MIT No Details →
5.9.4 26 Jul 2019 H1 M6 MIT No Details →
5.9.3 26 Jul 2019 H1 M6 MIT No Details →
5.9.2 05 Jun 2019 H1 M6 MIT No Details →
5.9.1 05 Jun 2019 H1 M6 MIT No Details →
5.9.0 27 Mar 2019 H1 M6 MIT No Details →
5.8.9 06 Dec 2017 H1 M6 MIT No Details →
5.8.8 10 Apr 2017 H1 M6 MIT No Details →
5.8.7 09 Apr 2017 H1 M6 MIT No Details →
5.8.6 13 Dec 2016 H1 M6 MIT No Details →
5.8.5 13 Dec 2016 H1 M6 MIT No Details →
5.8.4 09 Dec 2016 H1 M6 MIT No Details →
5.8.3 08 Dec 2016 H1 M6 MIT No Details →
5.8.2 25 Jul 2016 H1 M6 MIT No Details →
5.8.0 02 Feb 2016 H1 M6 MIT No Details →
5.7.0 22 Jan 2016 H1 M6 MIT No Details →
5.6.0 22 Jan 2016 H1 M6 MIT No Details →
5.5.0 21 Jan 2016 H1 M6 MIT No Details →
5.4.1 21 Jan 2016 H1 M6 MIT No Details →
5.4.0 21 Jan 2016 H1 M6 MIT No Details →
5.3.0 21 Jan 2016 H1 M6 MIT No Details →
5.2.0 20 Jan 2016 H1 M6 MIT No Details →
5.1.1 12 Jan 2016 H1 M6 MIT No Details →
5.1.0 12 Jan 2016 H1 M6 MIT No Details →
5.0.2 29 Oct 2015 H1 M6 MIT No Details →
5.0.1 29 Oct 2015 H1 M6 MIT No Details →
4.2.0 23 Jul 2015 H1 M6 MIT No Details →
4.1.0 23 Jul 2015 H1 M6 MIT No Details →
4.0.0 05 May 2015 H1 M6 MIT No Details →
3.2.0 05 May 2015 H1 M6 MIT No Details →
3.2.1 05 May 2015 H1 M6 MIT No Details →

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

02 Disclosure history

How often vulnerabilities are recorded

  • 2026 10

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

03 Vulnerabilities

Recorded vulnerabilities for ip-address

The 5 most severe of 10 vulnerabilities recorded for this package

Search all 10 in the database →
Vulnerability Severity Fixed version ↓ Disclosed ↓
CVE-2026-69192: ip-address Package Allows SSRF and Trust-Boundary Bypass Due to Leading-Zero Octet Misinterpretation 7.7 high 10.3.1 03 Aug 2026
CVE-2026-54272: ip-address Package Misclassifies IPv4-Mapped/NAT64 IPv6 Addresses Leading to SSRF Bypass 6.9 medium 10.2.1 03 Aug 2026
CVE-2026-69198: ip-address Package Vulnerability Allows SSRF Bypass via CIDR Suffix 6.9 medium 10.2.2 03 Aug 2026
CVE-2026-101910: ip-address Package Vulnerability Allowing SSRF and Trust-Boundary Bypass 6.9 medium 10.5.1 28 Sep 2026
CVE-2026-101913: ip-address Package Vulnerability Allows SSRF and Trust-Boundary Bypass 6.3 medium 10.5.1 28 Sep 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: 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 ip-address

Is ip-address safe to use?

Vulert records 10 vulnerabilities for ip-address in npm: 0 critical, 1 high, 9 medium and 0 low. 1 of them has no published fix yet, so that is the one to avoid or mitigate.

What is ip-address's Vulert package health score?

Vulert scores ip-address 60/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 ip-address affected?

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

Which version of ip-address should I use?

10.7.4 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 ip-address have?

10 vulnerabilities are recorded for ip-address in the npm ecosystem: 0 critical, 1 high, 9 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 ip-address vulnerabilities disclosed?

10 vulnerabilities were recorded for ip-address in the last 12 months, and the oldest entry in this database dates to 05 May 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 ip-address 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 ip-address for upcoming vulnerabilities?

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