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.
Published: 2026-11-03
Score: 7.6 High
EPSS: n/a
KEV: No
Impact: Database injection that can reveal internal data and exhaust resources
Action: Immediate Patch
AI Analysis

Impact

The vulnerability is an AQL injection in YETI’s search endpoints that lets an authenticated low-privileged user insert arbitrary AQL sub-expressions via the sort and filter_aliases parameters. The attacker can trigger error messages, read data from internal collections such as users, modify the logic of searches, enumerate schema details, and consume excessive database resources. This capability exposes sensitive data and can degrade availability, but the injection does not enable arbitrary write operations.

Affected Systems

Yeti Platform’s Yeti product is affected in all releases 2.5.0 and earlier. No fixed version is available as of this review.

Risk and Exploitability

With a CVSS v3.1 score of 7.6 the vulnerability is considered high severity. The EPSS score is not available, and it is not listed in the CISA KEV catalog. The attack requires valid authenticated credentials and flows through the listed search endpoints, enabling the attacker to trigger the injection. Because the attack uses only reading and filtering, a low-privileged user can still exploit the flaw, which increases its risk.

Generated by OpenCVE AI on November 3, 2026 at 20:51 UTC.

Remediation

No solution or workaround provided in the CVE record.

OpenCVE Recommended Actions

  • Manually apply the changes from the upstream PR #1277 (commit 89d8b61cf97…) which neutralizes the injection points until an official release is available.
  • Limit user privileges or disable filter_aliases and sorting features for low-privileged accounts to reduce exposure.
  • Continuously monitor the Yeti vendor for a formal security patch; once available, upgrade.

Generated by OpenCVE AI on November 3, 2026 at 20:51 UTC.

Tracking

Sign in to view the affected projects.

Advisories

No advisories yet.

History

Tue, 03 Nov 2026 21:30:00 +0000

Type Values Removed Values Added
First Time appeared Yeti-platform
Yeti-platform yeti
Vendors & Products Yeti-platform
Yeti-platform yeti

Tue, 03 Nov 2026 19:45:00 +0000

Type Values Removed Values Added
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.
Title Yeti: Authenticated AQL injection via unvalidated search sorting and filter_aliases parameters
Weaknesses CWE-943
References
Metrics cvssV3_1

{'score': 7.6, 'vector': 'CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:L/A:L'}


Subscriptions

Yeti-platform Yeti
cve-icon MITRE

Status: PUBLISHED

Assigner: GitHub_M

Published:

Updated: 2026-11-03T19:33:57.975Z

Reserved: 2026-07-16T21:49:52.068Z

Link: CVE-2026-63489

cve-icon Vulnrichment

No data.

cve-icon NVD

Status : Deferred

Published: 2026-11-03T20:18:16.590

Modified: 2026-11-03T20:18:16.737

Link: CVE-2026-63489

cve-icon Redhat

No data.

cve-icon OpenCVE Enrichment

Updated: 2026-11-03T21:15:03Z

Weaknesses
  • CWE-943

    Improper Neutralization of Special Elements in Data Query Logic