Yeti: Authenticated AQL injection via unvalidated search sorting and filter_aliases parameters
Affects Yeti 2.5.0 and earlier, and only for users with a valid authenticated account. No vendor severity is listed, and the checked facts name no fixed version.
Written by anthropic/claude-haiku-5.5 from the sources below. Verify against them.
- Exploited
- No known exploitation
- Fix
- No fix listed
- Who is exposed
- Specific setups only
Do first: Check whether your setup matches what the bug needs. The attacker has a valid authenticated account.
- Exploitation?/40Exploitation: unknown (data gap). No CISA SSVC exploitation rating yet
- Exposure8/25Specific setups only, reachable over the network
- Reach?/20Reach: unknown (data gap). No tracked technology or package matched
- Severity7.6/10CVSS 7.6
- No patch5/5No patch listed yet
What would change the score
- Would score about 71 if added to CISA KEV
- Would score about 66 if CISA's SSVC rates exploitation active
- Would score about 28 if CISA's SSVC rates it automatable
CVE-2026-63489 is not in CISA's Known Exploited Vulnerabilities (KEV) catalog. No public exploit code is tracked. It is rated CVSS 7.6 (high) and affects yeti; no fixed version is listed yet.
- Last modified
- Where the record stands: published, rejected by its publisher, or superseded by another id.What do these mean? →
- Published
- Whether CISA lists it in its Known Exploited Vulnerabilities catalog: proof that attackers are using it.What do these mean? →
- Not listed in CISA KEV
- A 0-100 score for how much a CVE matters across the industry: exploitation, exposure, how widely the software is used, severity and whether a fix exists.What do these mean? →
- 21/100 · provisional
- How many real-world setups can hit the bug, from the vendor's advisory and CISA data. It does not know your setup.What do these mean? →
- Specific setups only
- Whether working attack code is public (Exploit-DB, Metasploit, Nuclei or GitHub). Public code makes attacks easier.What do these mean? →
- None on Exploit-DB, Metasploit or GitHub
Summary
Yeti, a Forensics Intelligence platform for CTI and DFIR practitioners, is affected by an injection flaw in its search API endpoints, which lets a logged-in user with low privileges manipulate database queries. This could expose error details, read data from internal database collections such as user records, alter search results, reveal database structure, and overload the database, though arbitrary data writes have not been demonstrated.
Read the original 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.
What to do
Check whether your setup matches what the bug needs.
The attacker has a valid authenticated account.
Timeline
- CVE published
- First seen by cve.now
Affected versions
- yeti-platform yeti
through 2.5.0
Evidence 4
- Advisory
- Repository
- Repository
- Repository
Corrections
None so far.
Something wrong on this page? Report an error. Every fix is listed here.
Questions about CVE-2026-63489
Is CVE-2026-63489 being exploited?
It is not in CISA's Known Exploited Vulnerabilities catalog, and CISA's SSVC assessment does not mark exploitation as active. That does not mean it has not been attacked: vendors and researchers can report attacks before CISA lists them. No public exploit code is tracked.Source: cve.now feed data
What does this mean?
An authenticated low-privileged user can inject AQL expressions through the unvalidated search sorting and filter_aliases parameters. This can allow reads across collections, including the users collection, error-based probing, schema enumeration, altered search logic, and possibly denial of service.Source: github.com
Which versions are affected by CVE-2026-63489?
yeti: through 2.5.0.Source: cve.now feed data
Am I affected, and how do I check?
Yeti versions up to and including 2.5.0 are listed as affected. The attacker needs a valid authenticated account, so check the installed Yeti version against that range and review which accounts can log in.Source: github.com
How do I fix CVE-2026-63489?
The checked facts do not name a fixed version, so no upgrade target can be given. Check the vendor's advisory for a fixed release and upgrade to it when it is available.Source: github.com