Yeti 通过提供取证情报平台及处理流程,弥合了威胁情报(CTI)与数字取证与事件响应(DFIR)从业者之间的鸿沟。在 2.5.1 版本之前, 会通过 接口接收来自 DFIQ YAML 文件的未经验证的 UUID;随后, 在 接口中将该存储值拼接到归档文件系统路径中。权限较低但已认证的用户可导入一个包含路径遍历序列的 UUID 的 DFIQ 对象,并触发归档导出,导致攻击者控制的内容(以 为后缀)被写入到预期的临时归档目录之外。该漏洞的影响范围受限于 YETI 服务账户具有写权限的路径,且独立的 DFIQ 归档导入
Although we use advanced large model technology, its output may still contain inaccurate or outdated information.Shenlong tries to ensure data accuracy, but please verify and judge based on the actual situation.
| Vendor | Product | Affected Versions | CPE | Subscribe |
|---|---|---|---|---|
| yeti-platform | yeti | <= 2.5.0 | - |
|
| # | POC Description | Source Link | Shenlong Link |
|---|
No public POC found.
Login to generate AI POC| CVE-2026-63502 | 8.3 HIGH | Yeti: Path traversal in ExportTask name allows authenticated arbitrary file read and write |
| CVE-2026-63489 | 7.6 HIGH | Yeti: Authenticated AQL injection via unvalidated search sorting and filter_aliases parame |
| CVE-2026-63482 | 7.5 HIGH | Yeti: Unauthenticated Access to Full Audit Timeline Discloses All Threat Intelligence Data |