CVE-2026-63502: yeti · Path Traversal
Affects yetiSource CVE Database V5
Not known to be exploited · CVSS 8.3 High · fixed in 2.5.1 : patch yeti soon.
Data as of 3 Nov 2026, 20:13 UTC
Thin evidence
One scorer or none| CNA (GitHub_M) | CVSS 3.1 | 8.3 |
|---|
- Patch
- Available – fixed in 2.5.1
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:LExploitation evidence
Disclosed: evidence found.
CVE published 3 Nov 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponized: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by 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 3 Nov 2026.
What to do
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| yeti-platformyeti | Affected
| Fixed in– |
AI-suggested
Upgrade Yeti-platform to version 2.5.1 or later, where this path traversal vulnerability is fixed. No other mitigation is indicated or required according to the available data.
Description
Yeti-platform versions up to 2.5.0 contain a path traversal vulnerability in the ExportTask functionality. A low-privileged authenticated user can exploit this by submitting a crafted task name that includes traversal sequences, allowing unauthorized reading of files accessible to the Yeti service account and writing export output to attacker-controlled writable paths. The vulnerability is fixed in version 2.5.1.
References
- github.com/yeti-platform/yeti/security/advisories/GHSA-4q3w-w2g5-8wqq (opens in a new tab)
- github.com/yeti-platform/yeti/pull/1280 (opens in a new tab)
- github.com/yeti-platform/yeti/commit/bfd7c2424dc05dea2d46b5b106b5071f959d5d5a (opens in a new tab)
- github.com/yeti-platform/yeti/releases/tag/2.5.1 (opens in a new tab)