Bug 2507593 (CVE-2026-54272) - CVE-2026-54272 ip-address: ip-address: Server-Side Request Forgery via IPv4-mapped/NAT64 IPv6 address misclassification
Summary: CVE-2026-54272 ip-address: ip-address: Server-Side Request Forgery via IPv4-m...
Keywords:
Status: NEW
Alias: CVE-2026-54272
Product: Security Response
Classification: Other
Component: vulnerability
Version: unspecified
Hardware: All
OS: Linux
medium
medium
Target Milestone: ---
Assignee: Product Security
QA Contact:
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2026-07-27 18:01 UTC by OSIDB Bzimport
Modified: 2026-09-02 07:31 UTC (History)
81 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed:
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Product Errata RHSA-2026:54371 0 None None None 2026-08-12 14:17:27 UTC
Red Hat Product Errata RHSA-2026:55603 0 None None None 2026-08-17 14:33:53 UTC
Red Hat Product Errata RHSA-2026:58819 0 None None None 2026-08-24 06:57:12 UTC
Red Hat Product Errata RHSA-2026:62416 0 None None None 2026-09-02 07:31:41 UTC

Description OSIDB Bzimport 2026-07-27 18:01:23 UTC
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.

Comment 1 errata-xmlrpc 2026-08-12 14:17:22 UTC
This issue has been addressed in the following products:

  Red Hat Enterprise Linux 8

Via RHSA-2026:54371 https://access.redhat.com/errata/RHSA-2026:54371

Comment 2 errata-xmlrpc 2026-08-17 14:33:48 UTC
This issue has been addressed in the following products:

  Red Hat Enterprise Linux 9

Via RHSA-2026:55603 https://access.redhat.com/errata/RHSA-2026:55603

Comment 3 errata-xmlrpc 2026-08-24 06:57:08 UTC
This issue has been addressed in the following products:

  Red Hat Enterprise Linux 10

Via RHSA-2026:58819 https://access.redhat.com/errata/RHSA-2026:58819

Comment 5 errata-xmlrpc 2026-09-02 07:31:36 UTC
This issue has been addressed in the following products:

  Red Hat Enterprise Linux 9.6 Extended Update Support

Via RHSA-2026:62416 https://access.redhat.com/errata/RHSA-2026:62416


Note You need to log in before you can comment on or make changes to this bug.