CVE-2025-62596: youki container escape and denial of service due to arbitrary write gadgets and procfs write redirects

CVE-2025-62596 · Severity: critical · CVSS 10 · Published 2025-11-06

Youki is a container runtime written in Rust. In versions 0.5.6 and below, youki’s apparmor handling performs insufficiently strict write-target validation, and when combined with path substitution during pathname resolution, can allow writes to unintended procfs locations. While resolving a path component-by-component, a shared-mount race can substitute intermediate components and redirect the final target. This issue is fixed in version 0.5.7.

Technologies: youki (crates.io). Vendors: crates.io.

Quick answers

Is CVE-2025-62596 exploited in the wild?
No. Junglewise Threat Intelligence has no report of CVE-2025-62596 being exploited in the wild.
How severe is CVE-2025-62596?
Critical severity, with a CVSS score of 10, published 6 November 2025.
Which products and versions are affected?
youki (crates.io) SEMVER:introduced=0,fixed=0.5.7.
Is there a fix for CVE-2025-62596?
Yes. youki (crates.io): upgrade to 0.5.7 or later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
Am I affected by CVE-2025-62596?
Check whether you run youki (crates.io) or Youki-Dev Youki 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

  • youki (crates.io): upgrade to 0.5.7 or later
    cargo update -p youki

Affected products

  • youki (crates.io) SEMVER:introduced=0,fixed=0.5.7
  • Youki-Dev Youki

Identifiers

  • CVE-2025-62596
  • GHSA-vf95-55w6-qmrf

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