CVE-2026-90711
CRITICALDescription
proxy-addr is a Node.js module that determines a request's client address behind trusted reverse proxies, and it backs Express req.ip and req.ips. In versions 1.1.0 through 2.0.7, a trust subnet written in IPv4-mapped IPv6 notation with an IPv4-sized prefix, such as ::ffff:10.0.0.0/8 instead of the correct ::ffff:10.0.0.0/104, is accepted without error but trusts every IPv4 address on the internet rather than the block it names. Because the socket peer then becomes trusted at hop 0, any unauthenticated client can supply an arbitrary X-Forwarded-For header and control the address the application reads, which defeats IP-based access control, rate limiting, geolocation, and audit logging. This is a fail-open regression introduced in version 1.1.0. The issue is fixed in proxy-addr 2.0.8, and users should upgrade to 2.0.8 or later. As a workaround, ensure any IPv4-mapped IPv6 trust subnet uses a prefix length of at least 97, or express the range in plain IPv4 notation.
How to fix
This vulnerability affects an unusually large number of packages. The highest-confidence fixes are shown above; the full list is longer. Check the referenced advisories for complete coverage.
TridentStack Control can deploy fixes like this automatically across your Windows, macOS, and Linux fleet. See how it works
Remediation is compiled from vendor and distribution security advisories. Always confirm against the linked source for your exact version and platform.
CVSS v3 Vector
Exploitability
Impact
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:N
Exploit Intelligence
Low risk: more likely to be exploited than 18% of all known CVEs.
References
Related Vulnerabilities
Other CWE-290 vulnerabilities, ordered by exploit likelihood. View all
| CVE | Severity | CVSS | EPSS | Exploited | Fix |
|---|---|---|---|---|---|
| CVE-2024-4358 | Critical | 9.8 | 97% | KEV | - |
| CVE-2022-24112 | Critical | 9.8 | 96% | KEV | Fix |
| CVE-2022-23131 | Critical | 9.1 | 96% | KEV | - |
| CVE-2026-104935 | High | 8.6 | 87% | KEV | Fix |
| CVE-2021-29441 | High | 8.6 | 83% | - | Fix |
| CVE-2019-1234 | High | 7.5 | 75% | - | - |
Common questions
How do I fix CVE-2026-90711?
Published advisories record a fix for 146 affected products. The "How to fix" section on this page lists the fixed version and source advisory for each one, so apply the entry matching what you actually run.
Is CVE-2026-90711 being actively exploited?
Not that we know of. CVE-2026-90711 is not in the CISA Known Exploited Vulnerabilities catalog. Its EPSS score of 0.26% is the estimated probability that it will be exploited in the next 30 days. That is higher than 18% of all scored CVEs.
How severe is CVE-2026-90711?
CVE-2026-90711 has a CVSS v3 base score of 9.1, rated critical. CVSS rates the technical impact if the vulnerability is exploited, not how likely that is, so weigh it alongside the exploit-prediction score when you decide what to patch first.
What does CVE-2026-90711 affect?
Published advisories record a fix for node-proxy-addr (Debian), proxy-addr (npm), aap-metrics-utility (Red Hat / RHEL), aap-metrics-utility (Rocky), and 142 more. Only products with a sourced advisory are listed, so treat this as what we can cite rather than a complete inventory.
Embed a live status badge for CVE-2026-90711
Markdown
[](https://tridentstack.com/cve/CVE-2026-90711)HTML
<a href="https://tridentstack.com/cve/CVE-2026-90711"><img src="https://tridentstack.com/cve/badge/CVE-2026-90711.svg" alt="CVE-2026-90711"></a>Check your Linux endpoints for this class of vulnerability
TridentStack Control continuously scans Linux endpoints for known vulnerabilities and deploys the fixes from the same console. 200 endpoints free forever, no credit card.
This product uses NVD data but is not endorsed or certified by the NVD. EPSS scores courtesy of FIRST.org (https://www.first.org/epss). Source: CISA KEV Catalog. Data as of 2026-09-16.