Charmbracelet Wish 2.0.5 Path Traversal via git Middleware
- Exploited
- No known exploitation
- Fix
- Fixed in 2.0.5
- Who is exposed
- Specific setups only
Do first: Check whether your setup matches what the bug needs. Affected when wish is before 2.0.5 The git middleware (charm.land/wish/v2) is in use
- Last modified
- A 0-100 score for how much a CVE matters across the industry: exploitation, exposure, how widely the software is used, severity and whether a fix exists.What do these mean? →
- 18/100 · provisional
- How many real-world setups can hit the bug, from the vendor's advisory and CISA data. It does not know your setup.What do these mean? →
- Specific setups only
- Whether working attack code is public (Exploit-DB, Metasploit, Nuclei or GitHub). Public code makes attacks easier.What do these mean? →
- None on Exploit-DB, Metasploit or GitHub
- Exploitation: none
- Automatable: no
- Technical impact: total
Summary
Charmbracelet wish before 2.0.5 contains a path traversal vulnerability in the git middleware (charm.land/wish/v2) that allows authenticated SSH users to escape the configured repository directory by supplying crafted repo paths that bypass a flawed forward-slash-count containment check in git.Middleware(). Attackers can use a single-depth path ../evil, or on Windows a payload ..\..\evil that defeats the slash-count guard entirely, to read or write arbitrary repositories outside the intended root via git-upload-pack, git-upload-archive, or git-receive-pack.
cve.now Index
- Exploitation0/40No signal
- Exposure8/25Specific setups only, reachable over the network
- Reach?/20Unknown. No tracked technology or package matched
- Severity9.6/10CVSS 8.6, total technical impact per CISA
- No patch0/5No signal
What would change the score
- Would score about 68 if added to CISA KEV
- Would score about 63 if CISA's SSVC rates exploitation active
- Would score about 25 if CISA's SSVC rates it automatable
What to do
Check whether your setup matches what the bug needs.
Affected when wish is before 2.0.5 The git middleware (charm.land/wish/v2) is in useUpgrade to a fixed version: 2.0.5.
Timeline
- CVE published
- First seen by cve.now
- CISA SSVC assessment
Exploitation: none · Automatable: no · Technical impact: total
- Record last updated
Affected versions
- charmbracelet wish
fixed in 2.0.5
Evidence 3
- Patch
- Repository
- Link
Corrections
None so far.
Something wrong on this page? Report an error. Every fix is listed here.
Questions about CVE-2026-53980
Is CVE-2026-53980 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
What does this mean?
The git middleware in Charmbracelet Wish, which serves Git over SSH, does not keep requests inside the intended repository root. An authenticated SSH user can reach repositories outside that root through git-upload-pack, git-upload-archive, or git-receive-pack, and read or write them.Source: vulncheck.com
Which versions are affected by CVE-2026-53980?
wish: before 2.0.5.Source: cve.now feed data
Am I affected, and how do I check?
Wish versions before 2.0.5 are affected, but only where the git middleware (charm.land/wish/v2) is in use. To check, look at the wish version in your go.mod file and see whether the git middleware is imported and configured in your server.Source: vulncheck.com
How do I fix CVE-2026-53980?
The facts give no fixed release that is confirmed for this issue, so the only version information available is that the affected range ends before 2.0.5. Check the Charmbracelet Wish project for the current fix status before relying on any upgrade target.Source: vulncheck.com