CVE-2026-90711

CRITICALPre-NVD 9.19.1
EchelonGraph scoreHIGH confidence

“—” beside the score: it is equal to the CVSS score beside it.

Score 9.1 from GitHub Security Advisory (severity: CRITICAL) published 2026-10-05. A secondary CVSS source baseline 9.1; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: EPSS, GitHub Security Advisory, a secondary CVSS source
Trending — Patch released this week

Also known asEUVD-2026-78300 (ENISA EUVD) · GHSA-jqcg-44mw-7w3h (GitHub Security Advisories)Source: ENISA EUVD

9.1EG
EchelonGraph verdictPlan a fixRemediate within your standard update timelines (the SSVC decision on this page).
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 0.3%CVSS: 9.1Exploit: None knownExposed services: Not assessed

A fix is available — apply it.

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.

CVSS v3
9.1
EG Score
9.1CRITICALhigh confidence
EG Risk
41
EG Risk 41/100

EG Risk is EchelonGraph's 0–100 priority score. It fuses impact severity (EG Severity, the CVSS base score, never the KEV-floored or EPSS-lifted EG Score) with real-world exploitation and automatability, under weights EchelonGraph set by hand, so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner.

How it’s computed (value × EchelonGraph’s weight)
Severity91% × 45%
Impact severity (EG Severity): CVSS 9.1 of 10. Never the KEV-floored or EPSS-lifted EG Score.
Exploitation0.3% × 40%
FIRST EPSS: the 30-day exploitation probability when EchelonGraph scored this CVE.
Automatability0% × 15%
CISA's SSVC Automatable value: no (Vulnrichment).
SSVC (CISA's decision table, applied by EchelonGraph): Track at low or medium mission impact; Track* at high (mission-essential systems).
Exploitation none (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact total (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE.
Action: A fix is available. Apply it within your standard update timelines.
EPSS PROB
0.3%
EPSS %ILE
17th
KEV
Not listed

What the EG score is made of (scorer v4.0: the three questions the 0–10 score mixes, published apart · methodology)

The EG score (9.1): severity, escalated by confirmed exploitation. This CVE's 9.1 is its impact severity (EG Severity), not escalated.

EG Severity
9.1 CRITICALCVSS-B, impact only: no KEV listing, EPSS or EG-KEV tier raises it.GitHub Security Advisory CVSS
EG Likelihood
0.3% within 30 daysSource: FIRST EPSS (model v2026.06.15, score date 2026-11-01). FIRST's exploitation probability, not an EchelonGraph model.
Confirmed exploitation
None on record (CISA KEV, EG-KEV Tier 1)Reported apart from the likelihood: an observed fact, not a probability.
EG Priority
SSVC Track at medium mission impactTrack at low or medium mission impact; Track* at high (mission-essential systems).CISA BOD 26-04: 14 days if the affected system is publicly exposed; Fix on system upgrade if it is not.Each input and its source, and whom BOD 26-04 binds: the SSVC and BOD 26-04 blocks below.

SSVC (CISA's decision table, applied by EchelonGraph)Track at low or medium mission impact; Track* at high (mission-essential systems).

A fix is available. Apply it within your standard update timelines.

Exploitation none (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact total (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE. Mission impact is CISA's Mission & Well-being decision point, and only you can judge it. CISA's table makes it high when Mission Prevalence is Essential — the vulnerable component "directly provides capabilities that constitute at least one MEF for at least one entity" (MEF: mission essential function) — or when Public Well-Being Impact is Irreversible: "multiple fatalities are likely", the cyber-physical system "is likely lost or destroyed", "extreme or serious externalities" are imposed on other parties, or social systems such as elections or the financial grid "are destabilized and potentially collapse". CISA's decision table

BOD 26-04 (CISA's remediation timeline, Table 1)14 days if the affected system is publicly exposed; Fix on system upgrade if it is not.

The score's inputs: In CISA KEV no (CISA's KEV catalog) · Automatable no (CISA Vulnrichment) · Technical impact total (CISA Vulnrichment). Whether your system is publicly exposed is yours to answer. BOD 26-04 binds US Federal Civilian Executive Branch agencies; for anyone else it is CISA's published timeline, a reference rather than an obligation. The directive · how EchelonGraph applies it

Published

September 15, 2026

Last Modified

September 16, 2026

Advisory Details (2)

Auto-updated Sep 15, 2026
Patch available. Sources: github.
GitHub advisoryMentions a patch (unverified)

proxy-addr vulnerable to IP spoofing via IPv4-mapped IPv6 trust subnet · Advisory · jshttp/proxy-addr · GitHub

https://github.com/jshttp/proxy-addr/security/advisories/GHSA-jqcg-44mw-7w3h
Web page

Security Advisories | OpenJS Foundation CVE Numbering Authority

https://cna.openjsf.org/security-advisories.html

Vendor Advisories for CVE-2026-90711(8)

These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.

Patch Availability(10)

Vendor / EcosystemFix (by version range) / PatchReleasedSource
redhatsatellite/iop-remediations-rhel9:17930651382026-10-29redhat
redhatrhoai/odh-mod-arch-model-registry-rhel9:17930018272026-10-29redhat
redhatsatellite/iop-remediations-rhel9:17930922532026-10-29redhat
redhatdevspaces/jetbrains-ide-rhel9:17924764272026-10-26redhat
redhatrhdh/rhdh-hub-rhel9:17925938172026-10-22redhat
redhatautomation-platform-ui-0:2.6.15-1.el9ap2026-10-21redhat
redhatrhdh/red-hat-developer-hub-backstage-plugin-scaffolder-backend-module-orchestrator:17925085222026-10-21redhat
redhatansible-automation-platform/automation-portal:17925236402026-10-21redhat
redhatrhmtc/openshift-migration-ui-rhel8:17918532812026-10-20redhat
npmproxy-addr @ 2.0.8 (fixes >= 1.1.0, < 2.0.8)—ghsa

Patches are aggregated from vendor advisories (Red Hat, Microsoft, Cisco, GitHub) and package ecosystems (OSV, GHSA). Multiple rows for the same upstream release have been deduplicated.

Affected Packages

(4 across 4 ecosystems)
Debian:12(1)
PackageVulnerable rangeFix by version rangeDependents
node-proxy-addr2.0.7+~cs2.3.0-1, 2.0.7+~cs2.3.7-1, 2.0.8+~cs2.3.7-1
  • every version on: no fix on record
—
Debian:13(1)
PackageVulnerable rangeFix by version rangeDependents
node-proxy-addr2.0.7+~cs2.3.0-1, 2.0.7+~cs2.3.7-1, 2.0.8+~cs2.3.7-1
  • every version on: no fix on record
—
Debian:14(1)
PackageVulnerable rangeFix by version rangeDependents
node-proxy-addr2.0.7+~cs2.3.0-1, 2.0.7+~cs2.3.7-1
  • every version up to 2.0.8+~cs2.3.7-1: fixed in 2.0.8+~cs2.3.7-1
—
npm(1)
PackageVulnerable rangeFix by version rangeDependents
proxy-addr—
  • 1.1.0 up to 2.0.8: fixed in 2.0.8
—

Weakness Classification(3)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

Additional Vendor Advisories

(2)

Vendors that published advisories for this CVE beyond the curated set above. Broader coverage but minimal per-row detail — click through for the original advisory.

Data Freshness Timeline

(refreshed 24× in last 7d / 80× in last 30d)

Each row is a time one of our pipelines fetched, updated or re-scored this CVE. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. An arrow marks a change the record states ("CVSS v3 → 9.1"); EPSS and GHSA rows show the values recorded at that time, not what changed (EPSS values are rounded; hover one for the exact figures). Most recent first.

Showing the most recent 99 of 116 refreshes on record for this CVE.

A repeat, a row identical to one the same pipeline wrote less than 10 seconds earlier, is not a separate refresh and is not counted. 1 repeat row among the latest 100 is merged into the row it repeats. The 17 oldest rows on record are not shown and were not checked, so the counts can still include repeats.

  1. 2026-11-01 18:50 UTCEG score recompute
  2. 2026-11-01 18:50 UTCVendor advisory
  3. 2026-11-01 18:50 UTCGHSA enrichmentGHSA-jqcg-44mw-7w3h · GitHub severity CRITICAL · GitHub CVSS 9.1
  4. 2026-11-01 16:36 UTCEPSS rescoreEPSS 0.3% · 17th percentile
  5. 2026-11-01 07:37 UTCGHSA enrichmentGHSA-jqcg-44mw-7w3h · GitHub severity CRITICAL · GitHub CVSS 9.1
  6. 2026-11-01 07:37 UTCEG score recompute
  7. 2026-10-31 19:50 UTCEG score recompute
  8. 2026-10-31 19:50 UTCVendor advisory
  9. 2026-10-31 16:33 UTCEPSS rescoreEPSS 0.3% · 17th percentile
  10. 2026-10-30 20:50 UTCEG score recompute
  11. 2026-10-30 20:50 UTCVendor advisory
  12. 2026-10-30 16:35 UTCEPSS rescoreEPSS 0.3% · 17th percentile
  13. 2026-10-29 21:50 UTCEG score recompute
  14. 2026-10-29 21:50 UTCVendor advisory
  15. 2026-10-29 16:34 UTCEPSS rescoreEPSS 0.3% · 17th percentile
  16. 2026-10-28 22:50 UTCEG score recompute
  17. 2026-10-28 22:50 UTCVendor advisory
  18. 2026-10-28 16:33 UTCEPSS rescoreEPSS 0.3% · 17th percentile
  19. 2026-10-27 23:51 UTCEG score recompute
  20. 2026-10-27 23:51 UTCVendor advisory
  21. 2026-10-27 16:33 UTCEPSS rescoreEPSS 0.3% · 17th percentile
  22. 2026-10-27 00:49 UTCEG score recompute
  23. 2026-10-27 00:49 UTCVendor advisory
  24. 2026-10-26 16:32 UTCEPSS rescoreEPSS 0.3% · 17th percentile
  25. 2026-10-25 22:07 UTCEG score recompute
Show 74 more
  1. 2026-10-25 22:07 UTCVendor advisory
  2. 2026-10-25 16:34 UTCEPSS rescoreEPSS 0.3% · 17th percentile
  3. 2026-10-25 13:51 UTCEG score recompute
  4. 2026-10-24 23:01 UTCEG score recompute
  5. 2026-10-24 23:01 UTCVendor advisory
  6. 2026-10-24 16:34 UTCEPSS rescoreEPSS 0.3% · 16th percentile
  7. 2026-10-24 00:02 UTCEG score recompute
  8. 2026-10-24 00:02 UTCVendor advisory
  9. 2026-10-23 16:32 UTCEPSS rescoreEPSS 0.3% · 16th percentile
  10. 2026-10-23 01:01 UTCEG score recompute
  11. 2026-10-23 01:01 UTCVendor advisory
  12. 2026-10-22 16:35 UTCEPSS rescoreEPSS 0.3% · 16th percentile
  13. 2026-10-22 02:02 UTCEG score recompute
  14. 2026-10-22 02:02 UTCVendor advisory
  15. 2026-10-21 16:34 UTCEPSS rescoreEPSS 0.3% · 25th percentile
  16. 2026-10-21 02:59 UTCEG score recompute
  17. 2026-10-21 02:59 UTCVendor advisory
  18. 2026-10-20 16:34 UTCEPSS rescoreEPSS 0.3% · 24th percentile
  19. 2026-10-20 03:57 UTCEG score recompute
  20. 2026-10-19 16:33 UTCEPSS rescoreEPSS 0.3% · 24th percentile
  21. 2026-10-19 04:52 UTCEG score recompute
  22. 2026-10-18 16:33 UTCEPSS rescoreEPSS 0.3% · 24th percentile
  23. 2026-10-18 03:00 UTCEG score recompute
  24. 2026-10-17 16:35 UTCEPSS rescoreEPSS 0.3% · 24th percentile
  25. 2026-10-17 06:02 UTCEG score recompute
  26. 2026-10-16 16:45 UTCEPSS rescoreEPSS 0.3% · 24th percentile
  27. 2026-10-16 07:01 UTCEG score recompute
  28. 2026-10-15 16:33 UTCEPSS rescoreEPSS 0.3% · 24th percentile
  29. 2026-10-15 05:46 UTCEG score recompute
  30. 2026-10-14 16:34 UTCEPSS rescoreEPSS 0.3% · 24th percentile
  31. 2026-10-14 01:23 UTCEG score recompute
  32. 2026-10-13 16:35 UTCEPSS rescoreEPSS 0.3% · 24th percentile
  33. 2026-10-12 21:36 UTCEG score recompute
  34. 2026-10-12 16:35 UTCEPSS rescoreEPSS 0.3% · 24th percentile
  35. 2026-10-12 14:46 UTCEG score recompute
  36. 2026-10-11 19:14 UTCEG score recompute
  37. 2026-10-11 16:30 UTCEG score recompute
  38. 2026-10-11 14:36 UTCEG score recompute
  39. 2026-10-11 13:50 UTCEPSS rescoreEPSS 0.3% · 24th percentile
  40. 2026-10-11 13:45 UTCEG score recompute
  41. 2026-10-10 22:56 UTCEG score recompute
  42. 2026-10-10 20:00 UTCEPSS rescoreEPSS 0.3% · 24th percentile
  43. 2026-10-09 20:21 UTCEG score recompute
  44. 2026-10-09 20:08 UTCEPSS rescoreEPSS 0.3% · 24th percentile
  45. 2026-10-08 22:42 UTCEG score recompute
  46. 2026-10-08 17:14 UTCEPSS rescoreEPSS 0.3% · 24th percentile
  47. 2026-10-08 03:49 UTCEG score recompute
  48. 2026-10-07 23:48 UTCEPSS rescoreEPSS 0.3% · 24th percentile
  49. 2026-10-06 19:04 UTCEG score recompute
  50. 2026-10-06 15:18 UTCEPSS rescoreEPSS 0.3% · 24th percentile
  51. 2026-10-05 20:39 UTCEG score recompute
  52. 2026-10-05 17:44 UTCEPSS rescoreEPSS 0.3% · 24th percentile
  53. 2026-10-05 02:15 UTCEG score recompute
  54. 2026-10-04 23:22 UTCEPSS rescoreEPSS 0.3% · 24th percentile
  55. 2026-10-03 18:52 UTCEG score recompute
  56. 2026-10-02 18:19 UTCEG score recompute
  57. 2026-10-02 00:16 UTCEG score recompute
  58. 2026-10-01 19:51 UTCEPSS rescoreEPSS 0.3% · 24th percentile
  59. 2026-09-30 19:05 UTCEG score recompute
  60. 2026-09-30 15:04 UTCEPSS rescoreEPSS 0.3% · 23rd percentile
  61. 2026-09-29 20:21 UTCEG score recompute
  62. 2026-09-29 01:11 UTCEG score recompute
  63. 2026-09-28 16:20 UTCEG score recompute
  64. 2026-09-28 13:52 UTCEPSS rescoreEPSS 0.3% · 23rd percentile
  65. 2026-09-27 13:55 UTCEG score recompute
  66. 2026-09-27 13:49 UTCEPSS rescoreEPSS 0.3% · 23rd percentile
  67. 2026-09-26 20:07 UTCEG score recompute
  68. 2026-09-26 15:59 UTCEPSS rescoreEPSS 0.3% · 23rd percentile
  69. 2026-09-26 01:55 UTCEG score recompute
  70. 2026-09-24 14:36 UTCEG score recompute
  71. 2026-09-24 14:04 UTCEPSS rescoreEPSS 0.3% · 23rd percentile
  72. 2026-09-22 18:36 UTCEG score recompute
  73. 2026-09-22 16:01 UTCEPSS rescoreEPSS 0.2% · 8th percentile
  74. 2026-09-22 00:59 UTCEG score recompute

Related CVEs(same vendor + same CWE)

Frequently asked(5)

What is CVE-2026-90711?
CVE-2026-90711 is a critical-severity vulnerability; its CVE record was published on September 15, 2026. 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…
When was the CVE record for CVE-2026-90711 published?
The CVE record for CVE-2026-90711 was published on September 15, 2026. That is the record's publication date; the vulnerability itself may have been made public earlier. EchelonGraph's copy of the record carries a last-modified date of September 16, 2026; the record at its source may have been updated since.
Is CVE-2026-90711 actively exploited?
CVE-2026-90711 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.3% probability of exploitation in the next 30 days (17th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-90711?
CVE-2026-90711 has a CVSS base score of 9.1 (a secondary CVSS source that NVD displays; NVD's own analysis pending).
How do I remediate CVE-2026-90711?
A fix for CVE-2026-90711 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2026-90711 are linked in the Vendor Advisories panel on this page.

Dependency Blast Radius

See which npm, PyPI, Go, and Maven packages are affected by CVE-2026-90711

Explore →

Is Your Infrastructure Affected by CVE-2026-90711?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.

Book a Demo →Browse All CVEs