---
id: "CVE-2026-63482"
kind: "vulnerability"
aliases: ["CVE-2026-63482"]
title: "Yeti: unauthenticated audit timeline endpoint leaks analyst activity records"
severity: "high"
cvss: 7.5
epss: null
exploited: false
status: "open"
category: "package"
products: []
ecosystems: []
tags: ["dfir", "package", "self-hosted", "threat-intelligence", "yeti"]
not_affected_if: ["not-network-reachable", "version-2.5.1-or-later"]
published_at: "2026-11-03T20:18:16+00:00"
first_seen_at: "2026-11-03T20:49:23+00:00"
updated_at: "2026-11-03T20:50:13+00:00"
sources: [{"source": "nvd", "url": "https://nvd.nist.gov/vuln/detail/CVE-2026-63482", "first_seen_at": "2026-11-03T20:49:23+00:00"}]
---

# Yeti: unauthenticated audit timeline endpoint leaks analyst activity records

Yeti is a threat-intelligence and forensics platform. Before version 2.5.1, its audit timeline API at /api/v2/audit/timeline/ was registered without an authentication check, so an unauthenticated network attacker can read audit records with analyst usernames, object identifiers and before-and-after object data.

_Summary, check and fix written by a model from the sources; labelled as such._

## How to check

- Check the installed Yeti version against `2.5.1`.
- Look for the audit router registration in `core/web/apiv2/audit.py` and confirm it lacks `Depends(auth.get_current_active_user)`.
- Request `/api/v2/audit/timeline/` without credentials and confirm whether it returns data.

## Fix

- Upgrade Yeti to `2.5.1`.

## Timeline

- 2026-11-03T20:49:23+00:00 nvd https://nvd.nist.gov/vuln/detail/CVE-2026-63482

## Documents

- [advisory] Vendor advisory: github.com https://github.com/yeti-platform/yeti/security/advisories/GHSA-34r4-95hx-gxqr
- [fix] Patch: github.com https://github.com/yeti-platform/yeti/commit/692af02ffc05faabc8638b15a88765cb0e3f2503
- [fix] Release notes: github.com https://github.com/yeti-platform/yeti/releases/tag/2.5.1

## From the sources

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.

---

_Free to read at a human pace. An API with keys and an MCP server are in preparation; early access: hello@infrastack.ai_