PoC Monitor
← All CVEs
CVE-2026-63489published 3 Nov 2026 19:33 UTCData: JSON · API

Yeti

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

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.

First public PoC None yetno public PoC found
Public PoCs00 on GitHub
CVSS7.6high · scored by CNA · CWE-943
CISA KEV Not listednot known exploited

Affected versions and mitigation

From the CVE record and the vendor's references.

Affected

yeti-platform yeti
  • <= 2.5.0

Mitigation

The record names no fix. Check the vendor advisory below.

References

1 more

Timeline

Days relative to CVE publication
-2t=0+2+4+6+8CVE published3 Nov 2026 · t = 0

No public PoC found yet; not in CISA KEV.

PoC repositories

Found on GitHub.

No PoC repositories found yet.