build(deps): bump the go_modules group across 2 directories with 1 update

[dependabot]

Bumps the go_modules group with 1 update in the / directory: github.com/opencontainers/runc.
Bumps the go_modules group with 1 update in the /cmd directory: github.com/opencontainers/runc.

Updates github.com/opencontainers/runc from 1.4.0 to 1.4.3

Release notes

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

runc v1.4.2 -- "Я — Земля! Я своих провожаю питомцев"

This is the second patch release of the 1.4.z release series of runc.

Fixed

• A regression in runc v1.3.0 which can result in a stuck runc exec or runc run when the container process runs for a short time. (#5208, #5210, #5216)

• Mount sources that need to be open on the host are now closed earlier during container start, reducing the total amount of used file descriptors and helping to avoid hitting the open files limit when handling many such mounts. (#5177, #5201)

Static Linking Notices

The runc binary 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":

• libseccomp

The versions of these libraries were not modified from their upstream versions, but in order to comply with the LGPL-2.1 (§6(a)), we have attached the complete source code for those libraries which (when combined with the attached runc source code) may be used to exercise your rights under the LGPL-2.1.

However we strongly suggest that you make use of your distribution's packages or download them from the authoritative upstream sources, especially since these libraries are related to the security of your containers.

---

Thanks to the following contributors for making this release possible:

• Ayato Tokubi atokubi@redhat.com
• Akihiro Suda akihiro.suda.cz@hco.ntt.co.jp
• Aleksa Sarai cyphar@cyphar.com
• Kir Kolyshkin kolyshkin@gmail.com
• Li Fubang lifubang@acmcoder.com
• Rodrigo Campos Catelin rodrigo@amutable.com

Signed-off-by: Kir Kolyshkin kolyshkin@gmail.com

Changelog

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

[1.4.3] - 2026-06-13

The best way to irritate him is to feed his grandmother to the Ravenous Bugblatter Beast of Traal.

Security

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

• CVE-2026-41579 allowed a malicious image with a /dev symlink to have limited write access to the host filesystem in ways that our analysis indicates was too limited to be problematic in practice. This bug was very similar to those fixed in [CVE-2025-31133][], [CVE-2025-52565][], [CVE-2025-31133][] and was simply missed at the time when we hardened the rootfs preparation code. We have conducted a deeper audit and not found any other problematic cases.

Fixed

• Various integration test improvements. (#5222, #5237, #5226, #5229, #5239, #5249, #5269, #5287, #5295, #5304)

Changed

• When masking directories with maskPaths, runc will now reuse a single tmpfs instance (which is not writable) to reduce the number tmpfs superblocks that need to be reaped when containers die (in particular, Kubernetes applies masks to per-CPU sysfs directories which get expensive quickly). (#5275, #5281)

[1.3.6] - 2026-06-13

On no account should you allow a Vogon to read poetry at you.

Security

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

• CVE-2026-41579 allowed a malicious image with a /dev symlink to have limited write access to the host filesystem in ways that our analysis indicates was too limited to be problematic in practice. This bug was very similar to those fixed in [CVE-2025-31133][], [CVE-2025-52565][], [CVE-2025-31133][] and was simply missed at the time when we hardened the rootfs preparation code. We have conducted a deeper audit and not found any other problematic cases.

  This patchset required backports for #5190 and #5285, which were primarily code reorganisations that were already backported to runc 1.4 and 1.5.

... (truncated)

Commits

• bb14dab VERSION: release v1.4.3
• 31d72bf merge CVE-2026-41579 fixes into release-1.4
• b2b50a4 rootfs: make cgroupv1 subsystem symlinks fd-based
• a7343f8 rootfs: make /dev initialisation code fd-based
• 5f2f6b5 rootfs: switch createDevices argument order
• 6a7de4e Merge pull request #5304 from ricardobranco777/1.4-5295
• a753597 Update busybox:glibc in integration tests to latest (1.38.0) builds
• 3d7f708 Update busybox:glibc in integration tests to latest (1.37.0) builds
• c6454ef tests/int: relax testPids fork error match string
• cae4907 tests/int: build TestPids pipelines programmatically
• Additional commits viewable in compare view

Updates github.com/opencontainers/runc from 1.4.0 to 1.4.3

Release notes

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

runc v1.4.2 -- "Я — Земля! Я своих провожаю питомцев"

This is the second patch release of the 1.4.z release series of runc.

Fixed

• A regression in runc v1.3.0 which can result in a stuck runc exec or runc run when the container process runs for a short time. (#5208, #5210, #5216)

• Mount sources that need to be open on the host are now closed earlier during container start, reducing the total amount of used file descriptors and helping to avoid hitting the open files limit when handling many such mounts. (#5177, #5201)

Static Linking Notices

The runc binary 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":

• libseccomp

The versions of these libraries were not modified from their upstream versions, but in order to comply with the LGPL-2.1 (§6(a)), we have attached the complete source code for those libraries which (when combined with the attached runc source code) may be used to exercise your rights under the LGPL-2.1.

However we strongly suggest that you make use of your distribution's packages or download them from the authoritative upstream sources, especially since these libraries are related to the security of your containers.

---

Thanks to the following contributors for making this release possible:

• Ayato Tokubi atokubi@redhat.com
• Akihiro Suda akihiro.suda.cz@hco.ntt.co.jp
• Aleksa Sarai cyphar@cyphar.com
• Kir Kolyshkin kolyshkin@gmail.com
• Li Fubang lifubang@acmcoder.com
• Rodrigo Campos Catelin rodrigo@amutable.com

Signed-off-by: Kir Kolyshkin kolyshkin@gmail.com

Changelog

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

[1.4.3] - 2026-06-13

The best way to irritate him is to feed his grandmother to the Ravenous Bugblatter Beast of Traal.

Security

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

• CVE-2026-41579 allowed a malicious image with a /dev symlink to have limited write access to the host filesystem in ways that our analysis indicates was too limited to be problematic in practice. This bug was very similar to those fixed in [CVE-2025-31133][], [CVE-2025-52565][], [CVE-2025-31133][] and was simply missed at the time when we hardened the rootfs preparation code. We have conducted a deeper audit and not found any other problematic cases.

Fixed

• Various integration test improvements. (#5222, #5237, #5226, #5229, #5239, #5249, #5269, #5287, #5295, #5304)

Changed

• When masking directories with maskPaths, runc will now reuse a single tmpfs instance (which is not writable) to reduce the number tmpfs superblocks that need to be reaped when containers die (in particular, Kubernetes applies masks to per-CPU sysfs directories which get expensive quickly). (#5275, #5281)

[1.3.6] - 2026-06-13

On no account should you allow a Vogon to read poetry at you.

Security

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

• CVE-2026-41579 allowed a malicious image with a /dev symlink to have limited write access to the host filesystem in ways that our analysis indicates was too limited to be problematic in practice. This bug was very similar to those fixed in [CVE-2025-31133][], [CVE-2025-52565][], [CVE-2025-31133][] and was simply missed at the time when we hardened the rootfs preparation code. We have conducted a deeper audit and not found any other problematic cases.

  This patchset required backports for #5190 and #5285, which were primarily code reorganisations that were already backported to runc 1.4 and 1.5.

... (truncated)

Commits

• bb14dab VERSION: release v1.4.3
• 31d72bf merge CVE-2026-41579 fixes into release-1.4
• b2b50a4 rootfs: make cgroupv1 subsystem symlinks fd-based
• a7343f8 rootfs: make /dev initialisation code fd-based
• 5f2f6b5 rootfs: switch createDevices argument order
• 6a7de4e Merge pull request #5304 from ricardobranco777/1.4-5295
• a753597 Update busybox:glibc in integration tests to latest (1.38.0) builds
• 3d7f708 Update busybox:glibc in integration tests to latest (1.37.0) builds
• c6454ef tests/int: relax testPids fork error match string
• cae4907 tests/int: build TestPids pipelines programmatically
• Additional commits viewable in compare view

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 <dependency name> major version will close this group update PR and stop Dependabot creating any more for the specific dependency's major version (unless you unignore this specific dependency's major version or upgrade to it yourself)
• @dependabot ignore <dependency name> minor version will close this group update PR and stop Dependabot creating any more for the specific dependency's minor version (unless you unignore this specific dependency's minor version or upgrade to it yourself)
• @dependabot ignore <dependency name> will close this group update PR and stop Dependabot creating any more for the specific dependency (unless you unignore this specific dependency or upgrade to it yourself)
• @dependabot unignore <dependency name> will remove all of the ignore conditions of the specified dependency
• @dependabot unignore <dependency name> <ignore condition> will remove the ignore condition of the specified dependency and ignore conditions
  You can disable automated security fix PRs for this repo from the Security Alerts page.