CVE-2026-63489: Yeti: Authenticated AQL injection via unvalidated search sorting and filter_aliases parameters

Published Nov 3, 2026

Updated

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 filteraliases attribute paths into ArangoDB AQL identifier and expression positions in core/databasearango.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.

Event History

Nov 3, 2026

CVE Published

via MITRE·07:33 PM

Data Sourced

via MITRE·07:33 PM

DescriptionSeverityWeakness

Data Sourced

via NVD·08:18 PM

DescriptionSeverityWeakness

Frequently Asked Questions

Who can exploit this issue?

An attacker needs a low-privileged authenticated YETI account and network access to one of the affected search API endpoints. No user interaction is required.

Which deployments are affected?

YETI version 2.5.0 and earlier are affected. The vulnerable behavior is in core/database_arango.py and is reachable through the observable, entity, indicator, DFIQ, general, and graph search POST endpoints.

What can an attacker do through the injection?

An attacker can cause AQL subexpressions to be parsed in search requests, potentially using errors as an oracle, querying internal collections such as users, changing intended search logic, enumerating schema information, or consuming database resources. The verified injection points are read and search contexts; arbitrary database writes have not been established.

What should be done if a fixed version is not available?

No fixed version was available at the time of review. Limit access to the affected search APIs to trusted users, restrict low-privileged account creation and permissions, and monitor search requests for unusual sorting fields or filter_aliases values and for abnormal database resource consumption.

CVE-2026-63489: Yeti: Authenticated AQL injection via unvalidated search sorting and filter_aliases parameters

Event History

Frequently Asked Questions

Who can exploit this issue?

Which deployments are affected?

What can an attacker do through the injection?

What should be done if a fixed version is not available?

Company

Resources

Contact

Frequently Asked Questions

Who can exploit this issue?

Which deployments are affected?

What can an attacker do through the injection?

What should be done if a fixed version is not available?