CVE-2026-90711

validatedZero produced an exploit or a check.

GHSA-jqcg-44mw-7w3h ↗EUVD-2026-78300 ↗

check availableZero validated a working check for it.not proven exploitableZero has a detection check, but hasn't produced a full working exploit yet.
cve.orgpublic pocExploit code has been published by someone. Source signals can also carry a PoC (Proof of Concept).kevAttacks confirmed in the real world.
npm:proxy-addr >= 1.1.0, < 2.0.8
fixed in 2.0.8
CWE-290 Authentication Bypass by Spoofing
ETK-2026-225, permanent identifier
pkg:npm/proxy-addr
+16dTTV
5mAI analysisAnalysis: how long the AI spent reversing this signal.
Check if you are vulnerable
timeline
0 = cve.org publication
trigger signal (cve.org) +0dcheck available+16dagent stopped
0
+5d
+10d
+15d

description

proxy-addr before 2.0.8 can incorrectly treat arbitrary IPv4 clients as trusted proxies when an application uses certain IPv4-mapped IPv6 or zero-leading IPv6 trust ranges. An unauthenticated client may then influence the client address derived from forwarding headers, undermining controls that rely on source IP addresses. Exploitation depends on the application having an affected proxy-trust configuration.

mitigation

Upgrade proxy-addr to version 2.0.8 or later. Until upgraded, express IPv4 trusted ranges in IPv4 notation or correct IPv4-mapped IPv6 prefixes so they include the mapped-address marker.

fixed in 2.0.8

check
available
exploit
no
automationDeterministic: a check that runs on its own, the same request on every target. Contextual: an agentic technique that needs to be applied per target, for bugs that depend on contextual flows.
contextual
auth requiredWhether an attacker needs an account first, based on the CVSS vector's Privileges Required.
no
EPSSEstimate of the chance this CVE is exploited in the next 30 days. Refreshed daily.
0.33%24th percentile
agent run time
5m
cve.org record, t = 0The moment cve.org publishes the CVE in full.
2026-09-15 06:19Z
Δ to public pocExploit code has been published by someone. Source signals can also carry a PoC (Proof of Concept).
–
Δ to kevAttacks confirmed in the real world.
–

outcome

Contextual check: a technique exists and was validated, but no deterministic check could cover this one.

source signals

Public signals that triggered or updated the pipeline. These are inputs for the deltas above.

  1. 2026-09-15 06:19Z
  2. 2026-09-15 06:19Z

this entry in the feed

GET /api/v1/feed/CVE-2026-90711

{
  "etk_id": "ETK-2026-225",
  "cve_id": "CVE-2026-90711",
  "display_id": "CVE-2026-90711",
  "ghsa_id": "GHSA-jqcg-44mw-7w3h",
  "euvd_id": "EUVD-2026-78300",
  "status": "published",
  "anchor_state": "anchored",
  "title": "Proxy trust-range validation flaw in proxy-addr",
  "summary": "proxy-addr before 2.0.8 can incorrectly treat arbitrary IPv4 clients as trusted proxies when an application uses certain IPv4-mapped IPv6 or zero-leading IPv6 trust ranges. An unauthenticated client may then influence the client address derived from forwarding headers, undermining controls that rely on source IP addresses. Exploitation depends on the application having an affected proxy-trust configuration.",
  "mitigation": "Upgrade proxy-addr to version 2.0.8 or later. Until upgraded, express IPv4 trusted ranges in IPv4 notation or correct IPv4-mapped IPv6 prefixes so they include the mapped-address marker.",
  "vendor": "npm",
  "product": "npm:proxy-addr",
  "affected": [
    {
      "affected_notes": [],
      "affected_ranges": [
        ">= 1.1.0, < 2.0.8"
      ],
      "ecosystem": "npm",
      "fixed_versions": [
        "2.0.8"
      ],
      "package_name": "proxy-addr",
      "purl": "pkg:npm/proxy-addr"
    }
  ],
  "cwes": [
    290
  ],
  "cvss_score": 9.1,
  "cvss_src": "cna_vendor",
  "cvss_vector": "CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:N",
  "epss_score": 0.0033,
  "epss_percentile": 0.2496,
  "epss_asof": "2026-10-20",
  "automation": "contextual",
  "check": true,
  "check_confidence_basis": "assessed",
  "exploit": false,
  "pipeline_minutes": 5.33564445,
  "t0_at": "2026-09-15T06:19:46.332000+00:00",
  "signals": {
    "check": {
      "at": "2026-10-01T09:57:34.385191+00:00",
      "days": 16.151250615636574,
      "is_lower_bound": false,
      "measured_at": "2026-09-15T06:19:46.332000+00:00",
      "url": null
    },
    "trigger_signal": {
      "at": "2026-09-15T06:19:46.332000+00:00",
      "days": 0,
      "is_lower_bound": false,
      "measured_at": "2026-09-15T06:19:46.332000+00:00",
      "url": "https://github.com/jshttp/proxy-addr/security/advisories/GHSA-jqcg-44mw-7w3h"
    }
  }
}

published 2026-10-01 09:46Z
last change 2026-10-21 11:18Z

Need the technical details behind an entry?

Every entry here shows what we attempted and when. The technical details, the generated exploit that fired it and the evidence behind the verdict are not public. Tell us about your use case and we’ll get back to you about extended API access.