Cyber Resilience

CVE-2025-62596

Race Condition in Youki-Dev Youki ≤ 0.5.7

Race Condition
Published
06 November 2025
Modified
10 November 2025
Patch / advisory
View advisory
CVSS Score v4 7.3
Click a component to see what it means
Raw vectorCVSS:4.0/AV:L/AC:L/AT:P/PR:L/UI:A/VC:H/VI:H/VA:H/SC:H/SI:H/SA:H/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X
EPSS Score 0.0025 16th percentile
Risk Priority 55 floored blend · peak EPSS

Summary

CVE-2025-62596 is a high-severity UNIX Symbolic Link (Symlink) Following (CWE-61) vulnerability in Youki-Dev Youki. Its CVSS base score is 7.3 (High).

Operationally, exploitation aligns with the MITRE ATT&CK technique Path Interception (T1034); ranked at the 16th percentile by exploit likelihood (below the median); it is not currently listed in the CISA KEV catalog.

The strongest mitigations our analysis identified map to AC-3 (Access Enforcement) and AC-4 (Information Flow Enforcement) — see the control section below for these in your framework.

OWASP Top 10 for Web (2025)

A01:2025 Broken Access Control

EU & UK References

Vulnerability Data

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…

more

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.

CWE(s)
CWE-61CWE-363

Related Threats

MITRE ATT&CK Enterprise Techniques

T1034 Path Interception Persistence
**This technique has been deprecated.
attack.mitre.org →
Derived from this CVE’s CWE(s) via the direct CWE→ATT&CK cross-walk.

CVEs Like This One

CVE-2025-62161Same product: Youki-Dev Youki
CVE-2025-54867Same product: Youki-Dev Youki
CVE-2024-45310Shared CWE-363, CWE-61
CVE-2025-52565Shared CWE-363, CWE-61
CVE-2025-52881Shared CWE-363, CWE-61
CVE-2025-31133Shared CWE-363, CWE-61
CVE-2024-47515Shared CWE-61
CVE-2026-1386Shared CWE-61
CVE-2025-57802Shared CWE-61
CVE-2026-43570Shared CWE-61

Affected Assets

youki-dev
youki
≤ 0.5.7

Mitigating Controls

Control response

Prevent
Stop it (NIST 800-53)

—

Detect
Catch it (NIST detect / respond)

—

Harden
Shrink the surface (DISA STIG)
  • 2 hardening rules · 2 OS baselines
Validate
Prove the fix (OWASP ASVS)
  • V15.4.2
  • V5.2.5

Mitigating Controls (NIST 800-53 r5) AI

AC-3 Access Enforcement good match

Access enforcement must resolve the actual target of any file reference and apply authorizations to it, directly stopping symlink traversal to unauthorized objects.

AC-4 Information Flow Enforcement partial match

Information-flow enforcement on file operations must follow the resolved target rather than the link name, blocking unauthorized data movement via symlinks.

AC-6 Least Privilege partial match

Least-privilege restrictions on the directories that may contain links or targets reduce the set of files an attacker can reach even if a symlink is followed.

SA-8 Security and Privacy Engineering Principles partial match

SA-8 mandates security engineering principles that include atomic operations and safe file handling, preventing introduction of check-then-use race conditions.

Mitigating Controls (NIST CSF 2.0) AI

Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→CSF cross-walk (authority under review) — links open the control.

PR.PS-06 mostly match
prevents

Secure SDLC practices directly prevent introduction of symlink-following flaws in file-handling code.

ID.RA-01 partial match
prevents

Vulnerability identification can discover existing symlink issues but does not prevent or remediate them in code.

PR.AA-05 partial match
prevents

Least-privilege access policies can limit damage from symlink attacks but do not address the coding flaw itself.

Mitigating Controls (ISO/IEC 27001:2022 Annex A) AI

Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→ISO cross-walk (authority under review) — links open the control.

A.8.29 Security testing in development and acceptance mostly match
finds

Security testing can detect symlink-following vulnerabilities before deployment, covering most of the weakness.

A.8.25 Secure development life cycle partial match
prevents

Secure development lifecycle practices can include TOCTOU-safe file handling, but do not guarantee elimination of link-following races.

A.8.26 Application security requirements partial match
prevents

Application security requirements can mandate atomic file operations, yet the control is broader than this specific race condition.

A.8.27 Secure system architecture and engineering principles partial match
prevents

Secure-architecture principles require safe file-handling and canonicalization, directly addressing symlink attacks.

A.8.28 Secure coding partial match
prevents

Secure-coding standards mandate explicit symlink checks and safe open patterns, fully mitigating CWE-61.

A.8.3 Information access restriction partial match
mitigates

Access-control rules can restrict which files a process may open, reducing symlink-following risk but not eliminating the underlying path-resolution flaw.

Hardening callouts derived

Configuration rules from DISA STIG baselines that bear on weaknesses of the type cited by this CVE. Each rule is shown with the relationship its mapping actually records, against the CWE it was authored against. Derived via CVE→CWE over `controls_xwalks` (authoritative rows only; rows rated `none` are excluded).

Oracle Linux 8 (1 rule)
  • V-248577 OL 8 must enable kernel parameters to enforce Discretionary Access Control (DAC) on symlinks. prevents CWE-61

References