Vulnerability · Published Nov 3, 2026 · Assigned by GitHub_M
CVE-2026-63489Yeti: Authenticated AQL injection via unvalidated search sorting and filter_aliases parameters
High 7.6
In plain English
A high-severity security flaw in yeti from yeti-platform. There are no confirmed reports of exploitation so far. The chance it is exploited in the next 30 days is estimated at 0.3% (higher than 17% of all known vulnerabilities).
Official description
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.
Affected products (as reported)
| Vendor | Product | Versions |
|---|---|---|
| yeti-platform | yeti | <= 2.5.0 |
Weakness: CWE-943 · Vector: CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:L/A:L
References
- https://github.com/yeti-platform/yeti/security/advisories/GHSA-vw33-fwfx-6m9p x_refsource_CONFIRM
- https://github.com/yeti-platform/yeti/pull/1277 x_refsource_MISC
- https://github.com/yeti-platform/yeti/commit/89d8b61cf97b0fb2d46c2f9ee8b7411444345fc6 x_refsource_MISC
- https://github.com/yeti-platform/yeti/releases/tag/2.5.1 x_refsource_MISC