Quick answers
- Is CVE-2026-63489 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-63489 being exploited in the wild.
- How severe is CVE-2026-63489?
- High severity, with a CVSS score of 7.6, published 3 November 2026.
- Which products and versions are affected?
- Yeti 2.5.0 and earlier.
- Is there a fix for CVE-2026-63489?
- Yes: fixed in Fixed in commit 89d8b61 (merged July 1, 2026); consult repository for next release tag. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
- How is CVE-2026-63489 attacked?
- It is attacked over the network, in a web application.
- Am I affected by CVE-2026-63489?
- Check whether you run Yeti at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.
How to fix
- Fixed in: Fixed in commit 89d8b61 (merged July 1, 2026); consult repository for next release tag
Technical details
The vulnerability is an AQL injection in core/database_arango.py where user-controlled sorting field names and filter_aliases attribute paths are interpolated directly into AQL query strings without validation. An authenticated attacker can send crafted values to the search endpoints to inject AQL subexpressions that bypass intended access controls, exposing cross-collection data such as the users collection. The fix validates field and alias names against a regex pattern [a-zA-Z0-9_.] before query construction.
Affected products
- Yeti Yeti 2.5.0 and earlier
Timeline
- 2026-11-03: disclosed
- 2026-07-01: patched