Is CVE-2026-101913 exploited in the wild?

No. Junglewise Threat Intelligence has no report of CVE-2026-101913 being exploited in the wild.

How severe is CVE-2026-101913?

Medium severity, with a CVSS score of 4, published 28 September 2026.

Which products and versions are affected?

ip-address (npm) <= 10.5.0, SEMVER:introduced=0,fixed=10.5.1; Ip-Address before 10.5.1.

Is there a fix for CVE-2026-101913?

Yes. ip-address (npm): upgrade to 10.5.1 or later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.

How is CVE-2026-101913 attacked?

It is attacked over the network, in a software library.

Am I affected by CVE-2026-101913?

Check whether you run ip-address (npm) or Ip-Address at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

CVE-2026-101913: ip-address Address6 isLinkLocal incomplete subnet check

Q: Which products and versions are affected?

ip-address (npm) <= 10.5.0, SEMVER:introduced=0,fixed=10.5.1; Ip-Address before 10.5.1.

Q: Is there a fix for CVE-2026-101913?

Yes. ip-address (npm): upgrade to 10.5.1 or later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.

Q: How is CVE-2026-101913 attacked?

It is attacked over the network, in a software library.

Q: Am I affected by CVE-2026-101913?

Check whether you run ip-address (npm) or Ip-Address at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

CVE-2026-101913 · Severity: medium · CVSS 4 · Published 2026-09-28

The ip-address JavaScript library was incorrectly recognizing IPv6 link-local addresses. Applications that use the isLinkLocal method for security decisions—such as deciding whether to trust traffic from a particular address—would incorrectly accept addresses outside the intended range. An attacker could exploit this to bypass address-based access controls and reach systems that should only accept on-link traffic.

Technologies: ip-address (npm). Vendors: npm.

Quick answers

Is CVE-2026-101913 exploited in the wild?: No. Junglewise Threat Intelligence has no report of CVE-2026-101913 being exploited in the wild.
How severe is CVE-2026-101913?: Medium severity, with a CVSS score of 4, published 28 September 2026.
Which products and versions are affected?: ip-address (npm) <= 10.5.0, SEMVER:introduced=0,fixed=10.5.1; Ip-Address before 10.5.1.
Is there a fix for CVE-2026-101913?: Yes. ip-address (npm): upgrade to 10.5.1 or later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
How is CVE-2026-101913 attacked?: It is attacked over the network, in a software library.
Am I affected by CVE-2026-101913?: Check whether you run ip-address (npm) or Ip-Address at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

How to fix

ip-address (npm): upgrade to 10.5.1 or later
```
npm install ip-address@10.5.1
```

Technical details

The Address6 isLinkLocal method in src/ipv6.ts checked only the fe80::/64 subnet instead of the complete fe80::/10 range defined by RFC 4291. This caused addresses in fe80::/10 but outside fe80::/64 to fail the isLinkLocal check despite being classified as link-local by getType and getScope, creating an inconsistency that allowed trust-boundary bypasses when address type was used for network access control.

Affected products

ip-address before 10.5.1

Identifiers

CVE-2026-101913
GHSA-rpw4-54j3-4h4q

Timeline

2026-09-28: disclosed
2026-08-29: patched: Version 10.5.1 released

References

This page as Markdown. Free to reuse under CC BY 4.0 with a link back.