Auth bypass in Yeti-Platform Yeti
CVE-2026-63482
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.
Vulnerability class: Broken Authentication
Published · last modified .
CVSS v3 metric
CVSS v3 base score 7.5 (High). Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N.
EPSS exploit prediction
No EPSS score from FIRST.org yet. New CVEs usually get one within a few days; no score means no signal yet, not low risk. How EPSS works.
Affected products
- Yeti-Platform Yeti — versions < 2.5.1
Weakness classification (CWE)
References
Frequently asked questions
- What is CVE-2026-63482?
- CVE-2026-63482 is a high-severity vulnerability in Yeti-Platform Yeti, classified under Missing Authentication for Critical Function. CVSS score: 7.5/10. Published 2026-11-03.
- How severe is CVE-2026-63482?
- High severity. CVSS v3 base score is 7.5 out of 10.