CVE-2026-63489 PUBLISHED

Yeti: Authenticated AQL injection via unvalidated search sorting and filter_aliases parameters

Assigner: GitHub_M
Reserved: 16.07.2026 Published: 03.11.2026 Updated: 03.11.2026

Yeti bridges the gap between CTI and DFIR practitioners by providing a Forensics Intelligence platform and pipeline. In version 2.5.0 and earlier, YETI directly interpolates user-controlled sorting fields and filter_aliases attribute paths into ArangoDB AQL identifier and expression positions in core/database_arango.py. A low-privileged authenticated user can send crafted values to POST /api/v2/observables/search, POST /api/v2/entities/search, POST /api/v2/indicators/search, POST /api/v2/dfiq/search, POST /api/v2/search/, or POST /api/v2/graph/search, causing attacker-controlled AQL subexpressions to be parsed and evaluated. This can provide an error oracle, evaluate expressions against internal collections such as users, alter intended search logic, enumerate schema information, and consume excessive database resources. The verified injection points are read and search contexts, so arbitrary database writes are not established. No fixed version is available as of this review.

Metrics

CVSS Vector: CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:L/A:L
CVSS Score: 7.6

Product Status

Vendor yeti-platform
Product yeti
Versions
  • Version <= 2.5.0 is affected

References

Problem Types

  • CWE-943: Improper Neutralization of Special Elements in Data Query Logic CWE