CVE-2026-72815

MEDIUMPre-NVD 6.96.9—
EchelonGraph scoreMEDIUM confidence

This medium-severity CVE scores 6.9 under a secondary CVSS source (NVD's own analysis pending). EPSS exploit probability: 0.4%, top 66% of all CVEs by exploit prediction. GitHub Security Advisory data not yet ingested — confidence will rise once GHSA publishes (typical lag: hours to days for open-source ecosystem CVEs; never for infrastructure-only CVEs).

Triggered by: NVD CVSS baseline
Sources: epss, secondary
Trending — 4 sources updated this weekElevated
6.9EG
EchelonGraph verdictMonitorLow exploitation likelihood right now — keep watching.
  • Lower severity and no public exploit yet
CISA-KEV: Not listedEPSS PROB: 0%CVSS: 6.9Exploit: Elevated riskExposed: 0

A fix is available — apply it.

go-chi chi versions >= 5.2.1 and before 5.3.0 contain an IP spoofing vulnerability in the RealIP middleware, which blindly trusts the first (leftmost) value of the X-Forwarded-For HTTP header. A remote attacker can bypass IP-based access control lists and rate-limiting mechanisms, and forge log entries, by supplying a spoofed IP address in the X-Forwarded-For header. The issue is fixed in version 5.3.0.

CVSS v3
6.9
EG Score
6.9(medium)
EG Risk
62(Attend)
EG Risk 62/100SSVC: Attend

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
Severity69% × 45%
Exploitation40% × 40%
Automatability100% × 15%
Action: Remediate soon — notable exploitation risk.
EPSS PROB
0%
EPSS %ILE
34%
KEV
Not listed

Published

August 14, 2026

Last Modified

August 18, 2026

Advisory Details (2)

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

go-chi chi v5.2.1 IP Spoofing via X-Forwarded-For Header | Advisories | VulnCheck

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

IP Spoofing Vulnerability in `middleware.RealIP` · Advisory · go-chi/chi · GitHub

https://github.com/go-chi/chi/security/advisories/GHSA-3fxj-6jh8-hvhx

Vendor Advisories for CVE-2026-72815(5)

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

Patch Availability(4)

Vendor / EcosystemFixed in / PatchReleasedSource
redhatcosign-main-3.1.3-0.1.hum12026-08-12redhat
redhatprometheus3-13-main-3.13.2-0.2.hum12026-08-04redhat
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

(5 across 4 ecosystems)
Go(2)
PackageVulnerable rangeFixed inDependents
github.com/go-chi/chi/v5—5.3.0—
github.com/go-chi/chi/v5/middleware—5.3.0—
Debian:12(1)
PackageVulnerable rangeFixed inDependents
golang-github-go-chi-chi5.0.7-1 ... 5.3.0-1 (6 versions)——
Debian:13(1)
PackageVulnerable rangeFixed inDependents
golang-github-go-chi-chi5.2.0-1, 5.2.3-1, 5.2.5-1, 5.3.0-1——
Debian:14(1)
PackageVulnerable rangeFixed inDependents
golang-github-go-chi-chi5.2.0-1, 5.2.3-1, 5.2.5-15.3.0-1—

Weakness Classification(1)

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

Data Freshness Timeline

(refreshed 25× in last 7d / 111× 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 133 total refreshes for this CVE.

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

Frequently asked(5)

What is CVE-2026-72815?
CVE-2026-72815 is a medium vulnerability published on August 14, 2026. go-chi chi versions >= 5.2.1 and before 5.3.0 contain an IP spoofing vulnerability in the RealIP middleware, which blindly trusts the first (leftmost) value of the X-Forwarded-For HTTP header. A remote attacker can bypass IP-based access control lists and rate-limiting mechanisms, and forge log…
When was CVE-2026-72815 disclosed?
CVE-2026-72815 was first published in the National Vulnerability Database on August 14, 2026, with the most recent update on August 18, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-72815 actively exploited?
CVE-2026-72815 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0% probability of exploitation in the next 30 days, which ranks it in the top 66.3% of all scored CVEs.
What is the CVSS score of CVE-2026-72815?
CVE-2026-72815 has a CVSS v3 base score of 6.9 (NVD).
How do I remediate CVE-2026-72815?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-72815, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

Dependency Blast Radius

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

Explore →

Is Your Infrastructure Affected by CVE-2026-72815?

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

Start Free Scan →Browse All CVEs