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.
CVE-2026-54272
This medium-severity CVE scores 6.9 under a secondary CVSS source (NVD's own analysis pending). EPSS exploit probability: 0.4%, top 72% of all CVEs by exploit prediction. GitHub Security Advisory data not yet ingested — confidence will rise once GHSA publishes (typical lag: hours to days for open-source ecosystem CVEs; never for infrastructure-only CVEs).
- Lower severity and no public exploit yet
A fix is available — apply it.
- CVSS v3
- 6.9
- EG Score
- 6.9(medium)
- EG Risk
- 36(Track)EG Risk 36/100SSVC: Track
EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).
How it’s computedSeverity69% × 45%Exploitation0% × 40%Automatability30% × 15%Action: Routine — remediate on your standard cadence. - EPSS PROB
- 0%
- EPSS %ILE
- 28%
- KEV
- Not listed
Published
July 27, 2026
Last Modified
September 9, 2026
Advisory Details (1)
Auto-updated Jul 27, 2026ip-address: misclassification of IPv4-mapped/NAT64 IPv6 addresses can bypass SSRF and trust-boundary checks · Advisory · beaugunderson/ip-address · GitHub
https://github.com/beaugunderson/ip-address/security/advisories/GHSA-22jq-vg5j-6vggVendor Advisories for CVE-2026-54272(20)
These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.
- RHSA-2026:66003Red Hat Product SecurityHigh
Red Hat Security Advisory: Ansible automation portal Red Hat Enterprise Linux Images
- RHSA-2026:63046Red Hat Product SecurityHigh
Red Hat Security Advisory: OpenShift Container Platform 4.21.32 bug fix and security update
- RHSA-2026:63096Red Hat Product SecurityHigh
Red Hat Security Advisory: OpenShift Container Platform 4.22.13 bug fix and security update
- RHSA-2026:63103Red Hat Product SecurityHigh
Red Hat Security Advisory: OpenShift Container Platform 4.20.37 bug fix and security update
- RHSA-2026:62851Red Hat Product SecurityHigh
Red Hat Security Advisory: Red Hat Developer Hub 1.10.4 release.
- RHSA-2026:62416Red Hat Product SecurityHigh
Red Hat Security Advisory: nodejs:22 security update
- RHSA-2026:60390Red Hat Product SecurityHigh
Red Hat Security Advisory: Red Hat Advanced Cluster Management for Kubernetes v2.13.11 security update
- RHSA-2026:60388Red Hat Product SecurityHigh
Red Hat Security Advisory: Red Hat Advanced Cluster Management for Kubernetes v2.14.4 security update
- +12 more
Patch Availability(24)
Patches are aggregated from vendor advisories (Red Hat, Microsoft, Cisco, GitHub) and package ecosystems (OSV, GHSA). Multiple rows for the same upstream release have been deduplicated.
Affected Packages
(2 across 2 ecosystems)
Debian:14(1)
| Package | Vulnerable range | Fixed in | Dependents |
|---|---|---|---|
| node-ip-address | 10.2.0-1, 10.2.0-2, 8.1.0-2, 8.1.0-3 | 10.3.1-1 | — |
npm(1)
| Package | Vulnerable range | Fixed in | Dependents |
|---|---|---|---|
| ip-address | — | 10.2.1 | — |
Weakness Classification(2)
MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.
Additional Vendor Advisories
(4)
Vendors that published advisories for this CVE beyond the curated set above. Broader coverage but minimal per-row detail — click through for the original advisory.
Data Freshness Timeline
(refreshed 15× in last 7d / 70× in last 30d)
Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.
Showing the most recent 100 of 109 total refreshes for this CVE.
- 2026-09-14 15:41 UTCEG score recompute
- 2026-09-14 15:41 UTCVendor advisory
- 2026-09-13 16:47 UTCEPSS rescore
- 2026-09-13 15:22 UTCVendor advisory
- 2026-09-12 16:47 UTCEG score recompute
- 2026-09-12 16:47 UTCVendor advisory
- 2026-09-11 18:47 UTCEG score recompute
- 2026-09-11 18:47 UTCVendor advisory
- 2026-09-11 14:53 UTCEPSS rescore
- 2026-09-10 20:47 UTCEG score recompute
- 2026-09-10 20:47 UTCVendor advisory
- 2026-09-10 09:35 UTCEPSS rescore
- 2026-09-09 21:06 UTCVendor advisory
- 2026-09-09 08:19 UTCEG score recompute
- 2026-09-09 08:19 UTCVendor advisory
- 2026-09-08 22:01 UTCEPSS rescore
- 2026-09-07 21:03 UTCEG score recompute
- 2026-09-07 21:03 UTCVendor advisory
- 2026-09-07 16:01 UTCEPSS rescore
- 2026-09-06 17:24 UTCEG score recompute
- 2026-09-06 17:24 UTCVendor advisory
- 2026-09-06 13:47 UTCEPSS rescore
- 2026-09-05 19:15 UTCEG score recompute
- 2026-09-05 19:15 UTCVendor advisory
- 2026-09-04 12:18 UTCEG score recompute
Show 75 moreShow fewer
- 2026-09-04 12:18 UTCVendor advisory
- 2026-09-04 05:06 UTCEPSS rescore
- 2026-09-02 14:12 UTCEPSS rescore
- 2026-09-01 23:18 UTCEG score recompute
- 2026-09-01 23:18 UTCVendor advisory
- 2026-09-01 13:54 UTCEPSS rescore
- 2026-09-01 04:40 UTCEPSS rescore
- 2026-09-01 01:18 UTCVendor advisory
- 2026-08-30 21:51 UTCEG score recompute
- 2026-08-30 21:51 UTCVendor advisory
- 2026-08-30 19:17 UTCEPSS rescore
- 2026-08-30 01:22 UTCEPSS rescore
- 2026-08-29 23:52 UTCEG score recompute
- 2026-08-29 23:52 UTCVendor advisory
- 2026-08-28 21:41 UTCEPSS rescore
- 2026-08-28 01:55 UTCEG score recompute
- 2026-08-28 01:55 UTCVendor advisory
- 2026-08-27 14:25 UTCEPSS rescore
- 2026-08-27 03:56 UTCEG score recompute
- 2026-08-27 03:56 UTCVendor advisory
- 2026-08-26 14:46 UTCEPSS rescore
- 2026-08-26 05:56 UTCEG score recompute
- 2026-08-26 05:56 UTCVendor advisory
- 2026-08-25 13:49 UTCEPSS rescore
- 2026-08-25 07:56 UTCEG score recompute
- 2026-08-25 07:56 UTCVendor advisory
- 2026-08-24 09:57 UTCEG score recompute
- 2026-08-24 09:57 UTCVendor advisory
- 2026-08-23 11:57 UTCEG score recompute
- 2026-08-23 11:57 UTCVendor advisory
- 2026-08-23 00:19 UTCEPSS rescore
- 2026-08-22 13:58 UTCEG score recompute
- 2026-08-22 13:58 UTCVendor advisory
- 2026-08-21 23:49 UTCEPSS rescore
- 2026-08-21 15:58 UTCEG score recompute
- 2026-08-21 15:58 UTCVendor advisory
- 2026-08-20 22:55 UTCEPSS rescore
- 2026-08-20 17:55 UTCVendor advisory
- 2026-08-19 19:56 UTCEG score recompute
- 2026-08-19 19:56 UTCVendor advisory
- 2026-08-19 17:04 UTCEPSS rescore
- 2026-08-18 18:46 UTCEG score recompute
- 2026-08-18 13:48 UTCEPSS rescore
- 2026-08-17 20:33 UTCEG score recompute
- 2026-08-17 13:47 UTCEPSS rescore
- 2026-08-16 22:34 UTCEG score recompute
- 2026-08-16 14:56 UTCEPSS rescore
- 2026-08-16 02:14 UTCEPSS rescore
- 2026-08-15 02:35 UTCEG score recompute
- 2026-08-15 01:30 UTCEPSS rescore
- 2026-08-14 04:36 UTCEG score recompute
- 2026-08-13 22:00 UTCEPSS rescore
- 2026-08-13 06:36 UTCEG score recompute
- 2026-08-12 13:51 UTCEPSS rescore
- 2026-08-12 08:37 UTCEG score recompute
- 2026-08-11 10:37 UTCEG score recompute
- 2026-08-11 00:00 UTCEPSS rescore
- 2026-08-09 14:38 UTCEG score recompute
- 2026-08-09 13:46 UTCEPSS rescore
- 2026-08-08 16:39 UTCEG score recompute
- 2026-08-08 16:37 UTCEPSS rescore
- 2026-08-07 18:39 UTCEG score recompute
- 2026-08-06 20:39 UTCEG score recompute
- 2026-08-06 13:47 UTCEPSS rescore
- 2026-08-05 22:39 UTCEG score recompute
- 2026-08-05 19:17 UTCEPSS rescore
- 2026-08-05 00:39 UTCEG score recompute
- 2026-08-04 15:10 UTCEPSS rescore
- 2026-08-04 10:39 UTCEPSS rescore
- 2026-08-04 02:40 UTCEG score recompute
- 2026-08-03 10:36 UTCEPSS rescore
- 2026-08-02 06:41 UTCEG score recompute
- 2026-08-02 02:27 UTCEPSS rescore
- 2026-08-01 08:41 UTCEG score recompute
- 2026-08-01 04:16 UTCEPSS rescore
Related CVEs(same vendor + same CWE)
Same vendor
10 shownredhat
- CVE-2001-0825EG 10.0HIGH
- CVE-2001-1009EG 10.0EPSS p93HIGH
- CVE-2001-0554EG 10.0EPSS p98HIGH
- CVE-2001-1162EG 10.0EPSS p96HIGH
- CVE-2001-0414EG 10.0EPSS p100HIGH
- CVE-2001-0191EG 10.0EPSS p92HIGH
- CVE-2001-0301EG 10.0EPSS p91HIGH
- CVE-2001-0197EG 10.0EPSS p96HIGH
- CVE-2001-0233EG 10.0EPSS p96HIGH
- CVE-2001-0010EG 10.0EPSS p98HIGH
Same CWE
10 shownCWE-20
- CVE-2004-1019EG 10.0EPSS p94HIGH
- CVE-2004-0840EG 10.0EPSS p98HIGH
- CVE-2003-1425EG 10.0EPSS p96HIGH
- CVE-2003-1487EG 10.0EPSS p94HIGH
- CVE-2002-1874EG 10.0HIGH
- CVE-2002-2236EG 10.0EPSS p91HIGH
- CVE-2002-2365EG 10.0HIGH
- CVE-2002-1358EG 10.0EPSS p93HIGH
- CVE-2002-1359EG 10.0EPSS p100HIGH
- CVE-2002-1360EG 10.0EPSS p93HIGH
Frequently asked(5)
What is CVE-2026-54272?
When was CVE-2026-54272 disclosed?
Is CVE-2026-54272 actively exploited?
What is the CVSS score of CVE-2026-54272?
How do I remediate CVE-2026-54272?
Dependency Blast Radius
See which npm, PyPI, Go, and Maven packages are affected by CVE-2026-54272
Is Your Infrastructure Affected by CVE-2026-54272?
EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.