Skip to content
major vulnerability· requires attention

proxy-addr is bundled by Express and used in many Node.js apps; this bug allows universal IP-trust bypass, affecting widespread web applications and auth/rate controls.

Web

CVE-2026-90711

9.1
Critical
EPSS n/aPatch availableSep 16, 2026

IP-trust bypass in proxy-addr lets attackers spoof client IP via X-Forwarded-For.

common questions

Is CVE-2026-90711 being exploited?

Not confirmed. CVE-2026-90711 does not appear in CISA's Known Exploited Vulnerabilities catalog, which records only exploitation that has been observed and reported publicly. That is evidence of absence of a report, not evidence the flaw is unattacked.

How severe is CVE-2026-90711?

CVE-2026-90711 is rated Critical with a CVSS score of 9.1. Severity describes how bad exploitation would be, not how likely it is: pair it with exploitation evidence before deciding what to patch first.

Is there a patch for CVE-2026-90711?

Yes. A fix has been recorded for CVE-2026-90711. The vendor advisory is the authority on the exact fixed version — apply it from there rather than from a summary.

What does CVE-2026-90711 affect?

CVE-2026-90711 affects proxy-addr 1.1.0-2.0.7, Express (via proxy-addr), Node.js applications using proxy-addr/Express. Confirm the exact affected versions against the vendor advisory before deciding you are exposed.

What should I do about CVE-2026-90711?

Upgrade proxy-addr to >=2.0.8 and audit trusted-proxy subnet notation.

Exploitation status reflects CISA's KEV catalog as we last synced it. Check the catalog directly.

executive summary
technical analysis
affected
proxy-addr 1.1.0-2.0.7Express (via proxy-addr)Node.js applications using proxy-addr/Express
impact

Unauthenticated attacker can control req.ip via X-Forwarded-For, bypassing IP-based auth, rate limits, geofencing, and tampering audit logs.

action required

Immediate action required

affected versions
proxy-addr proxy-addr
  • affected>= 1.1.0 and < 2.0.8
vendor says fixed in2.0.8

As published in the CVE Program record. A version outside these ranges is not a statement that it is unaffected — vendors sometimes understate a range, and distribution-backported builds carry upstream numbers that do not reflect what was patched into them.

how to fix
Remediation steps are tailored for users whose stack is affected. Add this technology to your stack to see the fix checklist.
references
get alerted

Track only the vulnerabilities that affect your infrastructure.

start for free