CVE-2025-62596
criticalpriority · track · 40EPSS 0.003 · 19 %ileEUUSEPSS · scored 2026-10-27
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.
cvss
Technical severity, 0–10. One row per scoring source.
base score 0–10 · higher = more severe · hover a vector to decode⚠ sources disagree · medium–critical · 4.1–10
ssvc
A stakeholder decision — act, attend, or track — from exploitation and impact.
weaknesses
The CWE weakness classes this flaw belongs to.
affected products (3)
Products and version ranges known to be affected.
advisories (1)
Vendor and ecosystem advisories describing this.
- GHSA-vf95-55w6-qmrfyouki container escape and denial of service due to arbitrary write gadgets and procfs write redirects2025-11-05ghsa · osvUS
### Impact ### youki’s apparmor handling performs insufficiently strict write-target validation, which—combined with path substitution during pathname resolution—can allow writes to unintended procfs locations. **Weak write-target check** youki only verifies that the destination lies somewhere under procfs. As a result, a write intended for `/proc/self/attr/apparmor/exec` can succeed even if the path has been redirected to `/proc/sys/kernel/hostname`(which is also in procfs). **Path substitution** While resolving a path component-by-component, a shared-mount race can substitute intermediate components and redirect the final target. This is a different project, but the core logic is similar to the CVE in runc. Issues were identified in runc, and verification was also conducted in youki to confirm the problems. https://github.com/opencontainers/runc/security/advisories/GHSA-cgrx-mc8f-2prm ### Credits ### Thanks to Li Fubang (@lifubang from acmcoder.com, CIIC) and Tõnis Tiigi (@tonistiigi from Docker) for both independently discovering runc's original vulnerability, as well as Aleksa Sarai (@cyphar from SUSE) for the original research into this class of security issues and solutions.
also known as (3)
Other names and identifiers for this entity.
sources
Which sources assert this record, and when.
references (17)
External citations — patches, advisories, analysis.
- https://access.redhat.com/security/cve/cve-2025-62596cnnvd
- https://github.com/youki-dev/youki/commit/5886c91073b9be748bd8d5aed49c4a820548030acnnvd
- https://github.com/youki-dev/youki/releasesPatchcnnvd
- https://github.com/youki-dev/youki/security/advisories/GHSA-vf95-55w6-qmrfcnnvd
- https://pkg.go.dev/github.com/cyphar/filepath-securejoin/pathrs-lite/procfscnnvd
- https://youtu.be/tGseJW_uBB8cnnvd
- https://youtu.be/y1PaBzxwRWQcnnvd
- https://github.com/youki-dev/youki/commit/5886c91073b9be748bd8d5aed49c4a820548030aenisa_euvd
Attackers weaponise vulnerabilities like this against internet-exposed services. See what is exposed on your perimeter with a free passive scan.
Free scan