Skip to main content
VulnerabilityPublished

CVE-2026-53980: charmbracelet wish · Path Traversal

Affects charmbracelet wishSource CVE Database V5

0
Compare

Not known to be exploited · CVSS 8.6 High : upgrade to 2.0.5 soon.

Data as of 6 Nov 2026, 15:24 UTC

CVSS 4.0 base score
8.6High
How severe the flaw is on the 0–10 CVSS scale.

Thin evidence

One scorer or none
CVSS scores by source
CNA (VulnCheck)CVSS 4.08.6
CNA (VulnCheck)CVSS 3.18.1
Patch
Available – fixed in 2.0.5
CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:H/VI:H/VA:N/SC:N/SI:N/SA:N

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 6 Nov 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 6 Nov 2026.

What to do

Upgrade charmbracelet wish to 2.0.5.

Affected software

ProductAffectedFixed in
charmbraceletwishAffected
  • <2.0.5
Fixed in
  • 2.0.5
GitHubwishpkg:github/wishOther threatsAffected
  • <2.0.5
Fixed in
  • 2.0.5

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

AI-suggested

A fixed version 2.0.5 of charmbracelet wish is available that addresses this path traversal vulnerability. Users should upgrade to version 2.0.5 or later to remediate this issue. No additional mitigation steps are indicated beyond applying the official fix.

Description

CVE-2026-53980 is a path traversal vulnerability in charmbracelet wish before version 2.0.5. It affects the git middleware component, allowing authenticated SSH users to escape the intended repository directory by supplying crafted repository paths. The flaw is due to a bypass of a forward-slash-count containment check, enabling attackers to read or write arbitrary repositories outside the configured root directory.

References

Community reviews

Loading reviews…