🛡️ AZL-69826 — runc
Description
CVE-2025-52881 affecting package runc for versions less than 1.3.3-1
runc is a CLI tool for spawning and running containers according to the OCI specification. In versions 1.2.7, 1.3.2 and 1.4.0-rc.2, an attacker can trick runc into misdirecting writes to /proc to other procfs files through the use of a racing container with shared mounts (we have also verified this attack is possible to exploit using a standard Dockerfile with docker buildx build as that also permits triggering parallel execution of containers with custom shared mounts configured). This redirect could be through symbolic links in a tmpfs or theoretically other methods such as regular bind-mounts. While similar, the mitigation applied for the related CVE, CVE-2019-19921, was fairly limited and effectively only caused runc to verify that when LSM labels are written they are actually procfs files. This issue is fixed in versions 1.2.8, 1.3.3, and 1.4.0-rc.3.
Affected software
AZL-69826 is recorded against 1 package.
- runc (fixed in 1.3.3-1)
Timeline and source
Published on 6 November 2025 and last revised on 21 April 2026. No public exploit is currently recorded for this entry. Record sourced from OSV.
References
Details
Affected Packages
| Software | From version | Fixed in |
|---|---|---|
| runc | — | 1.3.3-1 |
References
Similar Threats
- Unknown ALSA-2023:6938
- Unknown ALSA-2023:6380
- Unknown ALSA-2023:2758
- Unknown ALSA-2023:2802
- Unknown ALSA-2022:8090
More AZL 6 advisories
Browse all of AZL 6 in the advisory index.
Free Vulnerability Check
Is your site affected by AZL-69826?
BotEraser helps you identify potentially vulnerable plugins and themes by checking your installation against AZL-69826 and other known CVE records.
Scan My Site Free →No credit card required · Results in minutes
ⓘ Data Notice: The information presented above has been compiled from publicly available internet sources. Boteraser aggregates this data solely for informational purposes and does not independently classify, evaluate, or endorse any findings about the vulnerabilities listed. The accuracy and completeness of this information is the sole responsibility of the original publishers. Boteraser and its operators accept no liability for any decisions made based on this data.