Opencontainers vulnerabilities
We track 6 vulnerabilities in Opencontainers products. 6 are rated high or critical, and none are known to be exploited. The most recent was published on November 6, 2025.
Latest Opencontainers vulnerabilities
- 7.5 High severity
runc: UNIX Symbolic Link (Symlink) Following
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 sh
- 7.5 High severity
runc: UNIX Symbolic Link (Symlink) Following
runc is a CLI tool for spawning and running containers according to the OCI specification. Versions 1.0.0-rc3 through 1.2.7, 1.3.0-rc.1 through 1.3.2, and 1.4.0-rc.1 through 1.4.0-rc.2, due to insufficient checks when bind-mounting `/dev/pts/$n` to `/dev/conso
- 7.8 High severity
runc: UNIX Symbolic Link (Symlink) Following
runc is a CLI tool for spawning and running containers according to the OCI specification. In versions 1.2.7 and below, 1.3.0-rc.1 through 1.3.1, 1.4.0-rc.1 and 1.4.0-rc.2 files, runc would not perform sufficient verification that the source of the bind-mount
- 8.6 High severity
runc: Exposure of Resource to Wrong Sphere
runc is a CLI tool for spawning and running containers on Linux according to the OCI specification. In runc 1.1.11 and earlier, due to an internal file descriptor leak, an attacker could cause a newly-spawned container process (from runc exec) to have a workin
- 7.8 High severity
runc: Improper Link Resolution Before File Access
runc is a CLI tool for spawning and running containers according to the OCI specification. It was found that AppArmor can be bypassed when `/proc` inside the container is symlinked with a specific mount configuration. This issue has been fixed in runc version
- 7.8 High severity
runc: Incorrect Default Permissions
runc is a CLI tool for spawning and running containers on Linux according to the OCI specification. A bug was found in runc prior to version 1.1.2 where `runc exec --cap` created processes with non-empty inheritable Linux process capabilities, creating an atyp