Sourced fromgithub.com/opencontainers/runc's releases.

runc v1.2.8 -- "鳥籠の中に囚われた屈辱を"

[!NOTE]Some vendors were given a pre-release version of this release.This public release includes two extra patches to fix regressionsdiscovered very late during the embargo period and were thus notincluded in the pre-release versions. Please update to this version.

This release contains fixes for three high-severity securityvulnerabilities in runc (CVE-2025-31133,CVE-2025-52565, andCVE-2025-52881). All three vulnerabilities ultimately allow (throughdifferent methods) for full container breakouts by bypassing runc'srestrictions for writing to arbitrary/proc files.

Security

• CVE-2025-31133 exploits an issue with how masked paths are implemented inrunc. When masking files, runc will bind-mount the container's/dev/nullinode on top of the file. However, if an attacker can replace/dev/nullwith a symlink to some other procfs file, runc will instead bind-mount thesymlink target read-write. This issue affected all known runc versions.

• CVE-2025-52565 is very similar in concept and application toCVE-2025-31133, except that it exploits a flaw in/dev/consolebind-mounts. When creating the/dev/console bind-mount (to/dev/pts/$n),if an attacker replaces/dev/pts/$n with a symlink then runc willbind-mount the symlink target over/dev/console. This issue affected allversions of runc >= 1.0.0-rc3.

• CVE-2025-52881 is a more sophisticated variant ofCVE-2019-19921,which was a flaw that allowed an attacker to trick runc into writing the LSMprocess labels for a container process into a dummy tmpfs file and thus notapply the correct LSM labels to the container process. The mitigation weapplied forCVE-2019-19921 was fairly limited and effectively only causedrunc to verify that when we write LSM labels that those labels are actualprocfs files. This issue affects all known runc versions.

Static Linking Notices

Therunc binary distributed with this release arestatically linked withthe followingGNU LGPL-2.1 licensed libraries, withrunc actingas a "work that uses the Library":

• libseccomp

... (truncated)

Sourced fromgithub.com/opencontainers/runc's changelog.

[1.2.8] - 2025-11-05

鳥籠の中に囚われた屈辱を

Security

This release includes fixes for the following high-severity security issues:

• CVE-2025-31133 exploits an issue with how masked paths are implemented inrunc. When masking files, runc will bind-mount the container's/dev/nullinode on top of the file. However, if an attacker can replace/dev/nullwith a symlink to some other procfs file, runc will instead bind-mount thesymlink target read-write. This issue affected all known runc versions.

• CVE-2025-52565 is very similar in concept and application toCVE-2025-31133, except that it exploits a flaw in/dev/consolebind-mounts. When creating the/dev/console bind-mount (to/dev/pts/$n),if an attacker replaces/dev/pts/$n with a symlink then runc willbind-mount the symlink target over/dev/console. This issue affected allversions of runc >= 1.0.0-rc3.

• CVE-2025-52881 is a more sophisticated variant ofCVE-2019-19921,which was a flaw that allowed an attacker to trick runc into writing the LSMprocess labels for a container process into a dummy tmpfs file and thus notapply the correct LSM labels to the container process. The mitigation weapplied forCVE-2019-19921 was fairly limited and effectively only causedrunc to verify that when we write LSM labels that those labels are actualprocfs files. This issue affects all known runc versions.

[1.2.7] - 2025-09-05

さんをつけろよデコ助野郎！

Fixed

• Removed preemptive "full access to cgroups" warning when callingrunc pause orrunc unpause as an unprivileged user without--systemd-cgroups. Now the warning is only emitted if an actual permissionerror was encountered. (#4709,#4720)
• Add time namespace to container config after checkpoint/restore. CRIU sinceversion 3.14 uses a time namespace for checkpoint/restore, however it wasnot joining the time namespace in runc. (#4696,#4714)
• Container processes will no longer inherit the CPU affinity of runc bydefault. Instead, the default CPU affinity of container processes will bethe largest set of CPUs permitted by the container's cpuset cgroup and anyother system restrictions (such as isolated CPUs). (#4041,#4815,#4858)

... (truncated)

• eeb7e60 VERSION: release v1.2.8
• cdee962 merge private security patches into ghsa-release-1.2.8
• b4cb2f5 rootfs: re-allow dangling symlinks in mount targets
• ee56b85 openat2: improve resilience on busy systems
• 2462b68 Merge pull request#4943 from lifubang/backport-1.2-4934-4937
• 99e41a5 ci: only run lint-extra job on PRs to main
• f2a1c98 CI: remove deprecated lima-vm/lima-actions/ssh
• 8f90185 selinux: use safe procfs API for labels
• 948d6e9 rootfs: switch to fd-based handling of mountpoint targets
• 7aa42ad libct: align param type for mountCgroupV1/V2 functions
• Additional commits viewable incompare view

You can trigger Dependabot actions by commenting on this PR:

• @dependabot rebase will rebase this PR
• @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
• @dependabot merge will merge this PR after your CI passes on it
• @dependabot squash and merge will squash and merge this PR after your CI passes on it
• @dependabot cancel merge will cancel a previously requested merge and block automerging
• @dependabot reopen will reopen this PR if it is closed
• @dependabot close will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually
• @dependabot show <dependency name> ignore conditions will show all of the ignore conditions of the specified dependency
• @dependabot ignore this major version will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this minor version will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)
  You can disable automated security fix PRs for this repo from theSecurity Alerts page.