CVE-2026-63500

published 3 Nov 2026 · updated 3 Nov 2026

Yeti: Path traversal in DFIQ uuid allows authenticated arbitrary file write during archive export

7.1HighCVSS 7.1EPSS 0%

No exploitation in the wild has been reported. EPSS puts the chance of exploitation in the next 30 days at 0%. No fixed version is recorded.

Yeti bridges the gap between CTI and DFIR practitioners by providing a Forensics Intelligence platform and pipeline. Prior to 2.5.1, core/schemas/dfiq.py accepts an unvalidated uuid from DFIQ YAML through POST /api/v2/dfiq/from_yaml, and core/web/apiv2/dfiq.py later interpolates that stored value into an archive filesystem path in POST /api/v2/dfiq/to_archive. A low-privileged authenticated user can import a DFIQ object whose UUID contains traversal sequences and trigger archive export, causing attacker-controlled content with a .yaml suffix to be written outside the intended temporary archive directory. The impact is limited by paths writable by the YETI service account, and the separate DFIQ archive-import zip-slip candidate is not part of this vulnerability. This issue is fixed in version 2.5.1.

Affected

Vendors, products and packages with version ranges

VendorProductVersionsFixed
yeti-platform<=2.5.0

Timeline

Every event on this vulnerability

Embed

A live severity badge for an advisory, README or ticket

CVE-2026-63500 severity on Zeptric[![CVE-2026-63500](https://zeptric.io/badge/cve/CVE-2026-63500.svg)](https://zeptric.io/cve/CVE-2026-63500)