CVE-2026-72817

MEDIUMPre-NVD 6.56.5—
EchelonGraph scoreMEDIUM confidence

Score 6.5 from GitHub Security Advisory published 2026-08-14. A secondary CVSS source baseline 6.5; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: epss, ghsa, secondary
Trending — 4 sources updated this week
6.5EG
EchelonGraph verdictMonitorLow exploitation likelihood right now — keep watching.
  • Lower severity and no public exploit yet
CISA-KEV: Not listedEPSS PROB: 0.2%CVSS: 6.5Exploit: None knownExposed services: Not assessed

A fix is available — apply it.

go-chi/chi versions 0.9.0 before 5.3.0 contains an IP spoofing vulnerability in the RealIP middleware, which resolves the request source IP (Request.RemoteAddr) using the first IP in the X-Forwarded-For header without validating trusted proxies. A malicious client can prepend a forged IP as the first value of the X-Forwarded-For header to spoof the request source IP, potentially bypassing access controls or falsifying request logs.

CVSS v3
6.5
EG Score
6.5MEDIUMmedium confidence
EG Risk
34
EG Risk 34/100CISA SSVC

EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).

How it’s computed
Severity65% × 45%
Exploitation0% × 40%
Automatability30% × 15%
CISA SSVC: Track at low or medium mission impact; Track or Attend at high (mission-essential systems).
Action: A fix is available. Apply it within your standard update timelines at low or medium mission impact and sooner than that at high.
EPSS PROB
0.2%
EPSS %ILE
13th
KEV
Not listed

CISA SSVCTrack at low or medium mission impact; Track or Attend at high (mission-essential systems).

A fix is available. Apply it within your standard update timelines at low or medium mission impact and sooner than that at high.

Exploitation none (no KEV listing, exploit record or EPSS ≥ 50%) · Automatable unknown (not published for this CVE) · Technical impact partial (CVSS below 9.0). Mission impact is CISA's Mission & Well-being decision point, and only you can judge it: high means the affected system is essential to your organisation's mission, or its compromise could cause irreversible harm to people. CISA's decision table

Published

August 14, 2026

Last Modified

September 9, 2026

Advisory Details (2)

Auto-updated Aug 14, 2026
🔬 Proof of concept available. Patch available. Sources: github.
generic

go-chi chi 0.9.0 before 5.3.0 IP Spoofing via X-Forwarded-For | Advisories | VulnCheck

https://www.vulncheck.com/advisories/go-chi-chi-before-ip-spoofing-via-x-forwarded-for
github Patch Available🟡 PoC Available

Potential IP Spoofing via `X-Forwarded-For` Header in `Request.RemoteAddr` Resolution · Advisory · go-chi/chi · GitHub

https://github.com/go-chi/chi/security/advisories/GHSA-9g5q-2w5x-hmxf

Patch Availability(3)

Vendor / EcosystemFix (by version range) / PatchReleasedSource
redhatcosign-main-3.1.3-0.1.hum12026-08-12redhat
redhatspire1-14-main-1.14.7-0.4.hum12026-08-03redhat
redhatspire1-15-main-1.15.2-0.4.hum12026-08-03redhat

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

(9 across 4 ecosystems)
Go(6)
PackageVulnerable rangeFix by version rangeDependents
github.com/go-chi/chi/middleware—
  • 0.9.0 through 1.5.5: no fix on record
—
github.com/go-chi/chi/v2/middleware—
  • every version through 2.1.1: no fix on record
—
github.com/go-chi/chi/v3/middleware—
  • every version through 3.3.5: no fix on record
—
github.com/go-chi/chi/v4/middleware—
  • every version through 4.1.3: no fix on record
—
github.com/go-chi/chi/v5—
  • every version up to 5.3.0: fixed in 5.3.0
—
github.com/go-chi/chi/v5/middleware—
  • every version up to 5.3.0: fixed in 5.3.0
—
Debian:12(1)
PackageVulnerable rangeFix by version rangeDependents
golang-github-go-chi-chi5.0.7-1 ... 5.3.0-1 (6 versions)
  • every version on: no fix on record
—
Debian:13(1)
PackageVulnerable rangeFix by version rangeDependents
golang-github-go-chi-chi5.2.0-1, 5.2.3-1, 5.2.5-1, 5.3.0-1
  • every version on: no fix on record
—
Debian:14(1)
PackageVulnerable rangeFix by version rangeDependents
golang-github-go-chi-chi5.2.0-1, 5.2.3-1, 5.2.5-1
  • every version up to 5.3.0-1: fixed in 5.3.0-1
—

Weakness Classification(1)

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

Data Freshness Timeline

(refreshed 15× in last 7d / 91× in last 30d)

Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. 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. Most recent first.

Showing the most recent 100 of 171 total refreshes for this CVE.

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

Frequently asked(5)

What is CVE-2026-72817?
CVE-2026-72817 is a medium vulnerability published on August 14, 2026. go-chi/chi versions 0.9.0 before 5.3.0 contains an IP spoofing vulnerability in the RealIP middleware, which resolves the request source IP (Request.RemoteAddr) using the first IP in the X-Forwarded-For header without validating trusted proxies. A malicious client can prepend a forged IP as the…
When was CVE-2026-72817 disclosed?
CVE-2026-72817 was first published on August 14, 2026, with the most recent update on September 9, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-72817 actively exploited?
CVE-2026-72817 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.2% probability of exploitation in the next 30 days (13th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-72817?
CVE-2026-72817 has a CVSS base score of 6.5 (a secondary CVSS source that NVD displays; NVD's own analysis pending).
How do I remediate CVE-2026-72817?
A fix for CVE-2026-72817 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2026-72817 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-72817

Explore →

Is Your Infrastructure Affected by CVE-2026-72817?

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