CVE-2026-63502: high-severity vulnerability in yeti-platform yeti
Yeti: Path traversal in ExportTask name allows authenticated arbitrary file read and write
Published
E-mail alert when it lands in KEV, gets a public PoC or its score goes up.
21Vexday Risk Score
No sign of exploitation. No public exploitation artifact known so far.
ssvc Trackcvss 8.3epss 0.4%
Yeti bridges the gap between CTI and DFIR practitioners by providing a Forensics Intelligence platform and pipeline. Prior to 2.5.1, YETI derives ExportTask.file_name from the user-controlled task name and passes it to core/clients/file_storage/classes/local_storage.py without sanitizing traversal sequences or enforcing path confinement. A low-privileged authenticated user using the default local storage backend can call POST /api/v2/tasks/export/new with a traversal name and use ExportTask.file_contents through GET /api/v2/tasks/export/{export_id}/content to read files accessible to the YETI service account. Running ExportTask.run() can also write attacker-controlled export output to an attacker-selected writable path. The impact depends on the service account's filesystem permissions, and universal code execution is not established. This issue is fixed in version 2.5.1.
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:L
Affected products
yeti-platform · yetiRelated CVEs — yeti-platform yeti
In the same product, most dangerous first.
CVE-2024-45412MEDIUMYeti affected by a Potential Denial of Service due to the One Milion Unicode characters attackEPSS 0.8%CVE-2026-92783HIGHYeti through 2.11.0 Missing Authorization on RBAC Relationship DeletionEPSS 0.5%CVE-2026-63482HIGHYeti: Unauthenticated Access to Full Audit Timeline Discloses All Threat Intelligence DataEPSS 0.4%CVE-2026-63500HIGHYeti: Path traversal in DFIQ uuid allows authenticated arbitrary file write during archive exportEPSS 0.4%CVE-2026-63489HIGHYeti: Authenticated AQL injection via unvalidated search sorting and filter_aliases parametersEPSS 0.3%