Skip to main content
← Vulnerabilities

go-chi chi 5.2.2 through 5.5.0 Open Redirect via RedirectSlashes Middleware

Written by anthropic/claude-haiku-5.5 from the sources below. Verify against them.

5.1MediumCNA
Exploited
No known exploitation
Fix
Fix or patch referenced
Who is exposed
Not reported

Do first: Apply the patch listed under Evidence.

12Pcve.now Index 12 of 100 · methodology v3 · provisional
  • Exploitation?/40Exploitation: unknown (data gap). No CISA SSVC exploitation rating yet
  • Exposure7/25Reachable over the network without a login · Data gap: No advisory context yet
  • Reach?/20Reach: unknown (data gap). No tracked technology or package matched
  • Severity5.1/10CVSS 5.1
  • No patch0/5No signal

What would change the score

  • Would score about 67 if added to CISA KEV
  • Would score about 62 if CISA's SSVC rates exploitation active
  • Would score about 27 if advisories confirm default setups are exposed

CVE-2026-122132 is not in CISA's Known Exploited Vulnerabilities (KEV) catalog. No public exploit code is tracked. It is rated CVSS 5.1 (medium) and affects chi; a fix or patch is referenced.

Published
Last modified
Published
Not listed in CISA KEV
12/100 · provisional
Fix
Fix or patch referenced
None on Exploit-DB, Metasploit or GitHub

Summary

The go-chi chi router's RedirectSlashes middleware, in versions 5.2.2 through 5.5.0, can be abused to send users to an external site. An attacker can remotely, without logging in, craft a link that includes an encoded tab character, which browsers strip so that the redirect goes to an attacker-chosen host, though the victim must be tricked into clicking it.

Read the original 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.

What to do

  • Apply the patch listed under Evidence.

Timeline

  1. CVE published
  2. First seen by cve.now

Affected versions

  • go-chi chi

    From 5.2.2 · through 5.5.0

Evidence 5

  1. Advisory
  2. Patch
  3. Repository
  4. Repository
  5. Link

Corrections

None so far.

Something wrong on this page? Report an error. Every fix is listed here.

FAQ

Questions about CVE-2026-122132

Is CVE-2026-122132 being exploited?

It is not in CISA's Known Exploited Vulnerabilities catalog, and CISA's SSVC assessment does not mark exploitation as active. That does not mean it has not been attacked: vendors and researchers can report attacks before CISA lists them. No public exploit code is tracked.Source: cve.now feed data

Which versions are affected by CVE-2026-122132?

chi: from 5.2.2 through 5.5.0.Source: cve.now feed data