CVE-2026-54272: ip-address: Misclassification of IPv4-mapped/NAT64 IPv6 addresses can bypass SSRF and trust-boundary checks
Noroxi assessment
Priority: Monitor (action score 27/100)
- The sources we track (CISA KEV, Exploit-DB, Metasploit, Nuclei, GitHub) show no public exploit code or exploitation in the wild.
- Probability of exploitation in the next 30 days: 0.40% (FIRST EPSS).
- Anyone who can reach it over the internet can trigger it. No account or password is required. No user action is required. No special conditions are required; it is repeatable.
- According to CISA the attack is automatable: targets can be found by mass scanning.
- Fixed version: beaugunderson ip-address 10.2.1.
Low priority for now. Upgrade to beaugunderson ip-address 10.2.1 or later.
Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it
Primary sources: NVD · CVE.org · FIRST EPSS
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.
- GHSA-22jq-vg5j-6vgg
- ALSA-2026:54371
- ALSA-2026:55601
- ALSA-2026:55603
- ALSA-2026:58819
- openSUSE-SU-2026:11611-1
- openSUSE-SU-2026:12134-1
- openSUSE-SU-2026:21545-1
- openSUSE-SU-2026:21546-1
- RHSA-2026:54371
- RHSA-2026:55601
- RHSA-2026:55603
- RHSA-2026:58819
- RHSA-2026:62416
- RLSA-2026:54371
- RLSA-2026:55603
- RLSA-2026:58819
- SUSE-SU-2026:23130-1
- SUSE-SU-2026:23131-1
- SUSE-SU-2026:23154-1
- Published
- Jul 27, 2026
- Updated
- Oct 24, 2026
- EPSS
- 0.4% · 34th percentile
- CWE
- CWE-20
Report tools
Action score
27
Low priority for now.
- CVSS
- 27 / 40 · 6.9 / 10
- CISA KEV
- 0 / 30 · Not listed
- EPSS
- 0 / 30 · 0.4%
CISA SSVC decision
- Exploitation
- proof of concept
- Automatable
- yes
- Technical impact
- partial
Vulnrichment: CISA's decision-tree inputs.
CNA vs NVD score
- NVD
- —
- CNA · GitHub_M
- 6.9
- NVD has not scored this yet; the score shown is the CNA’s.
CVSS:4.0/AV:N/AC:L/AT:P/PR:N/UI:N/VC:L/VI:N/VA:N/SC:H/SI:N/SA:N
The score given by the assigning authority versus NVD’s independent score. A gap means the severity is contested.
Get told when this record changes
- Not in KEV: no record of exploitation in the wild
- No public exploit code on record
- A fix has been released
If any of these changes, we'll tell you in the daily email digest.
Is your version affected? Check itNoroxi analysis
What does it mean in your environment?
The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.
We use this product, ask for helpAffected systems
Is your version affected?
Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.
—
Versions reported by the vendor
Affected version ranges reported by the assigning authority (GitHub_M). Independent of NVD's CPE analysis and usually ahead of it.
beaugunderson ip-address
- >= 10.1.1, < 10.2.1affected
Package-level exposure
OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.
| Ecosystem | Package | Affected range | Fix |
|---|---|---|---|
| AlmaLinux:10 | nodejs24 | before 1:24.18.0-5.el10_2 | 1:24.18.0-5.el10_2 |
| AlmaLinux:10 | nodejs24-devel | before 1:24.18.0-5.el10_2 | 1:24.18.0-5.el10_2 |
| AlmaLinux:10 | nodejs24-docs | before 1:24.18.0-5.el10_2 | 1:24.18.0-5.el10_2 |
| AlmaLinux:10 | nodejs24-full-i18n | before 1:24.18.0-5.el10_2 | 1:24.18.0-5.el10_2 |
| AlmaLinux:10 | nodejs24-libs | before 1:24.18.0-5.el10_2 | 1:24.18.0-5.el10_2 |
| AlmaLinux:10 | nodejs24-npm | before 1:11.16.0-1.24.18.0.5.el10_2 | 1:11.16.0-1.24.18.0.5.el10_2 |
| AlmaLinux:8 | nodejs | before 1:24.18.0-3.module_el8.10.0+4250+09238ed4 | 1:24.18.0-3.module_el8.10.0+4250+09238ed4 |
| AlmaLinux:8 | nodejs-devel | before 1:24.18.0-3.module_el8.10.0+4250+09238ed4 | 1:24.18.0-3.module_el8.10.0+4250+09238ed4 |
| AlmaLinux:8 | nodejs-docs | before 1:24.18.0-3.module_el8.10.0+4250+09238ed4 | 1:24.18.0-3.module_el8.10.0+4250+09238ed4 |
| AlmaLinux:8 | nodejs-full-i18n | before 1:24.18.0-3.module_el8.10.0+4250+09238ed4 | 1:24.18.0-3.module_el8.10.0+4250+09238ed4 |
| AlmaLinux:8 | nodejs-libs | before 1:24.18.0-3.module_el8.10.0+4250+09238ed4 | 1:24.18.0-3.module_el8.10.0+4250+09238ed4 |
| AlmaLinux:8 | nodejs-nodemon | before 3.1.14-2.module_el8.10.0+4250+09238ed4 | 3.1.14-2.module_el8.10.0+4250+09238ed4 |
| AlmaLinux:8 | nodejs-packaging | before 2021.06-6.module_el8.10.0+4086+70facd4a | 2021.06-6.module_el8.10.0+4086+70facd4a |
| AlmaLinux:8 | nodejs-packaging-bundler | before 2021.06-6.module_el8.10.0+4086+70facd4a | 2021.06-6.module_el8.10.0+4086+70facd4a |
| AlmaLinux:8 | npm | before 1:11.16.0-1.24.18.0.3.module_el8.10.0+4250+09238ed4 | 1:11.16.0-1.24.18.0.3.module_el8.10.0+4250+09238ed4 |
| AlmaLinux:8 | v8-13.6-devel | before 3:13.6.233.17-1.24.18.0.3.module_el8.10.0+4250+09238ed4 | 3:13.6.233.17-1.24.18.0.3.module_el8.10.0+4250+09238ed4 |
| AlmaLinux:9 | nodejs | before 1:22.23.1-3.module_el9.8.0+291+0bb98cce | 1:22.23.1-3.module_el9.8.0+291+0bb98cce |
| AlmaLinux:9 | nodejs | before 1:24.18.0-6.module_el9.8.0+292+f4eaf8b2 | 1:24.18.0-6.module_el9.8.0+292+f4eaf8b2 |
| AlmaLinux:9 | nodejs-devel | before 1:22.23.1-3.module_el9.8.0+291+0bb98cce | 1:22.23.1-3.module_el9.8.0+291+0bb98cce |
| AlmaLinux:9 | nodejs-devel | before 1:24.18.0-6.module_el9.8.0+292+f4eaf8b2 | 1:24.18.0-6.module_el9.8.0+292+f4eaf8b2 |
| AlmaLinux:9 | nodejs-docs | before 1:22.23.1-3.module_el9.8.0+291+0bb98cce | 1:22.23.1-3.module_el9.8.0+291+0bb98cce |
| AlmaLinux:9 | nodejs-docs | before 1:24.18.0-6.module_el9.8.0+292+f4eaf8b2 | 1:24.18.0-6.module_el9.8.0+292+f4eaf8b2 |
| AlmaLinux:9 | nodejs-full-i18n | before 1:24.18.0-6.module_el9.8.0+292+f4eaf8b2 | 1:24.18.0-6.module_el9.8.0+292+f4eaf8b2 |
| AlmaLinux:9 | nodejs-full-i18n | before 1:22.23.1-3.module_el9.8.0+291+0bb98cce | 1:22.23.1-3.module_el9.8.0+291+0bb98cce |
+96
Same product
beaugunderson: all recordsOther highest-scoring records for the same primary product.
- CVE-2026-69192ip-address: Address4 decodes leading-zero octets as decimal while resolvers decode them as octal, allowing SSRF and trust-boundary bypass30Monitor
- CVE-2026-101910ip-address: no classifier recognizes the NAT64 local-use range 64:ff9b:1::/48, allowing SSRF and trust-boundary bypass27Monitor
- CVE-2026-69198ip-address: a CIDR suffix on the parsed address suppresses special-use classification and can bypass SSRF and trust-boundary checks27Monitor
Published before and after this one in the same product
- ← EarlierCVE-2026-42338May 12, 2026 · ip-address: XSS in Address6 HTML-emitting methods21Monitor
- Later →CVE-2026-101911Sep 28, 2026 · ip-address: Address6 builds a parse diagnostic proportional to the input with no length bound, allowing a single long string to stall or crash the process25Monitor
- Later →CVE-2026-101912Sep 28, 2026 · ip-address: isInSubnet() and isHostInSubnet() compare addresses of different families as if they shared an address space, allowing an allowlist check to admit…25Monitor
Remediation
Which version to upgrade to
Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.
| Product / package | Fixed version | Source |
|---|---|---|
| beaugunderson ip-address | 10.2.1 · description | Vendor (CNA) |
| almalinux:nodejs | 1:24.18.0-3.module_el8.10.0+4250+09238ed4 · AlmaLinux:8 | Package registry (OSV) |
| almalinux:nodejs-devel | 1:24.18.0-3.module_el8.10.0+4250+09238ed4 · AlmaLinux:8 | Package registry (OSV) |
| almalinux:nodejs-docs | 1:24.18.0-3.module_el8.10.0+4250+09238ed4 · AlmaLinux:8 | Package registry (OSV) |
| almalinux:nodejs-full-i18n | 1:24.18.0-3.module_el8.10.0+4250+09238ed4 · AlmaLinux:8 | Package registry (OSV) |
| almalinux:nodejs-libs | 1:24.18.0-3.module_el8.10.0+4250+09238ed4 · AlmaLinux:8 | Package registry (OSV) |
| almalinux:nodejs-nodemon | 3.1.14-2.module_el8.10.0+4250+09238ed4 · AlmaLinux:8 | Package registry (OSV) |
| almalinux:nodejs-packaging | 2021.06-6.module_el8.10.0+4086+70facd4a · AlmaLinux:8 | Package registry (OSV) |
| almalinux:nodejs-packaging-bundler | 2021.06-6.module_el8.10.0+4086+70facd4a · AlmaLinux:8 | Package registry (OSV) |
| almalinux:nodejs24 | 1:24.18.0-5.el10_2 · AlmaLinux:10 | Package registry (OSV) |
| almalinux:nodejs24-devel | 1:24.18.0-5.el10_2 · AlmaLinux:10 | Package registry (OSV) |
| almalinux:npm | 1:11.16.0-1.24.18.0.3.module_el8.10.0+4250+09238ed4 · AlmaLinux:8 | Package registry (OSV) |
| almalinux:v8-12.4-devel | 3:12.4.254.21-1.22.23.1.3.module_el9.8.0+291+0bb98cce · AlmaLinux:9 | Package registry (OSV) |
| almalinux:v8-13.6-devel | 3:13.6.233.17-1.24.18.0.3.module_el8.10.0+4250+09238ed4 · AlmaLinux:8 | Package registry (OSV) |
| debian:node-ip-address | 10.3.1-1 · Debian:14 | Package registry (OSV) |
| npm:ip-address | 10.2.1 | Package registry (OSV) |
| opensuse:nodejs22 | 22.23.2-160000.1.1 · openSUSE:Leap 16.0 | Package registry (OSV) |
| opensuse:nodejs24 | 24.18.1-160000.1.1 · openSUSE:Leap 16.0 | Package registry (OSV) |
| opensuse:nodejs24 | 24.21.0-1.1 · openSUSE:Tumbleweed | Package registry (OSV) |
| opensuse:nodejs26 | 26.7.0-1.1 · openSUSE:Tumbleweed | Package registry (OSV) |
| red hat:nodejs | 1:24.18.0-3.module+el8.10.0+24639+56878497 · Red Hat:enterprise_linux:8::appstream | Package registry (OSV) |
| red hat:nodejs-debuginfo | 1:24.18.0-3.module+el8.10.0+24639+56878497 · Red Hat:enterprise_linux:8::appstream | Package registry (OSV) |
| red hat:nodejs-debugsource | 1:24.18.0-3.module+el8.10.0+24639+56878497 · Red Hat:enterprise_linux:8::appstream | Package registry (OSV) |
| red hat:nodejs-devel | 1:24.18.0-3.module+el8.10.0+24639+56878497 · Red Hat:enterprise_linux:8::appstream | Package registry (OSV) |
| red hat:nodejs-docs | 1:24.18.0-3.module+el8.10.0+24639+56878497 · Red Hat:enterprise_linux:8::appstream | Package registry (OSV) |
| red hat:nodejs-full-i18n | 1:24.18.0-3.module+el8.10.0+24639+56878497 · Red Hat:enterprise_linux:8::appstream | Package registry (OSV) |
| red hat:nodejs-libs | 1:24.18.0-3.module+el8.10.0+24639+56878497 · Red Hat:enterprise_linux:8::appstream | Package registry (OSV) |
| red hat:nodejs-libs-debuginfo | 1:24.18.0-3.module+el8.10.0+24639+56878497 · Red Hat:enterprise_linux:8::appstream | Package registry (OSV) |
| red hat:nodejs-nodemon | 0:3.1.14-2.module+el8.10.0+24639+56878497 · Red Hat:enterprise_linux:8::appstream | Package registry (OSV) |
| red hat:nodejs-packaging | 0:2021.06-6.module+el8.10.0+24562+090c6525 · Red Hat:enterprise_linux:8::appstream | Package registry (OSV) |
+8
Exploit status
No known public exploit
No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.
Research context
For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.
Timeline
From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.
No dated events beyond publication.
FIRST EPSS daily score; only changes of 0.01 or more are recorded (step chart).
Variant candidates
Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.
- CVE-2026-691927 days apartip-address: Address4 decodes leading-zero octets as decimal while resolvers decode them as octal, allowing SSRF and trust-boundary bypass30Monitor
- CVE-2026-691987 days apartip-address: a CIDR suffix on the parsed address suppresses special-use classification and can bypass SSRF and trust-boundary checks27Monitor
Not on record for this CVE: patch commit or PR link · researcher credit · public bounty program.
Technical details
Attack conditions
- Anyone who can reach it over the internet can trigger it.
- No account or password is required.
- No user action is required.
- No special conditions are required; it is repeatable.
If successful
- Confidentiality
- Integrity
- Availability
- Attack vector
- Network
- Attack complexity
- Low
- Privileges required
- None
- User interaction
- None
- Scope
- X
Weakness class (CWE)
CWE-20 · Improper Input ValidationCVSS vector
CVSS:4.0/AV:N/AC:L/AT:P/PR:N/UI:N/VC:L/VI:N/VA:N/SC:H/SI:N/SA:N/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X
nvd-secondary
Attack context
MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.
Attack patterns (CAPEC)
- Buffer Overflow via Environment VariablesCAPEC-10likelihood: High · High
- Server Side Include (SSI) InjectionCAPEC-101likelihood: High · High
- Cross Zone ScriptingCAPEC-104likelihood: Medium · High
- Command Line Execution through SQL InjectionCAPEC-108likelihood: Low · Very High
- Object Relational Mapping InjectionCAPEC-109likelihood: Low · High
- SQL Injection through SOAP Parameter TamperingCAPEC-110likelihood: High · Very High
- Double EncodingCAPEC-120likelihood: Low · Medium
- Subverting Environment Variable ValuesCAPEC-13likelihood: High · Very High
ATT&CK techniques
- Obfuscated Files or InformationT1027
- Masquerading: Invalid Code SignatureT1036.001
- Steal Web Session CookieT1539
- Subvert Trust Controls: Code SigningT1553.002
- Impair Defenses:Impair Command History LoggingT1562.003
- Hijack Execution Flow:Dynamic Linker HijackingT1574.006
- Hijack Execution Flow:Path Interception by PATH Environment VariableT1574.007
Change log (1)
- Fix✗ → ✓
For records you follow, these changes also arrive as notifications. →
References
Vendor advisories and official records. Exploit/PoC links are deliberately left out.