Skip to main content
VulnerabilityPublished Updated

CVE-2026-72816: chi · Authentication Bypass by Spoofing

Affects chiSource CVE Database V5

0
Compare

Not known to be exploited · CVSS 6.9 Medium : upgrade to 5.3.0 when convenient.

Data as of 12 Nov 2026, 23:24 UTC

CVSS 4.0 base score
6.9Medium
How severe the flaw is on the 0–10 CVSS scale.
EPSS
0.3% chance of exploitation in 30 days – higher than 23% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
Patch
Available – fixed in 5.3.0
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

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 14 Aug 2026

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponized: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 13 Nov 2026.

What to do

Upgrade chi to 5.3.0.

Affected software

ProductAffectedFixed in
go-chichiAffected
  • <5.3.0
Fixed in
  • 5.3.0
Gogithub.com/go-chi/chipkg:golang/github.com/go-chi/chiOther threatsAffected
  • <=5.2.1
Fixed in–

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

AI-suggested

Upgrade to go-chi/chi version 5.3.0 or later, where this vulnerability is fixed. Until then, avoid relying solely on the RealIP middleware for IP-based security controls or implement additional verification of trusted proxies. Patch status is confirmed fixed in 5.3.0.

Description

go-chi/chi through 5.2.1 contains an IP spoofing vulnerability in the RealIP middleware (middleware/realip.go). The realIP() function reads client-controlled headers (True-Client-IP, X-Real-IP, and X-Forwarded-For) and overwrites r.RemoteAddr without verifying that the request originated from a trusted proxy. Attackers can supply arbitrary IP addresses in these headers to bypass IP-based access controls, evade rate limiting and geo-IP restrictions, and pollute audit logs. Fixed in 5.3.0.

References

Community reviews

Loading reviews…