GHSA-rpw4-54j3-4h4q

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

Medium highest severity reported · also known as CVE-2026-101913

4
catalog tools match this advisory
0
ship the vulnerable code in their release binary (Go tools analyzed with govulncheck)
No
in the CISA KEV catalog
0.4%
EPSS for CVE-2026-101913, percentile 33

Catalog tools matching GHSA-rpw4-54j3-4h4q

ToolVersion scannedPackageFixed inReleased binaryDeclared in or found inDispute
infisical
Secret Management
v0.167.4ip-address@10.1.0
npm
10.5.1not analyzedupgrade-impact/package-lock.jsonDispute
prowler
Cloud Security
5.47.0ip-address@10.3.1
npm
10.5.1not analyzedui/pnpm-lock.yamlDispute
slsa-verifier
Supply Chain Compliance
v2.7.1ip-address@9.0.5
npm
10.5.1not analyzedpackage-lock.jsonDispute
snyk-cli
Software Composition Analysis (SCA)
v1.1308.3ip-address@9.0.5
npm
10.5.1not analyzedpackage-lock.jsonDispute

Vulnerabilities are known advisories that Grype matches against the dependencies declared in each project's release source (manifests and lockfiles, including development and build dependencies). A match does not mean the tool is exploitable: the vulnerable code may be unused, test-only, or not shipped in the released binary. KEV: listed in the CISA Known Exploited Vulnerabilities catalog. EPSS: FIRST's estimated probability of exploitation in the next 30 days. Both describe the vulnerability in general, not its exploitability through this tool; a match in a workflow file refers to a GitHub Action, not to shipped code. Released binary is only analyzed for Go tools with a Linux release binary; other tools show not analyzed.

Advisory sources

GitHub advisory GHSA-rpw4-54j3-4h4q · NVD CVE-2026-101913 · OSV GHSA-rpw4-54j3-4h4q

Grype data sources: https://github.com/advisories/GHSA-rpw4-54j3-4h4q