CVE-2026-54272 — ip-address
CVE-2026-54272 is a Improper Input Validation vulnerability in ip-address. A fix is available for ip-address — see the affected versions and patch details below.
ip-address: Misclassification of IPv4-mapped/NAT64 IPv6 addresses can bypass SSRF and trust-boundary checks
Exploitation Status
Proof-of-concept exploit code exists
- CISA’s SSVC triage found public proof-of-concept exploit code for this CVE, though no confirmed active exploitation.
- CISA assesses this as automatable — exploitation doesn’t require manual, per-target effort, which raises the odds of mass scanning and opportunistic attacks.
Exploitation and automatability from CISA’s SSVC triage for CVE-2026-54272.
EPSS Exploitation Probability
EPSS (Exploit Prediction Scoring System) is a daily probability model maintained by FIRST.org. It estimates the likelihood a CVE will be exploited in production environments within the next 30 days, derived from real-world threat intelligence signals.
Real-World Exposure
How broadly this vulnerability is actually deployed: weekly install volume shows current usage, and reverse-dependency count shows how many other packages break if it stays unpatched.
ip-addressnpmDescription
ip-address is a library for parsing and manipulating IPv4 and IPv6 addresses in JavaScript. Versions 10.1.1 through 10.2.0 are vulnerable to SSRF through misclassification of IPv4-mapped/NAT64 IPv6 addresses. Address6.getType() classifies an address by matching it against a table of known IPv6 special-use prefixes, returning Global unicast when nothing matches. That table had no entry for the IPv4-mapped range (::ffff:0:0/96), so every mapped address fell through to Global unicast; NAT64 addresses matched their own NAT64 … labels. The boolean checks isLoopback, isUnspecified, and isMulticast compared getType() against a fixed label and so returned false, while isLinkLocal and isULA checked only the native IPv6 ranges. The library already exposed isMapped4() and to4(), but did not apply them inside these checks, so a mapped or NAT64 address was never normalized to its embedded IPv4 address before classification. For IPv4-mapped addresses the host OS routes to the IPv4 stack, so the misclassification is reachable on any dual-stack host. For NAT64, the classification bypass is unconditional but end-to-end reachability additionally requires a NAT64/DNS64 gateway in the deployment network.This issue has been fixed in version 10.2.1.
Affected Packages
| Ecosystem | Package | Vulnerable range | Fix |
|---|---|---|---|
| 📦npm | ip-address | ≥ 10.1.1&&< 10.2.1 | 10.2.1npm install ip-address@10.2.1 |
Detection & mitigation playbook
Open-source dependencyDetect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for ip-address, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update ip-address to 10.2.1 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2026-54272 is resolved across your whole dependency graph.
Workarounds
If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.
How O3 protects you
O3 Security's impact-aware SCA analyses which vulnerable code paths your application actually calls, so a match like CVE-2026-54272 can be triaged on real exposure rather than presence alone.
Tailored to CVE-2026-54272. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.
Fixing This On Your OS
If you run this on a Linux distribution, patch through your package manager against the distro's own security advisory below — it tracks the exact backported fix for your release, which can ship on a different timeline (and sometimes a different severity) than the upstream project.
This is a Moderate flaw where the `ip-address` JavaScript library incorrectly classifies IPv4-mapped or NAT64 IPv6 addresses. This misclassification can lead to Server-Side Request Forgery (SSRF), allowing an attacker to bypass intended network restrictions and access internal resources. Exploitation is possible on…
| Product | Fixed in | Advisory |
|---|---|---|
| Red Hat Enterprise Linux 10 | nodejs24-1:24.18.0-5.el10_2 | RHSA-2026:58819 |
| Red Hat Enterprise Linux 8 | nodejs:24-8100020260807112957.6d880403 | RHSA-2026:54371 |
| Red Hat Enterprise Linux 9 | nodejs:24-9080020260806135511.rhel9 | RHSA-2026:55603 |
| Red Hat Enterprise Linux 9.6 Extended Update Support | nodejs:22-9060020260901085634.rhel9 | RHSA-2026:62416 |
| multicluster engine for Kubernetes 2.17 | multicluster-engine/console-mce-rhel9:1786668856 | RHSA-2026:59593 |
| multicluster engine for Kubernetes 2.6 | multicluster-engine/console-mce-rhel9:1787264250 | RHSA-2026:59579 |
| multicluster engine for Kubernetes 2.8 | multicluster-engine/console-mce-rhel9:1787259048 | RHSA-2026:59558 |
| multicluster engine for Kubernetes 2.9 | multicluster-engine/console-mce-rhel9:1787079359 | RHSA-2026:59559 |
Frequently Asked Questions
Is CVE-2026-54272 in your dependencies?
O3 Security finds CVE-2026-54272 across npm dependencies, including transitive ones, and its impact-aware SCA ranks findings by whether your code actually calls the vulnerable path.