CVE-2026-72817: go-chi chi 0.9.0 before 5.3.0 IP Spoofing via X-Forwarded-For
Noroxi assessment
Priority: Monitor (action score 27/100)
- The sources we track (CISA KEV, Exploit-DB, Metasploit, Nuclei, GitHub) show no public exploit code or exploitation in the wild.
- Probability of exploitation in the next 30 days: 0.24% (FIRST EPSS).
- Anyone who can reach it over the internet can trigger it. No account or password is required. No user action is required. No special conditions are required; it is repeatable.
- According to CISA the attack is automatable: targets can be found by mass scanning.
- Fixed version: go-chi chi 5.3.0; azl3 gh 2.62.0-20 on Azure Linux 3.0 2.97.0-1; azl3 influxdb 2.7.5-20 on Azure Linux 3.0 2.7.5-21.
Low priority for now. Upgrade to go-chi chi 5.3.0; azl3 gh 2.62.0-20 on Azure Linux 3.0 2.97.0-1; azl3 influxdb 2.7.5-20 on Azure Linux 3.0 2.7.5-21 or later.
Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it
Primary sources: NVD · CVE.org · FIRST EPSS
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.
- GHSA-9g5q-2w5x-hmxf
- GO-2026-5775
- openSUSE-SU-2026:11574-1
- openSUSE-SU-2026:11578-1
- openSUSE-SU-2026:11591-1
- openSUSE-SU-2026:11810-1
- openSUSE-SU-2026:21645-1
- openSUSE-SU-2026:21653-1
- openSUSE-SU-2026:21670-1
- openSUSE-SU-2026:21793-1
- openSUSE-SU-2026:21918-1
- RHSA-2026:49718
- RHSA-2026:49732
- RHSA-2026:54420
- Published
- Aug 14, 2026
- Updated
- Oct 8, 2026
- EPSS
- 0.2% · 15th percentile
- CWE
- CWE-345
Report tools
Action score
27
Low priority for now.
- CVSS
- 27 / 40 · 6.9 / 10
- CISA KEV
- 0 / 30 · Not listed
- EPSS
- 0 / 30 · 0.2%
CISA SSVC decision
- Exploitation
- none
- Automatable
- yes
- Technical impact
- partial
Vulnrichment: CISA's decision-tree inputs.
CNA vs NVD score
- NVD
- —
- CNA · VulnCheck
- 6.9
- NVD has not scored this yet; the score shown is the CNA’s.
CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:L/VI:L/VA:N/SC:N/SI:N/SA:N
The score given by the assigning authority versus NVD’s independent score. A gap means the severity is contested.
Get told when this record changes
- Not in KEV: no record of exploitation in the wild
- No public exploit code on record
- A fix has been released
If any of these changes, we'll tell you in the daily email digest.
Is your version affected? Check itNoroxi analysis
What does it mean in your environment?
The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.
We use this product, ask for helpAffected systems
Is your version affected?
Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.
—
Versions reported by the vendor
Affected version ranges reported by the assigning authority (VulnCheck). Independent of NVD's CPE analysis and usually ahead of it.
go-chi chi
- 5.3.0not affected
- 0.9.0 and later · before 5.3.0affected · semver
Package-level exposure
OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.
| Ecosystem | Package | Affected range | Fix |
|---|---|---|---|
| Debian:12 | golang-github-go-chi-chi | from 0 | — |
| Debian:14 | golang-github-go-chi-chi | before 5.3.0-1 | 5.3.0-1 |
| Go | github.com/go-chi/chi/middleware | from 0.9.0 · up to and including 1.5.5 | — |
| Go | github.com/go-chi/chi/v2/middleware | up to and including 2.1.1 | — |
| Go | github.com/go-chi/chi/v3/middleware | up to and including 3.3.5 | — |
| Go | github.com/go-chi/chi/v4/middleware | up to and including 4.1.3 | — |
| Go | github.com/go-chi/chi/v5 | before 5.3.0 | 5.3.0 |
| Go | github.com/go-chi/chi/v5/middleware | before 5.3.0 | 5.3.0 |
| openSUSE:Leap 16.0 | cloudflared | before 2026.8.2-bp160.1.1 | 2026.8.2-bp160.1.1 |
| openSUSE:Leap 16.0 | hauler | before 2.1.0-bp160.1.1 | 2.1.0-bp160.1.1 |
| openSUSE:Leap 16.0 | trivy | before 0.74.0-160000.1.1 | 0.74.0-160000.1.1 |
| openSUSE:Leap 16.0 | v2ray-core | before 5.53.0-bp160.1.1 | 5.53.0-bp160.1.1 |
| openSUSE:Leap 16.0 | warewulf4 | before 4.7.1-bp160.1.1 | 4.7.1-bp160.1.1 |
| openSUSE:Tumbleweed | hauler | before 2.0.3-1.1 | 2.0.3-1.1 |
| openSUSE:Tumbleweed | trivy | before 0.74.0-1.1 | 0.74.0-1.1 |
| openSUSE:Tumbleweed | v2ray-core | before 5.53.0-1.1 | 5.53.0-1.1 |
| openSUSE:Tumbleweed | warewulf4 | before 4.7.1-1.1 | 4.7.1-1.1 |
| Red Hat:hummingbird:1 | cosign | before 0:3.1.3-0.1.hum1 | 0:3.1.3-0.1.hum1 |
| Red Hat:hummingbird:1 | spire1.14 | before 0:1.14.7-0.4.hum1 | 0:1.14.7-0.4.hum1 |
| Red Hat:hummingbird:1 | spire1.14-agent | before 0:1.14.7-0.4.hum1 | 0:1.14.7-0.4.hum1 |
| Red Hat:hummingbird:1 | spire1.14-oidc-discovery-provider | before 0:1.14.7-0.4.hum1 | 0:1.14.7-0.4.hum1 |
| Red Hat:hummingbird:1 | spire1.14-server | before 0:1.14.7-0.4.hum1 | 0:1.14.7-0.4.hum1 |
| Red Hat:hummingbird:1 | spire1.15 | before 0:1.15.2-0.4.hum1 | 0:1.15.2-0.4.hum1 |
| Red Hat:hummingbird:1 | spire1.15-agent | before 0:1.15.2-0.4.hum1 | 0:1.15.2-0.4.hum1 |
+2
Same product
go-chi: all recordsOther highest-scoring records for the same primary product.
- CVE-2026-72816go-chi chi before 5.3.0 IP Spoofing via RealIP Middleware27Monitor
- CVE-2026-72815go-chi chi v5.2.1 IP Spoofing via X-Forwarded-For Header27Monitor
- CVE-2026-118681go-chi chi before 5.5.0 Authentication Bypass via SupressNotFound Middleware25Monitor
Published before and after this one in the same product
- ← EarlierCVE-2025-71405Aug 14, 2026 · go-chi chi before v5.2.2 Open Redirect via RedirectSlashes20Monitor
- Later →CVE-2026-114437Oct 21, 2026 · Chi Client IP Spoofing in ClientIPFromXFF via X-Forwarded-For25Monitor
- Later →CVE-2026-122132Nov 4, 2026 · go-chi chi 5.2.2 through 5.5.0 Open Redirect via RedirectSlashes Middleware20Monitor
Remediation
Which version to upgrade to
Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.
| Product / package | Fixed version | Source |
|---|---|---|
| go-chi chi | 5.3.0 | Vendor (CNA) |
| azl3 gh 2.62.0-20 on Azure Linux 3.0 | 2.97.0-1 · CBL-Mariner Releases | Microsoft (MSRC) |
| azl3 influxdb 2.7.5-20 on Azure Linux 3.0 | 2.7.5-21 | Microsoft (MSRC) |
| debian:golang-github-go-chi-chi | 5.3.0-1 · Debian:14 | Package registry (OSV) |
| Go:github.com/go-chi/chi/v5 | 5.3.0 | Package registry (OSV) |
| Go:github.com/go-chi/chi/v5/middleware | 5.3.0 | Package registry (OSV) |
| opensuse:cloudflared | 2026.8.2-bp160.1.1 · openSUSE:Leap 16.0 | Package registry (OSV) |
| opensuse:hauler | 2.0.3-1.1 · openSUSE:Tumbleweed | Package registry (OSV) |
| opensuse:trivy | 0.74.0-1.1 · openSUSE:Tumbleweed | Package registry (OSV) |
| opensuse:v2ray-core | 5.53.0-1.1 · openSUSE:Tumbleweed | Package registry (OSV) |
| opensuse:warewulf4 | 4.7.1-1.1 · openSUSE:Tumbleweed | Package registry (OSV) |
| red hat:cosign | 0:3.1.3-0.1.hum1 · Red Hat:hummingbird:1 | Package registry (OSV) |
| red hat:spire1.14 | 0:1.14.7-0.4.hum1 · Red Hat:hummingbird:1 | Package registry (OSV) |
| red hat:spire1.14-agent | 0:1.14.7-0.4.hum1 · Red Hat:hummingbird:1 | Package registry (OSV) |
| red hat:spire1.14-oidc-discovery-provider | 0:1.14.7-0.4.hum1 · Red Hat:hummingbird:1 | Package registry (OSV) |
| red hat:spire1.14-server | 0:1.14.7-0.4.hum1 · Red Hat:hummingbird:1 | Package registry (OSV) |
| red hat:spire1.15 | 0:1.15.2-0.4.hum1 · Red Hat:hummingbird:1 | Package registry (OSV) |
| red hat:spire1.15-agent | 0:1.15.2-0.4.hum1 · Red Hat:hummingbird:1 | Package registry (OSV) |
| red hat:spire1.15-oidc-discovery-provider | 0:1.15.2-0.4.hum1 · Red Hat:hummingbird:1 | Package registry (OSV) |
| red hat:spire1.15-server | 0:1.15.2-0.4.hum1 · Red Hat:hummingbird:1 | Package registry (OSV) |
Exploit status
No known public exploit
No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.
Research context
For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.
Timeline
From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.
No dated events beyond publication.
FIRST EPSS daily score; only changes of 0.01 or more are recorded (step chart).
Credits
All researchersFinders, reporters and analysts named in the CNA record. Click a name for that researcher’s other records.
- convtoreporter
Not on record for this CVE: patch commit or PR link · variant or chain candidate · public bounty program.
Technical details
Attack conditions
- Anyone who can reach it over the internet can trigger it.
- No account or password is required.
- No user action is required.
- No special conditions are required; it is repeatable.
If successful
- Confidentiality
- Integrity
- Availability
- Attack vector
- Network
- Attack complexity
- Low
- Privileges required
- None
- User interaction
- None
- Scope
- X
Weakness class (CWE)
CWE-345 · Insufficient Verification of Data AuthenticityCVSS vector
CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:L/VI:L/VA:N/SC:N/SI:N/SA:N/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X
nvd-secondary
Attack context
MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.
Attack patterns (CAPEC)
- JSON Hijacking (aka JavaScript Hijacking)CAPEC-111likelihood: High · High
- Cache PoisoningCAPEC-141likelihood: High · High
- DNS Cache PoisoningCAPEC-142likelihood: High · High
- Content SpoofingCAPEC-148likelihood: Medium · Medium
- Spoofing of UDDI/ebXML MessagesCAPEC-218Medium
- Application API Message Manipulation via Man-in-the-MiddleCAPEC-384Low
- Transaction or Event Tampering via Application API ManipulationCAPEC-385Medium
- Application API Navigation RemappingCAPEC-386Medium
Change log (1)
- Fix✗ → ✓
For records you follow, these changes also arrive as notifications. →
References
Show all references (1 more)Show less
Vendor advisories and official records. Exploit/PoC links are deliberately left out.