CVE-2026-54272

MEDIUMPre-NVD 6.96.9
EchelonGraph scoreMEDIUM confidence

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).

Triggered by: NVD CVSS baseline
Sources: epss, secondary
Trending — 3 sources updated this week
6.9EG
EchelonGraph verdictMonitorLow exploitation likelihood right now — keep watching.
  • Lower severity and no public exploit yet
CISA-KEV: Not listedEPSS PROB: 0%CVSS: 6.9Exploit: None knownExposed: 0

A fix is available — apply it.

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.

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 computed
Severity69% × 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, 2026
🔬 Proof of concept available. Patch available. Sources: github.
github Patch Available🟡 PoC Available

ip-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-6vgg

Patch Availability(24)

Vendor / EcosystemFixed in / PatchReleasedSource
redhatansible-automation-platform/bootc-automation-portal-rhel9:17889435312026-09-09redhat
redhatopenshift4/ose-agent-installer-ui-rhel9:17883149632026-09-08redhat
redhatopenshift4/ose-agent-installer-ui-rhel9:17883352362026-09-08redhat
redhatopenshift4/ose-agent-installer-ui-rhel9:17883515782026-09-08redhat
redhatrhdh/rhdh-hub-rhel9:17882860492026-09-02redhat
redhatnodejs:22-9060020260901085634.rhel92026-09-02redhat
redhatrhacm2/console-rhel9:17873392492026-08-26redhat
redhatrhacm2/console-rhel9:17873351052026-08-26redhat
redhatrhacm2/console-rhel9:17873392482026-08-26redhat
redhatrhacm2/console-rhel9:17876870622026-08-26redhat
redhatmulticluster-engine/console-mce-rhel9:17872642502026-08-25redhat
redhatmulticluster-engine/console-mce-rhel9:17870793592026-08-25redhat
redhatmulticluster-engine/console-mce-rhel9:17872590482026-08-25redhat
redhatopenshift-service-mesh/kiali-rhel9:17870764952026-08-25redhat
redhatopenshift-service-mesh/kiali-rhel9:17871656832026-08-25redhat
redhatopenshift-service-mesh/kiali-rhel9:17870921982026-08-25redhat
redhatmulticluster-engine/console-mce-rhel9:17866688562026-08-25redhat
redhatopenshift-service-mesh/kiali-rhel9:17870922552026-08-25redhat
redhatopenshift-service-mesh/kiali-rhel9:17870771082026-08-25redhat
redhatnodejs24-1:24.18.0-5.el10_22026-08-24redhat
redhatansible-automation-platform/automation-portal:17870471142026-08-18redhat
redhatansible-automation-platform/automation-portal:17870471882026-08-18redhat
redhatnodejs:24-9080020260806135511.rhel92026-08-17redhat
redhatnodejs:24-8100020260807112957.6d8804032026-08-12redhat

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)
PackageVulnerable rangeFixed inDependents
node-ip-address10.2.0-1, 10.2.0-2, 8.1.0-2, 8.1.0-310.3.1-1
npm(1)
PackageVulnerable rangeFixed inDependents
ip-address10.2.1

Weakness Classification(2)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

Additional Vendor Advisories

(4)

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.

  1. 2026-09-14 15:41 UTCEG score recompute
  2. 2026-09-14 15:41 UTCVendor advisory
  3. 2026-09-13 16:47 UTCEPSS rescore
  4. 2026-09-13 15:22 UTCVendor advisory
  5. 2026-09-12 16:47 UTCEG score recompute
  6. 2026-09-12 16:47 UTCVendor advisory
  7. 2026-09-11 18:47 UTCEG score recompute
  8. 2026-09-11 18:47 UTCVendor advisory
  9. 2026-09-11 14:53 UTCEPSS rescore
  10. 2026-09-10 20:47 UTCEG score recompute
  11. 2026-09-10 20:47 UTCVendor advisory
  12. 2026-09-10 09:35 UTCEPSS rescore
  13. 2026-09-09 21:06 UTCVendor advisory
  14. 2026-09-09 08:19 UTCEG score recompute
  15. 2026-09-09 08:19 UTCVendor advisory
  16. 2026-09-08 22:01 UTCEPSS rescore
  17. 2026-09-07 21:03 UTCEG score recompute
  18. 2026-09-07 21:03 UTCVendor advisory
  19. 2026-09-07 16:01 UTCEPSS rescore
  20. 2026-09-06 17:24 UTCEG score recompute
  21. 2026-09-06 17:24 UTCVendor advisory
  22. 2026-09-06 13:47 UTCEPSS rescore
  23. 2026-09-05 19:15 UTCEG score recompute
  24. 2026-09-05 19:15 UTCVendor advisory
  25. 2026-09-04 12:18 UTCEG score recompute
Show 75 more
  1. 2026-09-04 12:18 UTCVendor advisory
  2. 2026-09-04 05:06 UTCEPSS rescore
  3. 2026-09-02 14:12 UTCEPSS rescore
  4. 2026-09-01 23:18 UTCEG score recompute
  5. 2026-09-01 23:18 UTCVendor advisory
  6. 2026-09-01 13:54 UTCEPSS rescore
  7. 2026-09-01 04:40 UTCEPSS rescore
  8. 2026-09-01 01:18 UTCVendor advisory
  9. 2026-08-30 21:51 UTCEG score recompute
  10. 2026-08-30 21:51 UTCVendor advisory
  11. 2026-08-30 19:17 UTCEPSS rescore
  12. 2026-08-30 01:22 UTCEPSS rescore
  13. 2026-08-29 23:52 UTCEG score recompute
  14. 2026-08-29 23:52 UTCVendor advisory
  15. 2026-08-28 21:41 UTCEPSS rescore
  16. 2026-08-28 01:55 UTCEG score recompute
  17. 2026-08-28 01:55 UTCVendor advisory
  18. 2026-08-27 14:25 UTCEPSS rescore
  19. 2026-08-27 03:56 UTCEG score recompute
  20. 2026-08-27 03:56 UTCVendor advisory
  21. 2026-08-26 14:46 UTCEPSS rescore
  22. 2026-08-26 05:56 UTCEG score recompute
  23. 2026-08-26 05:56 UTCVendor advisory
  24. 2026-08-25 13:49 UTCEPSS rescore
  25. 2026-08-25 07:56 UTCEG score recompute
  26. 2026-08-25 07:56 UTCVendor advisory
  27. 2026-08-24 09:57 UTCEG score recompute
  28. 2026-08-24 09:57 UTCVendor advisory
  29. 2026-08-23 11:57 UTCEG score recompute
  30. 2026-08-23 11:57 UTCVendor advisory
  31. 2026-08-23 00:19 UTCEPSS rescore
  32. 2026-08-22 13:58 UTCEG score recompute
  33. 2026-08-22 13:58 UTCVendor advisory
  34. 2026-08-21 23:49 UTCEPSS rescore
  35. 2026-08-21 15:58 UTCEG score recompute
  36. 2026-08-21 15:58 UTCVendor advisory
  37. 2026-08-20 22:55 UTCEPSS rescore
  38. 2026-08-20 17:55 UTCVendor advisory
  39. 2026-08-19 19:56 UTCEG score recompute
  40. 2026-08-19 19:56 UTCVendor advisory
  41. 2026-08-19 17:04 UTCEPSS rescore
  42. 2026-08-18 18:46 UTCEG score recompute
  43. 2026-08-18 13:48 UTCEPSS rescore
  44. 2026-08-17 20:33 UTCEG score recompute
  45. 2026-08-17 13:47 UTCEPSS rescore
  46. 2026-08-16 22:34 UTCEG score recompute
  47. 2026-08-16 14:56 UTCEPSS rescore
  48. 2026-08-16 02:14 UTCEPSS rescore
  49. 2026-08-15 02:35 UTCEG score recompute
  50. 2026-08-15 01:30 UTCEPSS rescore
  51. 2026-08-14 04:36 UTCEG score recompute
  52. 2026-08-13 22:00 UTCEPSS rescore
  53. 2026-08-13 06:36 UTCEG score recompute
  54. 2026-08-12 13:51 UTCEPSS rescore
  55. 2026-08-12 08:37 UTCEG score recompute
  56. 2026-08-11 10:37 UTCEG score recompute
  57. 2026-08-11 00:00 UTCEPSS rescore
  58. 2026-08-09 14:38 UTCEG score recompute
  59. 2026-08-09 13:46 UTCEPSS rescore
  60. 2026-08-08 16:39 UTCEG score recompute
  61. 2026-08-08 16:37 UTCEPSS rescore
  62. 2026-08-07 18:39 UTCEG score recompute
  63. 2026-08-06 20:39 UTCEG score recompute
  64. 2026-08-06 13:47 UTCEPSS rescore
  65. 2026-08-05 22:39 UTCEG score recompute
  66. 2026-08-05 19:17 UTCEPSS rescore
  67. 2026-08-05 00:39 UTCEG score recompute
  68. 2026-08-04 15:10 UTCEPSS rescore
  69. 2026-08-04 10:39 UTCEPSS rescore
  70. 2026-08-04 02:40 UTCEG score recompute
  71. 2026-08-03 10:36 UTCEPSS rescore
  72. 2026-08-02 06:41 UTCEG score recompute
  73. 2026-08-02 02:27 UTCEPSS rescore
  74. 2026-08-01 08:41 UTCEG score recompute
  75. 2026-08-01 04:16 UTCEPSS rescore

Frequently asked(5)

What is CVE-2026-54272?
CVE-2026-54272 is a medium vulnerability published on July 27, 2026. 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…
When was CVE-2026-54272 disclosed?
CVE-2026-54272 was first published in the National Vulnerability Database on July 27, 2026, with the most recent update on September 9, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-54272 actively exploited?
CVE-2026-54272 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0% probability of exploitation in the next 30 days, which ranks it in the top 71.7% of all scored CVEs.
What is the CVSS score of CVE-2026-54272?
CVE-2026-54272 has a CVSS v3 base score of 6.9 (NVD).
How do I remediate CVE-2026-54272?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-54272, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

Dependency Blast Radius

See which npm, PyPI, Go, and Maven packages are affected by CVE-2026-54272

Explore →

Is Your Infrastructure Affected by CVE-2026-54272?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.