CVE-2026-63482
Yeti bridges the gap between CTI and DFIR practitioners by …
Yeti bridges the gap between CTI and DFIR practitioners by providing a Forensics Intelligence platform and pipeline. Prior to 2.5.1, YETI registers the audit router without Depends(auth.get_current_active_user), and core/web/apiv2/audit.py does not perform a route-level authentication check for /api/v2/audit/timeline/{id}. An unauthenticated network attacker can use an empty, partial, or specific wildcard path to query TimelineLog records containing the actor, target_id, action, and details fields, including analyst usernames, object identifiers and values, and before-and-after object data. This exposes the operational history of threat-intelligence objects while other application routers require authentication. This issue is fixed in version 2.5.1.
What to do now
- Check your exposureFind out whether the affected software runs anywhere in your environment, including systems of suppliers.
- UpdateInstall the version in which the vendor fixed the vulnerability. The references lead to the advisory.
- Limit access until thenIf you cannot update at once, take the system off the internet or restrict who can reach it.
References
- github.com/yeti-platform/yeti/commit/692af02ffc05faabc8638b15a88765cb0e3f2503
- github.com/yeti-platform/yeti/pull/1276
- github.com/yeti-platform/yeti/releases/tag/2.5.1
- github.com/yeti-platform/yeti/security/advisories/GHSA-34r4-95hx-gxqr
- nvd.nist.gov/vuln/detail/CVE-2026-63482
- cve.org/CVERecord?id=CVE-2026-63482
Data: CVE list and the NVD. This product uses data from the NVD API but is not endorsed or certified by the NVD.