Is CVE-2026-63500 exploited in the wild?

No. Junglewise Threat Intelligence has no report of CVE-2026-63500 being exploited in the wild.

How severe is CVE-2026-63500?

High severity, with a CVSS score of 7.1, published 3 November 2026.

Which products and versions are affected?

Yeti-Platform Yeti Prior to 2.5.1.

Is there a fix for CVE-2026-63500?

Yes: fixed in 2.5.1. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.

How is CVE-2026-63500 attacked?

It is attacked over the network, in a software library.

Am I affected by CVE-2026-63500?

Check whether you run Yeti-Platform 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.

CVE-2026-63500: Yeti path traversal in DFIQ UUID archive export

CVE-2026-63500 · Severity: high · CVSS 7.1 · Published 2026-11-03

Yeti is a forensics intelligence platform used by threat intelligence and digital forensics teams. A flaw in how Yeti validates UUID fields in DFIQ (Digital Forensics and Incident Response Questions) allows an authenticated user to inject path traversal sequences that, when combined with the archive export function, write arbitrary YAML files outside the intended directory on the server. An attacker with low-level access could write malicious files in unexpected locations, potentially leading to code execution or data integrity compromise depending on the writable paths available to the Yeti service account.

Technologies: Yeti-Platform Yeti. Vendors: Yeti-Platform.

Quick answers

Is CVE-2026-63500 exploited in the wild?: No. Junglewise Threat Intelligence has no report of CVE-2026-63500 being exploited in the wild.
How severe is CVE-2026-63500?: High severity, with a CVSS score of 7.1, published 3 November 2026.
Which products and versions are affected?: Yeti-Platform Yeti Prior to 2.5.1.
Is there a fix for CVE-2026-63500?: Yes: fixed in 2.5.1. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
How is CVE-2026-63500 attacked?: It is attacked over the network, in a software library.
Am I affected by CVE-2026-63500?: Check whether you run Yeti-Platform 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: 2.5.1

Technical details

The vulnerability is a path traversal (CWE-22) affecting DFIQ object handling. An authenticated attacker can import a DFIQ object with a malicious UUID containing traversal sequences (e.g., "../../../../tmp/pwn") via POST /api/v2/dfiq/from_yaml, then trigger archive export via POST /api/v2/dfiq/to_archive, which unsafely interpolates the UUID into a filesystem path. The fix validates UUIDs against RFC 4122 format at import time and adds path confinement checks at export time using path resolution verification.

Affected products

Yeti Platform Yeti Prior to 2.5.1

Timeline

2026-07-01: other: Fix committed
2026-11-03: advisory

References

This page as Markdown. Free to reuse under CC BY 4.0 with a link back.