---
id: "CVE-2026-63500"
kind: "vulnerability"
aliases: ["CVE-2026-63500"]
title: "Yeti: crafted DFIQ UUID lets authenticated users write files outside archive"
severity: "high"
cvss: 7.1
epss: null
exploited: false
status: "open"
category: "package"
products: []
ecosystems: []
tags: ["package", "python", "self-hosted", "yeti"]
not_affected_if: ["no-dfiq-import", "version-2.5.1-or-later"]
published_at: "2026-11-03T20:18:16+00:00"
first_seen_at: "2026-11-03T20:49:23+00:00"
updated_at: "2026-11-03T20:50:22+00:00"
sources: [{"source": "nvd", "url": "https://nvd.nist.gov/vuln/detail/CVE-2026-63500", "first_seen_at": "2026-11-03T20:49:23+00:00"}]
---

# Yeti: crafted DFIQ UUID lets authenticated users write files outside archive

Yeti, a forensics intelligence platform, fails to validate a UUID in imported DFIQ YAML objects, so the UUID's path traversal sequences are used when exporting to the archive. A low-privileged logged-in user can write attacker-controlled .yaml content to arbitrary locations the Yeti service account can write to.

_Summary, check and fix written by a model from the sources; labelled as such._

## How to check

- Check the installed Yeti version; affected versions are those before `2.5.1`.
- Look for the `POST /api/v2/dfiq/from_yaml` and `POST /api/v2/dfiq/to_archive` endpoints in your deployment's API logs.

## Fix

- Upgrade Yeti to `2.5.1`.

## Timeline

- 2026-11-03T20:49:23+00:00 nvd https://nvd.nist.gov/vuln/detail/CVE-2026-63500

## Documents

- [advisory] Vendor advisory: github.com https://github.com/yeti-platform/yeti/security/advisories/GHSA-6xf2-8436-rgvf
- [fix] Patch: github.com https://github.com/yeti-platform/yeti/commit/8e36bd0000f98f625540e37eeb9f304c684e8394
- [fix] Release notes: github.com https://github.com/yeti-platform/yeti/releases/tag/2.5.1

## From the sources

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.

---

_Free to read at a human pace. An API with keys and an MCP server are in preparation; early access: hello@infrastack.ai_