Live Exposure Defense: From CVE to Confirmed Exposure in 12 Hours – See more

New CVE Detected

CVE-2026-90711 – IP Spoofing / Access Control Bypass – proxy-addr npm package 1.1.0 to 2.0.7

Be the first to know when new zero-days emerge:

Summary

CVE-2026-90711 is a critical IP spoofing vulnerability (CWE-290: Authentication Bypass by Spoofing) affecting the widely-used proxy-addr npm package, a dependency relied on by Express and many other Node.js frameworks to determine the true client IP address behind a proxy. Applications that configure a trust subnet using IPv4-mapped IPv6 notation with an incorrect prefix length silently end up trusting every IPv4 address on the internet, allowing unauthenticated remote attackers to spoof their source IP via the X-Forwarded-For header. The flaw carries a CVSS v3.1 score of 9.1 (Critical).

Technical details

  • Root cause: When a trust subnet is specified using IPv4-mapped IPv6 notation (e.g. ::ffff:10.0.0.0/8) instead of the correct, fully-expanded prefix (e.g. ::ffff:10.0.0.0/104), proxy-addr compiles the subnet mask incorrectly. The resulting mask ends up with all-zero leading bits, causing it to match every IPv4 address rather than the intended, narrower block.
  • Trigger conditions: The application must configure proxy-addr (directly or via a framework such as Express’s trust proxy setting) with an IPv4-mapped IPv6 trust subnet whose prefix length is shorter than 96+the intended IPv4 prefix (i.e., not using the full /104-style notation). No error or warning is raised when the misconfiguration occurs.
  • Attack vector: Network — an unauthenticated attacker sends a crafted X-Forwarded-For header in an HTTP request; because the trust check erroneously matches, the attacker-supplied IP is treated as trusted.
  • Impact: Attackers can bypass IP-based access controls, rate limiting, geolocation restrictions, and audit/logging mechanisms that rely on the client IP resolved by proxy-addr. This can lead to unauthorized access to IP-restricted resources and falsified audit trails (High confidentiality and integrity impact; no direct availability impact).

Affected software

  • proxy-addr (npm package) versions >= 1.1.0 and < 2.0.8
  • Any application or framework (e.g., Express-based services) that depends on a vulnerable proxy-addr version and configures IP trust subnets using IPv4-mapped IPv6 notation with a short/incorrect prefix length

Severity

  • CVSS v3.1 Base Score: 9.1 (Critical)
  • Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:N

Mitigation and recommended actions

  • Immediate: Upgrade proxy-addr to version 2.0.8 or later, which correctly handles IPv4-mapped IPv6 prefix lengths.
  • If immediate patching is not possible:
    • Avoid IPv4-mapped IPv6 shorthand for trust subnets; use plain IPv4 notation instead (e.g., 10.0.0.0/8).
    • If IPv6 notation must be used, always specify the full, correctly-expanded prefix (e.g., ::ffff:10.0.0.0/104) rather than a shortened prefix.
    • Audit existing trust proxy / trusted-subnet configurations in Express and other frameworks that depend on proxy-addr to confirm no IPv4-mapped IPv6 subnets with short prefixes are in use.

References

Are you exposed?

Get a free report of your organization’s exposure to this CVE and threat

How IONIX’s External Exposure Management Platform Detects and Validates
Zero-Days to Shrink MTTR

1

Map your entire attack surface (continously)

IONIX uses multi-factor discovery methods, including DNS analysis, certificate mapping, metadata inspection, and more, to automatically map every internet-facing asset across your environment. This includes cloud instances, third-party platforms, shadow IT, and even forgotten infrastructure that traditional tools miss.

2

Monitor for new CVEs

Dozens of threat intel feeds using agentic technology are continuously analyzed to detect the appearance of proof-of-concept code, exploit kits, and indicators of active targeting. IONIX goes further by applying AI to proactively evaluate whether emerging vulnerabilities are likely to be exploited, even before PoCs go public.

3

Identify Potential External Exposures

Not all CVEs matter. IONIX filters vulnerabilities by asking attacker-centric questions: Can it be reached from the internet? Does it require authentication? Is it being exploited in the wild? This dramatically reduces noise and focuses teams on threats that can actually be weaponized.

4

Create Safe, Scalable Exploit Validations

IONIX transforms real-world PoCs into safe, non-intrusive test payloads that can be run in production environments without disruption. These simulations are precisely targeted to the systems that are vulnerable, ensuring rapid validation without unnecessary load.

5

Execute Exploit Validations

By combining context about software stack, versioning, exposure status, and reachability, IONIX ensures that only the right payloads are executed against the right assets, maximizing efficiency and minimizing risk.

6

Drive Fast and Actionable Remediation

Results are routed through integrations with ticketing, SOAR, and SIEM tools. Issues are written in plain language, bundled into remediation clusters, and prioritized based on asset criticality, exploitability, and blast radius. This shortens mean time to remediation (MTTR) and empowers teams to act with confidence.

Are you exposed?

Get a free report of your organization’s exposure to this CVE and threat

Subscribe to Threat Center RSS

Copy/paste the link below into your preferred RSS reader or follow these instructions to subscribe to Slack alerts.

Get Real-Time CVE Alerts to Your Email

Be the first to know when new zero-days emerge