CVE-2026-63500
HighCVSS 7.1Summary
In Yeti prior to 2.5.1, the uuid from DFIQ YAML is not validated on import via POST /api/v2/dfiq/from_yaml and is later interpolated 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, writing attacker-controlled content with a .yaml suffix outside the intended temporary archive directory.
Risk Assessment
A low-privileged authenticated user can write files to locations writable by the YETI service account, potentially overwriting or injecting content in unexpected places. Impact is bounded by the service account's write permissions.
Recommendation
Upgrade Yeti to version 2.5.1 or later. Until then, restrict access to DFIQ import and export endpoints and run the YETI service with minimal write privileges.
Other vulnerabilities in Yeti
See all- CVE-2026-63502High
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 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 read files accessible to the YETI service account.
- CVE-2026-63489High
In Yeti 2.5.0 and earlier, user-controlled sorting fields and filter_aliases attribute paths are interpolated into ArangoDB AQL identifier and expression positions in core/database_arango.py. A low-privileged authenticated user can send crafted values to search endpoints, causing attacker-controlled AQL subexpressions to be parsed and evaluated.
- CVE-2026-63482High
In Yeti prior to 2.5.1, the audit router is registered without Depends(auth.get_current_active_user), and core/web/apiv2/audit.py performs no route-level authentication check for /api/v2/audit/timeline/{id}. An unauthenticated network attacker can query TimelineLog records containing analyst usernames, object identifiers and values, and before-and-after object data.
- CVE-2026-92783High
Yeti through 2.11.0 fails to validate caller permissions in the DELETE /api/v2/rbac/{id} endpoint, allowing users with read access to delete access control relationships. Attackers can revoke the owner's grant and permanently lock legitimate owners out of objects.
Original NVD description (English source)
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.
Vulnerability data from NVD (NIST) · CISA KEV · EPSS