Vulnerability in ip-address (CVE-2026-69198)
Summary
Vulnerability in ip-address (CVE-2026-69198). Risk of unauthorized operations or information disclosure. Exploitable via isInSubnet. Mitigation: upgrade to 10.2.2 or later.
Original description
The description as published by the source.
Summary
Every special-use classification method is built on isInSubnet, which short-circuits to false whenever the address's own subnet mask is shorter than the reference range's mask. That mask comes verbatim from the CIDR suffix on the parsed input, so appending a suffix such as /0 suppresses classification entirely: isLoopback(), isPrivate(), isLinkLocal(), isCGNAT(), isMulticast(), isUnspecified(), isBroadcast(), isULA(), and getType() all report an internal address as unremarkable, while correctForm() and address still return the real internal target.
An application that builds a network trust-boundary decision on these checks (for example a filter intended to block Server-Side Request Forgery, or SSRF) may therefore treat an internal target as external and allow the request. SSRF is an attack in which a user-supplied address coaxes the server into making a request to an internal destination the user could not otherwise reach, such as a loopback service or a cloud metadata endpoint.
Details
isInSubnet in src/common.ts opens with a guard that compares the two prefix lengths:
export function isInSubnet(this, address) {
if (this.subnetMask < address.subnetMask) {
return false; // <-- reached before any bit comparison
}
if (this.mask(address.subnetMask) === address.mask()) {
return true;
}
return false;
}
That guard is correct for the question isInSubnet is named…
Source: GitHub Security Advisories (Global) NVD GitHub Advisory
Auto-generated summary
Assembled by SecPulse from the source data (CVSS, CWE, affected versions) using templates — no AI involved. Check the original description and references below for exact details.
A vulnerability tracked as CVE-2026-69198 has been found in ip-address.
Attackers can target a specific entry point like isInSubnet over the network to misuse the product.
Risk of unauthorized operations or information disclosure.
What to do: upgrade ip-address to 10.2.2 or later.
If unsure, ask your IT team or search "ip-address CVE-2026-69198" on the vendor's site.
CVE-2026-69198 (ip-address) — CWE-20
Attack surface: isInSubnet / false / address / subnetMask
Patched: 10.2.2 — apply immediately
Plan: 1) Audit SBOM/dependencies, 2) Stage→prod upgrade, 3) Add WAF/proxy monitoring on affected endpoints, 4) Hunt IOCs in logs.
Refs: see the GHSA / vendor advisory / patched release linked on this page.
A vulnerability (CWE-20) exists in ip-address. Attackers reach the vulnerable code path via isInSubnet.
Check the vendor advisory for the affected versions of ip-address. Attack surface: isInSubnet / false / address / subnetMask.
Severity: ?. Risk of unauthorized operations or information disclosure.
Update to 10.2.2.
Until the patch is applied: disable the affected feature, apply WAF rules, or restrict access via network ACLs.
Search webserver/proxy logs for unusual request patterns matching this CVE's known IOCs. Run grep -r 'ip-address' . against your dependency files (package-lock.json, requirements.txt, go.sum) to find affected services.
Response actions
Concrete steps and command examples for SOC/SRE teams to execute in order
-
1Identify exposure identify
grep -r 'ip-address' . | grep -v node_modulesリポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で
ip-addressを grep し、稼働しているサービス・バージョンを把握する。 -
2Apply patch patch
Upgrade ip-address to 10.2.2ステージング環境で 10.2.2 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスを含めること。
-
3Post-deployment verification verify
Confirm patched version is live in productionパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番ではアクセスログ・WAF でアラート再発が無いか継続監視。
Affected packages
Fix status by distribution
Fixed packages published by each distribution for this CVE
- Debian DEBIAN-CVE-2026-69198 node-ip-address Fixed in: 10.3.1-1
- Ubuntu UBUNTU-CVE-2026-69198 node-ip-address