CVE-2026-63482: Yeti: Unauthenticated Access to Full Audit Timeline Discloses All Threat Intelligence Data

What it is

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.

Description quoted from the CVE record (assigned by GitHub_M, published 2026-11-03).

Weakness: CWE-306: Missing Authentication for Critical Function

How it can be exploited

Exploitable over the network with low attack complexity needing no privileges and no user interaction. Impact: confidentiality high, integrity none, availability none. CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N

CISA assessment (SSVC): CISA has no evidence of exploitation. Automatable: yes. Technical impact: partial.

Public exploit evidence (Exploit Observer)

Exploit Observer found 5 code repositories naming this CVE.

Code repositories that name a CVE are often scanners, copies or fakes, and some are malware. Read the code before running anything.

See all 6 references on Exploit Observer

Live scores

EPSS

0.004
low predicted chance of attack

VEDAS

0.985
strong exploit evidence

On CISA KEV

Not listed

Detection rule

Nuclei · Suricata

Who is affected

Version ranges exactly as the CVE record states them. “Before X” means X is the first fixed version.

How to fix it

No fixed version or vendor advisory is listed in the CVE record yet. Watch the vendor’s security page.

How to detect it

Nuclei template (active check)

Yeti - Unauthenticated Audit Timeline Disclosure

Yeti (Your Everyday Threat Intelligence) prior to 2.5.1 registers the audit router without `Depends(auth.get_current_active_user)`, so `core/web/apiv2/audit.py` does not enforce a route-level authentication check on `GET /api/v2/audit/timeline/{id}`. An unauthenticated network attacker requesting the endpoint with an empty id retrieves all TimelineLog records, disclosing analyst usernames, object identifiers and before/after object data. This template requests the timeline with an empty id. Fixed in version 2.5.1.

Name and description quoted from the template, written by VEDAS.

The template sends 1 request (GET /api/v2/audit/timeline/); it decides using dsl matchers. Severity in the template: high. Marked as not yet verified against a live vulnerable target.

Run it against a host you own or are authorised to test:

nuclei -u https://your-host -t CVE-2026-63482.yaml

id: CVE-2026-63482

info:
  name: "Yeti - Unauthenticated Audit Timeline Disclosure"
  author: vedas-arpsyndicate
  severity: high
  description: |
    Yeti (Your Everyday Threat Intelligence) prior to 2.5.1 registers the audit router without
    `Depends(auth.get_current_active_user)`, so `core/web/apiv2/audit.py` does not enforce a
    route-level authentication check on `GET /api/v2/audit/timeline/{id}`. An unauthenticated network
    attacker requesting the endpoint with an empty id retrieves all TimelineLog records, disclosing
    analyst usernames, object identifiers and before/after object data. This template requests the
    timeline with an empty id. Fixed in version 2.5.1.
  reference:
    - https://www.exploit.observer/?keyword=CVE-2026-63482&match=exact
    - https://subdomain.center/?engine=ammonites&keyword=yeti&match=exact
  classification:
    cve-id: CVE-2026-63482
    cwe-id: CWE-306
  metadata:
    verified: false
    max-request: 1
  tags: cve,cve2026,yeti,auth-bypass
http:
  - method: GET
    path:
      - "{{BaseURL}}/api/v2/audit/timeline/"
    matchers-condition: and
    matchers:
      - type: dsl
        dsl:
          - 'status_code == 200'
          - 'contains(content_type, "application/json")'
          - 'contains(body, "\"target_id\"")'
          - 'contains(body, "\"actor\"")'
          - 'contains(body, "\"action\"")'
        condition: and

CVE-2026-63482.yaml on GitHub

Suricata rules (network detection)

1 rule that alert on traffic matching this exploit: VEDAS CVE-2026-63482 Yeti - Unauthenticated Audit Timeline Disclosure. Add them to your Suricata rule set and reload.

alert http $EXTERNAL_NET any -> $HTTP_SERVERS $HTTP_PORTS (msg:"VEDAS CVE-2026-63482 Yeti - Unauthenticated Audit Timeline Disclosure"; flow:established,to_server; http.method; content:"GET"; http.uri; content:"/api/v2/audit/timeline/"; nocase; fast_pattern; classtype:web-application-attack; reference:cve,CVE-2026-63482; reference:url,https://www.exploit.observer/?keyword=CVE-2026-63482&match=exact; reference:url,https://subdomain.center/?engine=ammonites&keyword=yeti&match=exact; sid:1103002; rev:1;)

CVE-2026-63482.rules on GitHub

References

Other references

• https://github.com/yeti-platform/yeti/security/advisories/GHSA-34r4-95hx-gxqr (x_refsource_CONFIRM)
• https://github.com/yeti-platform/yeti/pull/1276 (x_refsource_MISC)
• https://github.com/yeti-platform/yeti/commit/692af02ffc05faabc8638b15a88765cb0e3f2503 (x_refsource_MISC)
• https://github.com/yeti-platform/yeti/releases/tag/2.5.1 (x_refsource_MISC)

Other databases

• CVE record (cve.org)
• NVD
• Exploit Observer

Where this comes from

This advisory is generated automatically by VEDAS from: CVE.org record, cve-scores (EPSS and VEDAS), Exploit Observer, vedas-signatures. Text in quotes is reproduced from the source; everything else is a fixed template filled with source fields. Nothing here is written by a language model. Check the vendor advisory before acting, and read how VEDAS and Exploit Observer work, and their limits.