Skip to content

build(deps): Bump github.com/opencontainers/runc from 1.5.2 to 1.5.3 - #2223

Open
dependabot[bot] wants to merge 1 commit into
release-1.20from
dependabot/go_modules/release-1.20/github.com/opencontainers/runc-1.5.3
Open

dependabot[bot] wants to merge 1 commit into
release-1.20from
dependabot/go_modules/release-1.20/github.com/opencontainers/runc-1.5.3

Conversation

@dependabot

@dependabot dependabot Bot commented on behalf of github Nov 15, 2026

Copy link
Copy Markdown
Contributor

Bumps github.com/opencontainers/runc from 1.5.2 to 1.5.3.

Release notes

Sourced from github.com/opencontainers/runc's releases.

runc v1.5.3 -- "Let me hear you make decisions without your television."

This is the third patch release in the 1.5.z release series of runc. It includes a fix for a high-severity vulnerability (CVE-2026-119101) affecting users who checkpoint and restore containers, as well as a few other fixes. Users are encouraged to update.

Security

This release includes a fix for the following high-severity security issue:

  • CVE-2026-119101 allowed a malicious image, using crafted symlinks in its rootfs, to confuse the way runc names external mounts for CRIU, and so make runc restore bind-mount an arbitrary host directory into the restored container, read-write. Only users who both checkpoint and later restore containers running untrusted images are affected (checkpoint/restore requires root, so rootless runc is not affected). The same issue was found in crun (CVE-2026-115520); CRIU itself is fixed in CVE-2026-119614.

    In addition, runc restore no longer makes read-only bind mounts writable, even temporarily, while preparing the container mounts.

Fixed

  • Running a container which does not have its own mount namespace no longer changes the propagation of host's / and of the parent mount of the container rootfs (they were made private or slave). (#5537, #5581)
  • When making the container rootfs read-only (root.readonly), runc no longer clears the nosuid, nodev, noexec and nosymfollow flags of the rootfs mount (this only happened when not using a user namespace). (#5588, #5601)
  • The defaults mount option is no longer passed to the kernel as filesystem-specific mount data, which made mounting filesystems that do not accept it (such as tmpfs) fail. (#5500, #5520, #5602)

Changed

Static Linking Notices

The runc binaries distributed with this release are statically linked with the following GNU LGPL-2.1 licensed libraries, with runc acting as a "work that uses the Library":

... (truncated)

Changelog

Sourced from github.com/opencontainers/runc's changelog.

[1.5.3] - 2026-11-12

Let me hear you make decisions without your television.

Security

This release includes a fix for the following high-severity security issue:

  • CVE-2026-119101 allowed a malicious image, using crafted symlinks in its rootfs, to confuse the way runc names external mounts for CRIU, and so make runc restore bind-mount an arbitrary host directory into the restored container, read-write. Only users who both checkpoint and later restore containers running untrusted images are affected (checkpoint/restore requires root, so rootless runc is not affected). The same issue was found in crun (CVE-2026-115520); CRIU itself is fixed in CVE-2026-119614.

    In addition, runc restore no longer makes read-only bind mounts writable, even temporarily, while preparing the container mounts.

Fixed

  • Running a container which does not have its own mount namespace no longer changes the propagation of host's / and of the parent mount of the container rootfs (they were made private or slave). (#5537, #5581)
  • When making the container rootfs read-only (root.readonly), runc no longer clears the nosuid, nodev, noexec and nosymfollow flags of the rootfs mount (this only happened when not using a user namespace). (#5588, #5601)
  • The defaults mount option is no longer passed to the kernel as filesystem-specific mount data, which made mounting filesystems that do not accept it (such as tmpfs) fail. (#5500, #5520, #5602)

Changed

[1.4.4] - 2026-11-12

Never again is what you swore the time before.

Security

This release includes a fix for the following high-severity security issue:

  • CVE-2026-119101 allowed a malicious image, using crafted symlinks in its rootfs, to confuse the way runc names external mounts for CRIU, and so make runc restore bind-mount an arbitrary host directory into the restored

... (truncated)

Commits
  • 46365c6 VERSION: release v1.5.3
  • 9827e75 merge private security patches into ghsa-release-1.5.3
  • 34f3bd0 libct: don't bind mount read-only sources while preparing the restore
  • bc7676c libct: refuse CRIU external mount keys CRIU cannot read back
  • c74288c Merge pull request #5615 from kolyshkin/1.5-5609
  • 1720f92 ci: drop all-done-actionlint
  • 7a6f054 ci: make all-done fail when a needed job fails
  • 27ca323 ci: let all-done-validate tolerate skipped jobs
  • dc9dd22 Merge pull request #5601 from kolyshkin/1.5-5588
  • 0341208 Merge pull request #5602 from kolyshkin/1.5-5520
  • Additional commits viewable in compare view

Dependabot compatibility score

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.


Dependabot commands and options

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 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)

Bumps [github.com/opencontainers/runc](https://github.com/opencontainers/runc) from 1.5.2 to 1.5.3.
- [Release notes](https://github.com/opencontainers/runc/releases)
- [Changelog](https://github.com/opencontainers/runc/blob/main/CHANGELOG.md)
- [Commits](opencontainers/runc@v1.5.2...v1.5.3)

---
updated-dependencies:
- dependency-name: github.com/opencontainers/runc
  dependency-version: 1.5.3
  dependency-type: direct:production
  update-type: version-update:semver-patch
...

Signed-off-by: dependabot[bot] <support@github.com>
@dependabot dependabot Bot added dependencies Issue/PR Pull about a dependency file maintenance Issue/PR to create or address a team project management need labels Nov 15, 2026
@copy-pr-bot

copy-pr-bot Bot commented Nov 15, 2026

Copy link
Copy Markdown

This pull request requires additional validation before any workflows can run on NVIDIA's runners.

Pull request vetters can view their responsibilities here.

Contributors can view more details about this message here.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

dependencies Issue/PR Pull about a dependency file maintenance Issue/PR to create or address a team project management need

Projects

None yet

Development

Successfully merging this pull request may close these issues.

0 participants