# CVE-2026-63500: Yeti: Path traversal in DFIQ uuid allows authenticated arbitrary file write during archive export

Status: published. Published: 2026-11-03. Updated: 2026-11-03.

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.

## Remediation

No remediation reported in collected sources

## Affected products and versions

- yeti-platform / yeti: <= 2.5.0 (affected). Source: CNA: GitHub_M

## Severity and prioritization

- CVSS 3.1: 7.1 (high); CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:H/A:L; source: CNA: GitHub_M

- CISA KEV: No listing in collected sources

- EPSS: Not available

- SSVC: Not available

- Weaknesses: CWE-22

## Exploit evidence

No exploit evidence in collected sources. This is not proof of no exploitation.

## References

- https://github.com/yeti-platform/yeti/security/advisories/GHSA-6xf2-8436-rgvf (CNA: GitHub_M; x_refsource_CONFIRM)

- https://github.com/yeti-platform/yeti/pull/1279 (CNA: GitHub_M; x_refsource_MISC)

- https://github.com/yeti-platform/yeti/commit/8e36bd0000f98f625540e37eeb9f304c684e8394 (CNA: GitHub_M; x_refsource_MISC)

- https://github.com/yeti-platform/yeti/releases/tag/2.5.1 (CNA: GitHub_M; x_refsource_MISC)

## Provenance

- CNA: GitHub_M: https://www.cve.org/CVERecord?id=CVE-2026-63500; retrieved 2026-11-03; source updated 2026-11-03

Revision: 69a2353892abd518cedb00509aff63cb68995bd592907391bb73efc49fcf370a

Canonical: https://y2.dev/cve/CVE-2026-63500

## Agent and API access

Public CVE pages, Markdown, and JSON are free to read without an account or API key.

- Public catalog: https://y2.dev/cve/index.json. Follow nextCursor with the same search, filters, sort, and limit (1–100). A null cursor marks the end.

- WebMCP: search_cve_disclosures, get_cve_disclosure, get_cve_page_markdown, get_y2_cve_access. Available in compatible browsers.

- Cyber API: https://api.y2.dev/api/v2/cyber/cves and https://api.y2.dev/api/v2/cyber/cves/{cveId}.

- Y2 Pro or Elite: create a workspace API key with the intel:cyber scope and send Authorization: Bearer <Y2_API_KEY>. Setup: https://y2.dev/docs/api/create-key.

- x402: Pay per request without an account or API key. Omit Authorization, read the HTTP 402 PAYMENT-REQUIRED challenge, validate its current requirements, and retry with PAYMENT-SIGNATURE through an authorized payment client. These browser tools never make payments. Guide: https://y2.dev/docs/api/x402.

- OpenAPI: https://y2.dev/api/openapi.yaml. Agent access metadata: https://y2.dev/cve/agent.json.

Collected public records only. Check source status for coverage and freshness.