# CVE-2026-122132: go-chi chi 5.2.2 through 5.5.0 Open Redirect via RedirectSlashes Middleware


- **Severity:** Medium 5.1 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:A/VC:L/VI:L/VA:N/SC:N/SI:N/SA:N`)
- **Exploited in the wild:** Not known
- **Fix available:** Yes
- **Published:** 4 Nov 2026
- **Updated:** 5 Nov 2026
- **Also known as:** DEBIAN-CVE-2026-122132, GHSA-27h9-x5w9-37mx, UBUNTU-CVE-2026-122132

## What is CVE-2026-122132?

CVE-2026-122132 is a medium-severity vulnerability in go-chi chi, published on 4 Nov 2026. 

### Official description

go-chi chi 5.2.2 through 5.5.0 contains an open redirect vulnerability in the RedirectSlashes middleware that allows attackers to redirect victims to external hosts by embedding tab characters in request paths. Attackers can craft links with a URL-encoded tab, which browsers strip from the 301 Location header and resolve as a protocol-relative URL, bypassing the fix for CVE-2025-69725.

Weakness: CWE-601 (URL Redirection to Untrusted Site)

## Which versions are affected by CVE-2026-122132?


## How do I fix CVE-2026-122132?

Upgrade to a fixed version.

## Is CVE-2026-122132 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-122132 exists.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-122132 and fix it if it is affected.

What it is: CVE-2026-122132 is a medium-severity vulnerability in go-chi chi, published on 4 Nov 2026. 
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-122132 exists.

Affected product: go-chi chi. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-122132/ (Markdown: https://insights.sbomify.com/CVE-2026-122132/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-122132
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-122132
- OSV: https://osv.dev/vulnerability/CVE-2026-122132

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-122132/
Summaries are generated and may contain mistakes; the official description above is the record.