NetSight
high8.3

CVE-2026-63502

Yeti bridges the gap between CTI and DFIR practitioners by providing a Forensics Intelligence platform and pipeline.

Impact

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.

An attacker can exploit this over the network, with a regular user account, without any action by a user. If it succeeds: high risk of data being read, high risk of data or systems being changed, low risk of outages.

Affected products · Yeti-platform

ProductAffected versions
Yeti
Versions <= 2.5.0, ≤ 2.5.0

Weakness classification

References