Vulnerability in golang-github-go-chi-chi (UBUNTU-CVE-2026-72816)

Summary

Vulnerability in golang-github-go-chi-chi (UBUNTU-CVE-2026-72816). Risk of unauthorized operations or information disclosure. Mitigation: upgrade to 5.3.0 or later.

Original description

The description as published by the source.

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.

Source: OSV.dev (Open Source Vulnerabilities) OSV

Auto-generated summary

Assembled by SecPulse from the source data (CVSS, CWE, affected versions) using templates — no AI involved. Check the original description and references below for exact details.

A vulnerability tracked as UBUNTU-CVE-2026-72816 has been found in golang-github-go-chi-chi.
Risk of unauthorized operations or information disclosure.
What to do: upgrade golang-github-go-chi-chi to 5.3.0 or later.
If unsure, ask your IT team or search "golang-github-go-chi-chi UBUNTU-CVE-2026-72816" on the vendor's site.

UBUNTU-CVE-2026-72816 (golang-github-go-chi-chi)
Attack vector: remote (network-reachable) / unauthenticated / no user interaction
Patched: 5.3.0 — apply immediately
Plan: 1) Audit SBOM/dependencies, 2) Stage→prod upgrade, 3) Add WAF/proxy monitoring on affected endpoints, 4) Hunt IOCs in logs.
Refs: see the GHSA / vendor advisory / patched release linked on this page.

❓ What is the problem

A vulnerability (unclassified) exists in golang-github-go-chi-chi.

📍 Affected scope

Check the vendor advisory for the affected versions of golang-github-go-chi-chi.

🔥 Severity

Severity: ?. Risk of unauthorized operations or information disclosure.

🔧 How to fix

Update to 5.3.0.

🛡️ Workaround

Until the patch is applied: disable the affected feature, apply WAF rules, or restrict access via network ACLs.

🔍 Detection

Search webserver/proxy logs for unusual request patterns matching this CVE's known IOCs. Run grep -r 'golang-github-go-chi-chi' . against your dependency files (package-lock.json, requirements.txt, go.sum) to find affected services.

Response actions

Concrete steps and command examples for SOC/SRE teams to execute in order

1
Identify exposure identify
```
grep -r 'golang-github-go-chi-chi' . | grep -v node_modules
```
リポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で golang-github-go-chi-chi を grep し、稼働しているサービス・バージョンを把握する。
2
Apply patch patch
```
Upgrade golang-github-go-chi-chi to 5.3.0
```
ステージング環境で 5.3.0 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスを含めること。
3
Post-deployment verification verify
```
Confirm patched version is live in production
```
パッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番ではアクセスログ・WAF でアラート再発が無いか継続監視。

Affected packages

Ubuntu:22.04:LTS golang-github-go-chi-chi

[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}]

Ubuntu:24.04:LTS golang-github-go-chi-chi

[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}]

Ubuntu:26.04:LTS golang-github-go-chi-chi

[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}]

References

report ubuntu.com
report cve.org
report github.com
report vulncheck.com