PoC Monitor
← All CVEs
CVE-2026-63502published 3 Nov 2026 19:36 UTCData: JSON · API

Yeti

Yeti: Path traversal in ExportTask name allows authenticated arbitrary file read and write

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.

First public PoC None yetno public PoC found
Public PoCs00 on GitHub
CVSS8.3high · scored by CNA · CWE-22
CISA KEV Not listednot known exploited

Affected versions and mitigation

From the CVE record and the vendor's references.

Affected

yeti-platform yeti
  • <= 2.5.0

Mitigation

The record names no fix. Check the vendor advisory below.

References

1 more

Timeline

Days relative to CVE publication
-2t=0+2+4+6+8CVE published3 Nov 2026 · t = 0

No public PoC found yet; not in CISA KEV.

PoC repositories

Found on GitHub.

No PoC repositories found yet.