# CVE-2026-101913: ip-address: Address6.isLinkLocal() recognizes fe80::/64 rather than fe80::/10, allowing SSRF and trust-boundary bypass to on-link hosts

> Attackers can bypass link-local address checks to access on-link hosts, leading to SSRF and trust-boundary violations in applications using the ip-address library.

- **Severity:** Medium 6.3 (`CVSS:4.0/AV:N/AC:L/AT:P/PR:N/UI:N/VC:L/VI:N/VA:N/SC:L/SI:N/SA:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 28 Sep 2026
- **Updated:** 28 Sep 2026
- **Also known as:** CLEANSTART-2026-AO39613, CLEANSTART-2026-DP95262, CLEANSTART-2026-EE28153, CLEANSTART-2026-GF20241, CLEANSTART-2026-JF11250, CLSA-2026-1790676837, CLSA-2026-1790677530, DEBIAN-CVE-2026-101913, ECHO-ea7a-10bd-b753, GHSA-rpw4-54j3-4h4q, MINI-27xg-4wwq-qxwc, MINI-2jfr-77r5-m3mj, MINI-2rrg-q5vg-qr92, MINI-2wrw-w964-2p27, MINI-4gpg-83rq-7phh, MINI-555j-3866-92pm, MINI-653g-cwh4-f7mc, MINI-6vp4-mqp8-chpp, MINI-75p8-92hv-r6m7, MINI-9h4x-9gpw-2vv4, MINI-9wmp-h854-9336, MINI-cx63-8crf-xw4q, MINI-f255-c4jf-7hp6, MINI-f8q9-6469-g6cf, MINI-fjc4-x9j3-gr54, MINI-g45m-6hgw-j6q2, MINI-gx8h-q4wp-4q5v, MINI-hcg4-xw48-2h83, MINI-hfph-w88q-g433, MINI-jg2m-56m5-rv74, MINI-p5q9-7432-q8hq, MINI-pc5v-5972-84gm, MINI-pc9p-jxw2-9h6h, MINI-qc49-c724-p387, MINI-qwx4-6gvq-8p57, MINI-r33x-rf8m-84h8, MINI-vx3g-pr2g-p2qv, MINI-vxh9-xwgx-g5rw, MINI-w3cg-5mj6-7cmw, MINI-wgvx-493g-9q7g, MINI-wvc8-rp59-44rc, MINI-x328-qfwm-m8cp, MINI-x45j-6222-2g9h, MINI-xp88-v7x4-pjqx, UBUNTU-CVE-2026-101913

## What is CVE-2026-101913?

CVE-2026-101913 is a medium-severity server-side request forgery vulnerability in beaugunderson ip-address, published on 28 Sep 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

ip-address is a library for parsing and manipulating IPv4 and IPv6 addresses in JavaScript. Prior to 10.5.1, the Address6 isLinkLocal method in src/ipv6.ts recognizes only fe80::/64 instead of the complete fe80::/10 IPv6 link-local range. An attacker-controlled address elsewhere in fe80::/10 can therefore pass a trust-boundary check that relies on isLinkLocal. The same address is identified as link-local by getType and getScope, exposing the inconsistent classification. A successful bypass can reach an on-link host outside the intended trust boundary. This issue is fixed in version 10.5.1.

Weakness: CWE-918 (Server-Side Request Forgery), CWE-697 (Incorrect Comparison)

## Which versions are affected by CVE-2026-101913?

2 open source packages ship an affected version, including ip-address.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `ip-address` | npm | All versions | 10.5.1 |
| `ip-address` | npm | All versions | 10.5.1 |

## How do I fix CVE-2026-101913?

Upgrade ip-address to 10.5.1 or later.

## Is CVE-2026-101913 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-101913 exists.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-101913 and fix it if it is affected.

What it is: CVE-2026-101913 is a medium-severity server-side request forgery vulnerability in beaugunderson ip-address, published on 28 Sep 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-101913 exists.

Affected packages and fixed versions:
- ip-address (npm): affected all versions; fixed in 10.5.1
- ip-address (npm): affected all versions; fixed in 10.5.1

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-101913/ (Markdown: https://insights.sbomify.com/CVE-2026-101913/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-101913
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-101913
- OSV: https://osv.dev/vulnerability/CVE-2026-101913

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-101913/
Summaries are generated and may contain mistakes; the official description above is the record.