5 matches found
CVE-2026-63500
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/fromyaml, and core/web/apiv2/dfiq.py later interpolates that stored value...
CVE-2026-63500
The Yeti forensics intelligence platform (prior to version 2.5.1 ) is vulnerable to a path traversal flaw in its DFIQ processing. The application fails to validate a uuid provided via POST /api/v2/dfiq/from_yaml in core/schemas/dfiq.py. This unvalidated value is later interpolated into a filesyst...
EUVD-2026-116268
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/fromyaml, and core/web/apiv2/dfiq.py later interpolates that stored value...
CVE-2026-63500 Yeti: Path traversal in DFIQ uuid allows authenticated arbitrary file write during archive export
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/fromyaml, and core/web/apiv2/dfiq.py later interpolates that stored value...
CVE-2026-63500: yeti-platform yeti: Yeti bridges the gap between CTI and DFIR practitioners by providing a Forensics Intelligence platform and pipeline
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/fromyaml, and core/web/apiv2/dfiq.py later interpolates that stored value...