Every CVE Search/ Get API key

CVE-2026-41579

runc: Malicious image with /dev symlink can trigger limited host filesystem integrity violations

3.3 LowFix available

runc is a CLI tool for spawning and running containers according to the OCI specification. In versions prior to 1.3.6, 1.4.0-rc.1, 1.4.0-rc.12, 1.5.0-rc.1, and 1.5.0-rc.1, when setting up the container rootfs, setupPtmx and setupDevSymlinks call os.Remove and os.Symlink with a filepath.Join string which allow an image with /dev as a symlink to trick runc into deleting files called ptmx on the host or creating a hardcoded set of symlinks with specific names and targets in an arbitrary pre-existing host directory. This issue is not exploitable under Docker, because Docker creates a top-level read-only layer that masks any malicious /dev symlink present in the container image — unlike some other Linux container tooling, whose higher-level runtimes built on runc remain exposed to exploitation via a malicious image. This issue has been fixed in versions 1.3.6, 1.4.3 and 1.5.0.

Attack profile

How easy it is to exploit

Attack vector
Local
Complexity
Low
Privileges needed
None
User interaction
Required

What an attacker can affect

Confidentiality
None
Integrity
Low
Availability
None

Exploit likelihood

0.19%Up 0.2 points since Jun 14, 2026
90%50%10%1%

What each source reports

CVE List Score used 3.3

runc: Malicious image with /dev symlink can trigger limited host filesystem integrity violations

runc is a CLI tool for spawning and running containers according to the OCI specification. In versions prior to 1.3.6, 1.4.0-rc.1, 1.4.0-rc.12, 1.5.0-rc.1, and 1.5.0-rc.1, when setting up the container rootfs, setupPtmx and setupDevSymlinks call os.Remove and os.Symlink with a filepath.Join string which allow an image with /dev as a symlink to trick runc into deleting files called ptmx on the host or creating a hardcoded set of symlinks with specific names and targets in an arbitrary pre-existing host directory. This issue is not exploitable under Docker, because Docker creates a top-level read-only layer that masks any malicious /dev symlink present in the container image — unlike some other Linux container tooling, whose higher-level runtimes built on runc remain exposed to exploitation via a malicious image. This issue has been fixed in versions 1.3.6, 1.4.3 and 1.5.0.

Record
CVE-2026-41579
CVSS 3.1
3.3 LowCVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:N/I:L/A:N
Weakness
CWE-61
Updated
2026-11-02
EUVDEUVD-2026-40859 3.3

runc is a CLI tool for spawning and running containers according to the OCI specification. In versions prior to 1.3.6, 1.4.0-rc.1, 1.4.0-rc.12, 1.5.0-rc.1, and 1.5.0-rc.1, when setting up the container rootfs, setupPtmx and setupDevSymlinks call os.Remove and os.Symlink with a filepath.Join string which allow an image with /dev as a symlink to trick runc into deleting files called ptmx on the host or creating a hardcoded set of symlinks with specific names and targets in an arbitrary pre-existing host directory. This issue is not exploitable under Docker, because Docker creates a top-level read-only layer that masks any malicious /dev symlink present in the container image — unlike some other Linux container tooling, whose higher-level runtimes built on runc remain exposed to exploitation via a malicious image. This issue has been fixed in versions 1.3.6, 1.4.3 and 1.5.0.

Record
EUVD-2026-40859
CVSS 3.1
3.3 LowCVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:N/I:L/A:N
Updated
2026-11-02
GitHub AdvisoriesGHSA-xjvp-4fhw-gc47 4.8

runc: Malicious image with /dev symlink can trigger limited host filesystem integrity violations

Impact

When setting up the container rootfs, setupPtmx and setupDevSymlinks call os.Remove and os.Symlink with a filepath.Join string which allow an image with /dev as a symlink to trick runc into deleting files called ptmx on the host or creating a hardcoded set of symlinks with specific names and targets in an arbitrary pre-existing host directory.

Please note that this issue is not exploitable under Docker because it creates a top-level ro layer that masks any malicious /dev symlink present in the container image (this is also done without mounting the lower layers so there is no opportunity for the malicious /dev symlink to trick it into resolving to some other path). Unfortunately, Podman and containerd<sup>†</sup> do not do this and so users using those higher-level runtimes with runc can be exploited via a malicious image.

This issue mirrors a somewhat similar issue in crun, which was also published recently.

† Actually, at the time the issue was analysed, containerd had dead code that implemented this feature but the implementation contained several security issues that would arguably have made it more exploitable than in runc. Luckily, the code appears to have never been used (at least since 2017) and the code has since been removed.

Mitigating Factors

There are a few mitigating factors about this issue which reduce the impact for most users quite significantly, and is the reason why we decided to release the fix publicly without an embargo.

While the deletion of ptmx seems like a significant issue, in practice it is quite limited. Notably, devpts does not permit you to unlink /dev/pts/ptmx regardless of privileges and so it is not a usable target for this attack. Additionally, while /dev/ptmx can be unlinked<sup>‡</sup>, trying to use an image with a symlink from /dev to /dev will cause runc will return an error before it reaches the buggy code (it correctly detects a symlink loop while setting up the mount target and the code correctly scopes the lookup inside the container). Thus, the only files called ptmx that are guaranteed to exist on the system cannot actually be removed by this bug and so only some user file that happens to have that specific name could be deleted, which seems fairly unlikely to happen on real systems.

As for the issue of symlinks, again the impact is likely quite limited. While the creation of arbitrary symlinks could be used to create drop-in files for system services (and thus lead to a container breakout), the hardcoded set of symlink names and targets that this bug allows you to create on the host make it quite unlikely that you would be able to do much more than pollute the host system with dummy symlinks. Here is the complete list of symlinks that can be created with this attack:

  • core → /proc/kcore
  • fd → /proc/self/fd/
  • ptmx → pts/ptmx
  • stdin → /proc/self/fd/0
  • stdout → /proc/self/fd/1
  • stderr → /proc/self/fd/2

Note that none of these symlinks are likely to point to user-controlled data -- the /proc/self/fd/$n symlinks are all properties of the process accessing them (so privileged processes will only see the state they were spawned with) and the pts/ptmx symlink is almost certainly in the same privilege scope as the directory the symlink itself is in. It seems the only somewhat plausible impact would be that a service could return an error when trying to parse one of these symlinks and thus treat it as an invalid configuration file. How arbitrary processes deal with this situation is a bit hard to analyse, but most daemons require…

Record
GHSA-xjvp-4fhw-gc47
CVSS 4.0
4.8 MediumCVSS:4.0/AV:L/AC:L/AT:N/PR:N/UI:P/VC:N/VI:L/VA:N/SC:N/SI:L/SA:N
CVSS 3.1
3.3 LowCVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:N/I:L/A:N
Weakness
CWE-61
Updated
2026-11-02
NVD 3.3

runc is a CLI tool for spawning and running containers according to the OCI specification. In versions prior to 1.3.6, 1.4.0-rc.1, 1.4.0-rc.12, 1.5.0-rc.1, and 1.5.0-rc.1, when setting up the container rootfs, setupPtmx and setupDevSymlinks call os.Remove and os.Symlink with a filepath.Join string which allow an image with /dev as a symlink to trick runc into deleting files called ptmx on the host or creating a hardcoded set of symlinks with specific names and targets in an arbitrary pre-existing host directory. This issue is not exploitable under Docker, because Docker creates a top-level read-only layer that masks any malicious /dev symlink present in the container image — unlike some other Linux container tooling, whose higher-level runtimes built on runc remain exposed to exploitation via a malicious image. This issue has been fixed in versions 1.3.6, 1.4.3 and 1.5.0.

Record
CVE-2026-41579
CVSS 3.1
3.3 LowCVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:N/I:L/A:N
Weakness
CWE-61
Updated
2026-11-02
OSVALPINE-CVE-2026-41579 3.3

runc is a CLI tool for spawning and running containers according to the OCI specification. In versions prior to 1.3.6, 1.4.0-rc.1, 1.4.0-rc.12, 1.5.0-rc.1, and 1.5.0-rc.1, when setting up the container rootfs, setupPtmx and setupDevSymlinks call os.Remove and os.Symlink with a filepath.Join string which allow an image with /dev as a symlink to trick runc into deleting files called ptmx on the host or creating a hardcoded set of symlinks with specific names and targets in an arbitrary pre-existing host directory. This issue is not exploitable under Docker, because Docker creates a top-level read-only layer that masks any malicious /dev symlink present in the container image — unlike some other Linux container tooling, whose higher-level runtimes built on runc remain exposed to exploitation via a malicious image. This issue has been fixed in versions 1.3.6, 1.4.3 and 1.5.0.

Record
ALPINE-CVE-2026-41579
CVSS 3.1
3.3 LowCVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:N/I:L/A:N
Updated
2026-11-03
OSVBELL-CVE-2026-41579 3.3
Record
BELL-CVE-2026-41579
CVSS 3.1
3.3 LowCVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:N/I:L/A:N
Updated
2026-11-02
Show 20 moreShow less
OSV 3.3

runc: Malicious image with /dev symlink can trigger limited host filesystem integrity violations

runc is a CLI tool for spawning and running containers according to the OCI specification. In versions prior to 1.3.6, 1.4.0-rc.1, 1.4.0-rc.12, 1.5.0-rc.1, and 1.5.0-rc.1, when setting up the container rootfs, setupPtmx and setupDevSymlinks call os.Remove and os.Symlink with a filepath.Join string which allow an image with /dev as a symlink to trick runc into deleting files called ptmx on the host or creating a hardcoded set of symlinks with specific names and targets in an arbitrary pre-existing host directory. This issue is not exploitable under Docker, because Docker creates a top-level read-only layer that masks any malicious /dev symlink present in the container image — unlike some other Linux container tooling, whose higher-level runtimes built on runc remain exposed to exploitation via a malicious image. This issue has been fixed in versions 1.3.6, 1.4.3 and 1.5.0.

Record
CVE-2026-41579
CVSS 3.1
3.3 LowCVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:N/I:L/A:N
Weakness
CWE-61
Updated
2026-11-02
OSVDEBIAN-CVE-2026-41579 3.3

runc is a CLI tool for spawning and running containers according to the OCI specification. In versions prior to 1.3.6, 1.4.0-rc.1, 1.4.0-rc.12, 1.5.0-rc.1, and 1.5.0-rc.1, when setting up the container rootfs, setupPtmx and setupDevSymlinks call os.Remove and os.Symlink with a filepath.Join string which allow an image with /dev as a symlink to trick runc into deleting files called ptmx on the host or creating a hardcoded set of symlinks with specific names and targets in an arbitrary pre-existing host directory. This issue is not exploitable under Docker, because Docker creates a top-level read-only layer that masks any malicious /dev symlink present in the container image — unlike some other Linux container tooling, whose higher-level runtimes built on runc remain exposed to exploitation via a malicious image. This issue has been fixed in versions 1.3.6, 1.4.3 and 1.5.0.

Record
DEBIAN-CVE-2026-41579
CVSS 3.1
3.3 LowCVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:N/I:L/A:N
Updated
2026-11-02
OSVGHSA-xjvp-4fhw-gc47 4.8

runc: Malicious image with /dev symlink can trigger limited host filesystem integrity violations

Impact

When setting up the container rootfs, setupPtmx and setupDevSymlinks call os.Remove and os.Symlink with a filepath.Join string which allow an image with /dev as a symlink to trick runc into deleting files called ptmx on the host or creating a hardcoded set of symlinks with specific names and targets in an arbitrary pre-existing host directory.

Please note that this issue is not exploitable under Docker because it creates a top-level ro layer that masks any malicious /dev symlink present in the container image (this is also done without mounting the lower layers so there is no opportunity for the malicious /dev symlink to trick it into resolving to some other path). Unfortunately, Podman and containerd<sup>†</sup> do not do this and so users using those higher-level runtimes with runc can be exploited via a malicious image.

This issue mirrors a somewhat similar issue in crun, which was also published recently.

† Actually, at the time the issue was analysed, containerd had dead code that implemented this feature but the implementation contained several security issues that would arguably have made it more exploitable than in runc. Luckily, the code appears to have never been used (at least since 2017) and the code has since been removed.

Mitigating Factors

There are a few mitigating factors about this issue which reduce the impact for most users quite significantly, and is the reason why we decided to release the fix publicly without an embargo.

While the deletion of ptmx seems like a significant issue, in practice it is quite limited. Notably, devpts does not permit you to unlink /dev/pts/ptmx regardless of privileges and so it is not a usable target for this attack. Additionally, while /dev/ptmx can be unlinked<sup>‡</sup>, trying to use an image with a symlink from /dev to /dev will cause runc will return an error before it reaches the buggy code (it correctly detects a symlink loop while setting up the mount target and the code correctly scopes the lookup inside the container). Thus, the only files called ptmx that are guaranteed to exist on the system cannot actually be removed by this bug and so only some user file that happens to have that specific name could be deleted, which seems fairly unlikely to happen on real systems.

As for the issue of symlinks, again the impact is likely quite limited. While the creation of arbitrary symlinks could be used to create drop-in files for system services (and thus lead to a container breakout), the hardcoded set of symlink names and targets that this bug allows you to create on the host make it quite unlikely that you would be able to do much more than pollute the host system with dummy symlinks. Here is the complete list of symlinks that can be created with this attack:

  • core → /proc/kcore
  • fd → /proc/self/fd/
  • ptmx → pts/ptmx
  • stdin → /proc/self/fd/0
  • stdout → /proc/self/fd/1
  • stderr → /proc/self/fd/2

Note that none of these symlinks are likely to point to user-controlled data -- the /proc/self/fd/$n symlinks are all properties of the process accessing them (so privileged processes will only see the state they were spawned with) and the pts/ptmx symlink is almost certainly in the same privilege scope as the directory the symlink itself is in. It seems the only somewhat plausible impact would be that a service could return an error when trying to parse one of these symlinks and thus treat it as an invalid configuration file. How arbitrary processes deal with this situation is a bit hard to analyse, but most daemons require…

Record
GHSA-xjvp-4fhw-gc47
CVSS 4.0
4.8 MediumCVSS:4.0/AV:L/AC:L/AT:N/PR:N/UI:P/VC:N/VI:L/VA:N/SC:N/SI:L/SA:N
CVSS 3.1
3.3 LowCVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:N/I:L/A:N
Weakness
CWE-61
Updated
2026-11-02
OSVOESA-2026-3154 3.3

runc security update

runc is a CLI tool for spawning and running containers according to the OCI specification.

Security Fix(es):

runc is a CLI tool for spawning and running containers according to the OCI specification. In versions prior to 1.3.6, 1.4.0-rc.1, 1.4.0-rc.12, 1.5.0-rc.1, and 1.5.0-rc.1, when setting up the container rootfs, setupPtmx and setupDevSymlinks call os.Remove and os.Symlink with a filepath.Join string which allow an image with /dev as a symlink to trick runc into deleting files called ptmx on the host or creating a hardcoded set of symlinks with specific names and targets in an arbitrary pre-existing host directory. This issue is not exploitable under Docker, because Docker creates a top-level read-only layer that masks any malicious /dev symlink present in the container image — unlike some other Linux container tooling, whose higher-level runtimes built on runc remain exposed to exploitation via a malicious image. This issue has been fixed in versions 1.3.6, 1.4.3 and 1.5.0.(CVE-2026-41579)

Record
OESA-2026-3154
CVSS 3.1
3.3 LowCVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:N/I:L/A:N
Updated
2026-11-02
OSVUBUNTU-CVE-2026-41579 3.3

runc is a CLI tool for spawning and running containers according to the OCI specification. In versions prior to 1.3.6, 1.4.0-rc.1, 1.4.0-rc.12, 1.5.0-rc.1, and 1.5.0-rc.1, when setting up the container rootfs, setupPtmx and setupDevSymlinks call os.Remove and os.Symlink with a filepath.Join string which allow an image with /dev as a symlink to trick runc into deleting files called ptmx on the host or creating a hardcoded set of symlinks with specific names and targets in an arbitrary pre-existing host directory. This issue is not exploitable under Docker, because Docker creates a top-level read-only layer that masks any malicious /dev symlink present in the container image — unlike some other Linux container tooling, whose higher-level runtimes built on runc remain exposed to exploitation via a malicious image. This issue has been fixed in versions 1.3.6, 1.4.3 and 1.5.0.

Record
UBUNTU-CVE-2026-41579
CVSS 3.1
3.3 LowCVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:N/I:L/A:N
Updated
2026-11-02
OSVAZL-91590 No score

CVE-2026-41579 affecting package runc for versions less than 1.3.6-1

runc is a CLI tool for spawning and running containers according to the OCI specification. In versions prior to 1.3.6, 1.4.0-rc.1, 1.4.0-rc.12, 1.5.0-rc.1, and 1.5.0-rc.1, when setting up the container rootfs, setupPtmx and setupDevSymlinks call os.Remove and os.Symlink with a filepath.Join string which allow an image with /dev as a symlink to trick runc into deleting files called ptmx on the host or creating a hardcoded set of symlinks with specific names and targets in an arbitrary pre-existing host directory. This issue is not exploitable under Docker, because Docker creates a top-level read-only layer that masks any malicious /dev symlink present in the container image — unlike some other Linux container tooling, whose higher-level runtimes built on runc remain exposed to exploitation via a malicious image. This issue has been fixed in versions 1.3.6, 1.4.3 and 1.5.0.

Record
AZL-91590
Updated
2026-11-02
OSVCLSA-2026-1783518302 No score

runc: Fix of CVE-2026-41579

  • CVE-2026-41579: fix /dev symlink path traversal in setupPtmx/setupDevSymlinks by resolving /dev inside the rootfs via fd-based helpers
Record
CLSA-2026-1783518302
Updated
2026-11-02
OSVCLSA-2026-1784034091 No score

runc: Fix of CVE-2026-41579

  • CVE-2026-41579: fix /dev symlink path traversal in rootfs /dev setup
Record
CLSA-2026-1784034091
Updated
2026-11-02
OSVGO-2026-5761 No score

Malicious image with /dev symlink can trigger limited host filesystem integrity violations in github.com/opencontainers/runc

Malicious image with /dev symlink can trigger limited host filesystem integrity violations in github.com/opencontainers/runc

Record
GO-2026-5761
Updated
2026-11-02
OSVopenSUSE-SU-2026:11301-1 No score

runc-1.4.3-1.1 on GA media

These are all security issues fixed in the runc-1.4.3-1.1 package on the GA media of openSUSE Tumbleweed.

Record
openSUSE-SU-2026:11301-1
Updated
2026-11-02
OSVopenSUSE-SU-2026:21431-1 No score

Security update for runc

This update for runc fixes the following issues:

Update to 1.3.6.

  • CVE-2026-41579: malicious image with a /dev symlink can trigger limited host filesystem integrity violations (bsc#1268275).

Other updates and bugfixes:

  • Version 1.3.6:
    • Various integration test improvements.
    • When masking directories with maskPaths, runc will now re- use a single tmpfs instance (which is not writeable) 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).
  • Version 1.3.5:
    • Recursive atime-related mount flags (rrelatime et al.) are now applied properly.
    • PR #4757 caused a regression that resulted in spurious cannot start a container that has stopped errors when running runc create and has thus been reverted.
    • Updated builds to Go 1.25, libseccomp v2.6.0.
    • Minor signing keyring updates.
Record
openSUSE-SU-2026:21431-1
Updated
2026-11-02
OSVopenSUSE-SU-2026:21483-1 No score

Security update for govulncheck-vulndb

This update for govulncheck-vulndb fixes the following issues:

  • Update to version 0.0.20260723T184607 2026-07-23T18:46:07Z (jsc#PED-11136).

Go CVE Numbering Authority IDs added or updated with aliases:

  • GO-2026-4730 CVE-2026-33022 GHSA-cv4x-93xx-wgfj
  • GO-2026-4761 CVE-2026-33211 GHSA-j5q5-j9gm-2w5c
  • GO-2026-5102 CVE-2026-45021 GHSA-3vcp-chfh-f6r2
  • GO-2026-5272 CVE-2026-40938 GHSA-94jr-7pqp-xhcq
  • GO-2026-5486 CVE-2026-40924 GHSA-m2cx-gpqf-qf74
  • GO-2026-5542 CVE-2026-40090 GHSA-pj97-4p9w-gx3q
  • GO-2026-5630 CVE-2026-25542 GHSA-rmx9-2pp3-xhcr
  • GO-2026-5643 CVE-2026-40923 GHSA-rx35-6rhx-7858
  • GO-2026-5675 CVE-2026-41492 GHSA-vvf7-6rmr-m29q
  • GO-2026-5711 CVE-2026-40161 GHSA-wjxp-xrpv-xpff
  • GO-2026-5746 CVE-2026-41567 GHSA-x86f-5xw2-fm2r
  • GO-2026-5749 CVE-2026-41328 GHSA-x92x-px7w-4gx4
  • GO-2026-5837 CVE-2026-44840 GHSA-q2m9-6jp9-c6mc
  • GO-2026-5929 CVE-2026-44342 GHSA-26v7-h57m-gh9m
  • GO-2026-5930 CVE-2026-33655 GHSA-6qcr-qxgr-m7fv
  • GO-2026-5933 GHSA-3g4q-2f67-2gvh
  • GO-2026-5934 GHSA-59qp-cfj3-rp64
  • GO-2026-5935 GHSA-7856-g3gv-9wq8
  • GO-2026-5936 CVE-2026-53552 GHSA-26rh-24rg-j3vv
  • GO-2026-5937 CVE-2026-53508 GHSA-2jcc-mxv7-p3f9
  • GO-2026-5938 CVE-2026-53553 GHSA-4g5x-hcwm-82jw
  • GO-2026-5939 CVE-2026-10517 GHSA-698x-9w2p-7vvp
  • GO-2026-5940 CVE-2026-53572 GHSA-6w3m-4hhp-775q
  • GO-2026-5941 CVE-2026-53487 GHSA-gvhc-wv3v-7pf8
  • GO-2026-5942 CVE-2026-46600
  • GO-2026-5944 CVE-2026-50197 GHSA-659f-rgp5-w4wf
  • GO-2026-5945 CVE-2026-6815 GHSA-rmxx-v9rj-vpvg
  • GO-2026-5946 CVE-2026-52831 GHSA-v5px-423j-pf7p
  • GO-2026-5947 CVE-2026-53649 GHSA-xqhv-chqm-fhcc
  • GO-2026-5948 CVE-2026-50554 GHSA-588f-fvcv-xhvf
  • GO-2026-5949 CVE-2026-50553 GHSA-rqrh-8wpv-x7hh
  • GO-2026-5950 CVE-2026-53602 GHSA-339v-266x-79xr
  • GO-2026-5951 CVE-2026-10219 GHSA-6jm8-4fhr-5w64
  • GO-2026-5952 CVE-2026-49834 GHSA-9vcr-p3rj-q5q6
  • GO-2026-5953 CVE-2026-9094 GHSA-c9w5-qp6m-m395
  • GO-2026-5956 CVE-2026-55252 GHSA-h5g6-xmh4-hc37
  • GO-2026-5957 CVE-2026-54158 GHSA-5xfx-xj4h-5p7r
  • GO-2026-5958 CVE-2026-54068 GHSA-gcm7-57gf-953c
  • GO-2026-5959 CVE-2026-54072 GHSA-h29v-hj44-q8cv
  • GO-2026-5961 CVE-2026-54069 GHSA-hvr9-72v2-fff3
  • GO-2026-5962 CVE-2026-54088 GHSA-m93h-4hw7-5qcm
  • GO-2026-5963 CVE-2026-54067 GHSA-mvjr-vv3c-w4qv
  • GO-2026-5964 CVE-2026-54066 GHSA-p4m3-mgmm-c664
  • GO-2026-5965 CVE-2026-54070 GHSA-w7cg-whh7-xp28
  • GO-2026-5966 CVE-2026-54089 GHSA-xqp3-jq6g-x3qm
  • GO-2026-5967 CVE-2026-50551 GHSA-56mp-4f3v-fgj2
  • GO-2026-5968 CVE-2026-54174 GHSA-fpg8-7664-jc5q
  • GO-2026-5969 GHSA-g936-7jqj-mwv8
  • GO-2026-5970 CVE-2026-56852
  • GO-2026-5973 CVE-2026-54250 GHSA-jxr7-mqhw-9p98
  • GO-2026-5974 CVE-2026-44300 GHSA-wmj8-9953-vff5
  • GO-2026-5975 CVE-2026-50018 GHSA-42j2-w334-qxw7
  • GO-2026-5976 CVE-2026-50141 GHSA-g7mm-9vx7-jm7h
  • GO-2026-5977 CVE-2026-50013 GHSA-qrh4-p6v4-mrfg
  • GO-2026-5978 CVE-2026-50125 GHSA-qw5r-ppcg-f8rj
  • GO-2026-5979 CVE-2026-50006 GHSA-xrcf-6jh3-ggvx
  • GO-2026-5980 CVE-2026-50158 GHSA-2c7f-fxww-6w6c
  • GO-2026-5981 GHSA-mqxv-9rm6-w8qc
  • GO-2026-5982 GHSA-pqg7-v6wh-3pfp
  • GO-2026-5984 CVE-2026-53604 GHSA-2p2f-px33-4vv5
  • GO-2026-5985 GHSA-7rx3-5wx3-5v76
  • GO-2026-5986 CVE-2026-61699 GHSA-cm26-5974-52h8
  • GO-2026-5987 CVE-2026-55513 GHSA-g4x6-jcvr-9m3g
  • GO-2026-5988 CVE-2026-54628 GHSA-hwrq-8wxh-q4xv
  • GO-2026-5989 CVE-2026-55512 GHSA-m3cx-mwpg-32jg
  • GO-2026-5990 CVE-2026-54629 GHSA-mf78-3rpf-r784
  • GO-2026-5991 CVE-2026-53603 GHSA-q4vm-pq3q-8wgq
  • GO-2026-5992 CVE-2026-61549 GHSA-qf34-295c-26v8
  • GO-2026-5996 CVE-2026-54450 GHSA-pph6-vfjv-vpjw
  • GO-2026-5997 CVE-2026-54452 GHSA-xgch-x3mx-cm3c
  • GO-2026-5998 CVE-2026-54495 GHSA-398h-7f66-3h4p
  • GO-2026-5999 CVE-2026-10814 GHSA-jh6h-v6mp-h22v
  • GO-2026-6002 CVE-2026-58196 GHSA-pr64-jmmf-jp54
  • GO-2026-6003 CVE-2026-53714 GHSA-22xc-xg2r-9j7v
  • GO-2026-6004 CVE-2026-52833 GHSA-3v79-m2cg-89ww
  • GO-2026-6005 CVE-2026-53715 GHSA-8fv2-88gg-hm7q
  • GO-2026-6006 CVE-2026-53716 GHSA-cxpq-8v7q-cg56 *…
Record
openSUSE-SU-2026:21483-1
Updated
2026-11-02
OSVSUSE-SU-2026:22938-1 No score

Security update for runc

This update for runc fixes the following issues:

Update to 1.3.6.

  • CVE-2026-41579: malicious image with a /dev symlink can trigger limited host filesystem integrity violations (bsc#1268275).

Other updates and bugfixes:

  • Version 1.3.6:
    • Various integration test improvements.
    • When masking directories with maskPaths, runc will now re- use a single tmpfs instance (which is not writeable) 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).
  • Version 1.3.5:
    • Recursive atime-related mount flags (rrelatime et al.) are now applied properly.
    • PR #4757 caused a regression that resulted in spurious cannot start a container that has stopped errors when running runc create and has thus been reverted.
    • Updated builds to Go 1.25, libseccomp v2.6.0.
    • Minor signing keyring updates.
Record
SUSE-SU-2026:22938-1
Updated
2026-11-02
OSVSUSE-SU-2026:22942-1 No score

Security update for runc

This update for runc fixes the following issues:

Update to 1.3.6.

  • CVE-2026-41579: malicious image with a /dev symlink can trigger limited host filesystem integrity violations (bsc#1268275).

Other updates and bugfixes:

  • Version 1.3.6:
    • Various integration test improvements.
    • When masking directories with maskPaths, runc will now re- use a single tmpfs instance (which is not writeable) 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).
  • Version 1.3.5:
    • Recursive atime-related mount flags (rrelatime et al.) are now applied properly.
    • PR #4757 caused a regression that resulted in spurious cannot start a container that has stopped errors when running runc create and has thus been reverted.
    • Updated builds to Go 1.25, libseccomp v2.6.0.
    • Minor signing keyring updates.
Record
SUSE-SU-2026:22942-1
Updated
2026-11-02
OSVSUSE-SU-2026:23047-1 No score

Security update for runc

This update for runc fixes the following issues:

  • CVE-2026-41579: runc allows a malicious image with a /dev symlink to trigger limited host filesystem integrity violations (bsc#1268275).

Changes for runc:

  • update to 1.3.6:
  • Various integration test improvements. (#5222, #5237, #5226, #5229, #5239, #5249, #5269, #5287, #5295, #5304)
  • When masking directories with maskPaths, runc will now re- use a single tmpfs instance (which is not writeable) 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).
  • update to 1.3.5
  • Recursive atime-related mount flags (rrelatime et al.) are now applied properly. (#5115, #5098)
  • PR #4757 caused a regression that resulted in spurious cannot start a container that has stopped errors when running runc create and has thus been reverted. (#5158, #5153, #5151, #4645, #4757)
  • Updated builds to Go 1.25, libseccomp v2.6.0. (#5111, #5053)
  • Minor signing keyring updates. (#5146, #5139, #5144, #5148)
Record
SUSE-SU-2026:23047-1
Updated
2026-11-02
OSVSUSE-SU-2026:23164-1 No score

Security update for runc

This update for runc fixes the following issues:

  • CVE-2026-41579: runc allows a malicious image with a /dev symlink to trigger limited host filesystem integrity violations (bsc#1268275).

Changes for runc:

  • update to 1.3.6:
  • Various integration test improvements. (#5222, #5237, #5226, #5229, #5239, #5249, #5269, #5287, #5295, #5304)
  • When masking directories with maskPaths, runc will now re- use a single tmpfs instance (which is not writeable) 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).
  • update to 1.3.5
  • Recursive atime-related mount flags (rrelatime et al.) are now applied properly. (#5115, #5098)
  • PR #4757 caused a regression that resulted in spurious cannot start a container that has stopped errors when running runc create and has thus been reverted. (#5158, #5153, #5151, #4645, #4757)
  • Updated builds to Go 1.25, libseccomp v2.6.0. (#5111, #5053)
  • Minor signing keyring updates. (#5146, #5139, #5144, #5148)
Record
SUSE-SU-2026:23164-1
Updated
2026-11-02
OSVSUSE-SU-2026:3428-1 No score

Security update for runc

This update for runc fixes the following issues:

Update to 1.3.6.

  • CVE-2026-41579: malicious image with a /dev symlink can trigger limited host filesystem integrity violations (bsc#1268275).

Other updates and bugfixes:

  • Version 1.3.6:
    • When masking directories with maskPaths, runc will now re- use a single tmpfs instance (which is not writeable) 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).
  • Version 1.3.5:
    • Recursive atime-related mount flags (rrelatime et al.) are now applied properly.
    • PR #4757 caused a regression that resulted in spurious cannot start a container that has stopped errors when running runc create and has thus been reverted.
    • Updated builds to Go 1.25, libseccomp v2.6.0.
    • Minor signing keyring updates.
Record
SUSE-SU-2026:3428-1
Updated
2026-11-02
OSVSUSE-SU-2026:3428-2 No score

Security update for runc

This update for runc fixes the following issues:

Update to 1.3.6.

  • CVE-2026-41579: malicious image with a /dev symlink can trigger limited host filesystem integrity violations (bsc#1268275).

Other updates and bugfixes:

  • Version 1.3.6:
    • When masking directories with maskPaths, runc will now re- use a single tmpfs instance (which is not writeable) 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).
  • Version 1.3.5:
    • Recursive atime-related mount flags (rrelatime et al.) are now applied properly.
    • PR #4757 caused a regression that resulted in spurious cannot start a container that has stopped errors when running runc create and has thus been reverted.
    • Updated builds to Go 1.25, libseccomp v2.6.0.
    • Minor signing keyring updates.
Record
SUSE-SU-2026:3428-2
Updated
2026-11-02
OSVSUSE-SU-2026:3433-1 No score

Security update for runc

This update for runc fixes the following issues:

Update to 1.3.6.

  • CVE-2026-41579: malicious image with a /dev symlink can trigger limited host filesystem integrity violations (bsc#1268275).

Other updates and bugfixes:

  • Version 1.3.6:
    • When masking directories with maskPaths, runc will now re- use a single tmpfs instance (which is not writeable) 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).
  • Version 1.3.5:
    • Recursive atime-related mount flags (rrelatime et al.) are now applied properly.
    • PR #4757 caused a regression that resulted in spurious cannot start a container that has stopped errors when running runc create and has thus been reverted.
    • Updated builds to Go 1.25, libseccomp v2.6.0.
    • Minor signing keyring updates.
Record
SUSE-SU-2026:3433-1
Updated
2026-11-02
OSVSUSE-SU-2026:3433-2 No score

Security update for runc

This update for runc fixes the following issues:

Update to 1.3.6.

  • CVE-2026-41579: malicious image with a /dev symlink can trigger limited host filesystem integrity violations (bsc#1268275).

Other updates and bugfixes:

  • Version 1.3.6:
    • When masking directories with maskPaths, runc will now re- use a single tmpfs instance (which is not writeable) 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).
  • Version 1.3.5:
    • Recursive atime-related mount flags (rrelatime et al.) are now applied properly.
    • PR #4757 caused a regression that resulted in spurious cannot start a container that has stopped errors when running runc create and has thus been reverted.
    • Updated builds to Go 1.25, libseccomp v2.6.0.
    • Minor signing keyring updates.
Record
SUSE-SU-2026:3433-2
Updated
2026-11-02

Affected products

Affected packages

Affected packages
PackageAffectedFixed
github.com/opencontainers/runc
Go
 through 1.3.5
1.3.6
github.com/opencontainers/runc
Go
 1.4.0 to 1.4.2
1.4.3
github.com/opencontainers/runc
Go
 1.5.0-rc.1 to 1.5.0-rc.2
1.5.0-rc.3
runc
Alpine:v3.24
 1.4.0 up to 1.4.3-r0
1.4.3-r0
runc
Azure Linux:3
 before 1.3.6-1
1.3.6-1
runc
Alpaquita:23
 1.1.4-r3 up to 1.3.6-r0
1.3.6-r0
runc
Alpaquita:25
 1.3.0-r1 up to 1.3.6-r0
1.3.6-r0
runc
Alpaquita:stream
 1.1.7-r1 up to 1.4.3-r0
1.4.3-r0
runc
TuxCare:AlmaLinux:9.6
 before 4:1.2.5-3.el9_6.tuxcare.els4
4:1.2.5-3.el9_6.tuxcare.els4
runc
TuxCare:AlmaLinux:9.2
 before 4:1.2.8-1.el9_1.tuxcare.els4
4:1.2.8-1.el9_1.tuxcare.els4
Show 54 moreShow less
Affected packages
PackageAffectedFixed
runc
Debian:12
 All versions, plus listed versions
1.1.10+ds1-11.1.12+ds1-11.1.12+ds1-21.1.12+ds1-31.1.12+ds1-4
Show 21 moreShow less
1.1.12+ds1-51.1.12+ds1-5.11.1.15+ds1-11.1.15+ds1-21.1.5+ds1-11.1.5+ds1-1+deb12u11.1.5+ds1-21.1.5+ds1-31.1.5+ds1-41.1.5+ds1-51.3.0+ds1-11.3.0+ds1-21.3.0+ds1-31.3.0+ds1-41.3.2+ds1-11.3.3+ds1-11.3.3+ds1-21.3.3+ds1-31.3.5+ds1-11.3.6+ds1-11.4.3+ds1-1
 None known
runc
Debian:13
 All versions, plus listed versions
1.1.15+ds1-21.3.0+ds1-11.3.0+ds1-21.3.0+ds1-31.3.0+ds1-4
Show 7 moreShow less
1.3.2+ds1-11.3.3+ds1-11.3.3+ds1-21.3.3+ds1-31.3.5+ds1-11.3.6+ds1-11.4.3+ds1-1
 None known
runc
Debian:14
 before 1.3.6+ds1-1, plus listed versions
1.1.15+ds1-21.3.0+ds1-11.3.0+ds1-21.3.0+ds1-31.3.0+ds1-4
Show 5 moreShow less
1.3.2+ds1-11.3.3+ds1-11.3.3+ds1-21.3.3+ds1-31.3.5+ds1-1
1.3.6+ds1-1
github.com/opencontainers/runc
Go
 before 1.3.6
1.3.6
github.com/opencontainers/runc
Go
 1.4.0 up to 1.4.3
1.4.3
github.com/opencontainers/runc
Go
 1.5.0-rc.1 up to 1.5.0-rc.3
1.5.0-rc.3
github.com/opencontainers/runc
Go
 before 1.3.6, 1.4.0 up to 1.4.3, 1.5.0-rc.1 up to 1.5.0-rc.3
1.3.61.4.31.5.0-rc.3
runc
openEuler:20.03-LTS-SP4
 before docker-1.0.0.rc3-235.oe2003sp4
docker-1.0.0.rc3-235.oe2003sp4
runc
openEuler:22.03-LTS-SP4
 before 1.1.3-40.oe2203sp4
1.1.3-40.oe2203sp4
runc
openEuler:24.03-LTS-SP1
 before 1.1.8-35.oe2403sp1
1.1.8-35.oe2403sp1
runc
openEuler:24.03-LTS-SP3
 before 1.1.8-35.oe2403sp3
1.1.8-35.oe2403sp3
runc
openEuler:24.03-LTS-SP4
 before 1.1.8-35.oe2403sp4
1.1.8-35.oe2403sp4
runc
SUSE:Linux Micro 6.2
From an advisory covering 3 CVEs
 before 1.3.6-160000.1.1
1.3.6-160000.1.1
runc
SUSE:Linux Enterprise Server 16.0
From an advisory covering 3 CVEs
 before 1.3.6-160000.1.1
1.3.6-160000.1.1
runc
SUSE:Linux Enterprise Server for SAP applications 16.0
From an advisory covering 3 CVEs
 before 1.3.6-160000.1.1
1.3.6-160000.1.1
runc
SUSE:Linux Micro 6.0
 before 1.3.6-1.1
1.3.6-1.1
runc
SUSE:Linux Micro 6.1
 before 1.3.6-slfo.1.1_1.1
1.3.6-slfo.1.1_1.1
runc
SUSE:Linux Enterprise Server LTSS Extended Security 12 SP5
From an advisory covering 3 CVEs
 before 1.3.6-16.76.1
1.3.6-16.76.1
runc
SUSE:Linux Enterprise Server 12 SP5-LTSS
 before 1.3.6-16.76.1
1.3.6-16.76.1
runc
SUSE:Linux Enterprise Micro 5.3
From an advisory covering 3 CVEs
 before 1.3.6-150000.101.1
1.3.6-150000.101.1
runc
SUSE:Linux Enterprise Micro 5.4
From an advisory covering 3 CVEs
 before 1.3.6-150000.101.1
1.3.6-150000.101.1
runc
SUSE:Linux Enterprise Micro 5.5
From an advisory covering 3 CVEs
 before 1.3.6-150000.101.1
1.3.6-150000.101.1
runc
SUSE:Linux Enterprise Module for Basesystem 15 SP7
From an advisory covering 3 CVEs
 before 1.3.6-150000.101.1
1.3.6-150000.101.1
runc
SUSE:Enterprise Storage 7.1
From an advisory covering 3 CVEs
 before 1.3.6-150000.101.1
1.3.6-150000.101.1
runc
SUSE:Linux Enterprise High Performance Computing 15 SP4-ESPOS
 before 1.3.6-150000.101.1
1.3.6-150000.101.1
runc
SUSE:Linux Enterprise High Performance Computing 15 SP4-LTSS
 before 1.3.6-150000.101.1
1.3.6-150000.101.1
runc
SUSE:Linux Enterprise High Performance Computing 15 SP5-ESPOS
 before 1.3.6-150000.101.1
1.3.6-150000.101.1
runc
SUSE:Linux Enterprise High Performance Computing 15 SP5-LTSS
 before 1.3.6-150000.101.1
1.3.6-150000.101.1
runc
SUSE:Linux Enterprise Server 15 SP4-LTSS
 before 1.3.6-150000.101.1
1.3.6-150000.101.1
runc
SUSE:Linux Enterprise Server 15 SP5-LTSS
 before 1.3.6-150000.101.1
1.3.6-150000.101.1
runc
SUSE:Linux Enterprise Server 15 SP6-LTSS
 before 1.3.6-150000.101.1
1.3.6-150000.101.1
runc
SUSE:Linux Enterprise Server for SAP Applications 15 SP4
 before 1.3.6-150000.101.1
1.3.6-150000.101.1
runc
SUSE:Linux Enterprise Server for SAP Applications 15 SP5
 before 1.3.6-150000.101.1
1.3.6-150000.101.1
runc
SUSE:Linux Enterprise Server for SAP Applications 15 SP6
 before 1.3.6-150000.101.1
1.3.6-150000.101.1
runc
Ubuntu:Pro:16.04:LTS
 All versions, plus listed versions
0.0.8+dfsg-20.1.1-0ubuntu5~16.041.0.0~rc1-0ubuntu1~16.041.0.0~rc1-0ubuntu2~16.04.11.0.0~rc1-0ubuntu2~16.04.1.1
Show 9 moreShow less
1.0.0~rc2-0ubuntu2~16.04.11.0.0~rc2+docker1.12.6-0ubuntu1~16.04.11.0.0~rc2+docker1.13.1-0ubuntu1~16.04.11.0.0~rc2+docker1.13.1-0ubuntu1~16.04.21.0.0~rc7+git20190403.029124da-0ubuntu1~16.04.31.0.0~rc7+git20190403.029124da-0ubuntu1~16.04.41.0.0~rc7+git20190403.029124da-0ubuntu1~16.04.4+esm11.0.0~rc7+git20190403.029124da-0ubuntu1~16.04.4+esm21.0.0~rc7+git20190403.029124da-0ubuntu1~16.04.4+esm4
 None known
runc
Ubuntu:Pro:18.04:LTS
 All versions, plus listed versions
1.0.0~rc2+docker1.13.1-0ubuntu11.0.0~rc4+dfsg1-21.0.0~rc4+dfsg1-61.0.0~rc4+dfsg1-6ubuntu0.18.04.11.0.0~rc7+git20190403.029124da-0ubuntu1~18.04.1
Show 13 moreShow less
1.0.0~rc7+git20190403.029124da-0ubuntu1~18.04.21.0.0~rc7+git20190403.029124da-0ubuntu1~18.04.2+esm11.0.0~rc10-0ubuntu1~18.04.11.0.0~rc10-0ubuntu1~18.04.21.0.0~rc93-0ubuntu1~18.04.11.0.0~rc93-0ubuntu1~18.04.21.0.0~rc95-0ubuntu1~18.04.11.0.0~rc95-0ubuntu1~18.04.21.0.1-0ubuntu2~18.04.11.1.0-0ubuntu1~18.04.11.1.4-0ubuntu1~18.04.11.1.4-0ubuntu1~18.04.21.1.4-0ubuntu1~18.04.2+esm1
 None known
runc
Ubuntu:20.04:LTS
 All versions, plus listed versions
1.0.0~rc8+git20190923.3e425f80-0ubuntu11.0.0~rc10-0ubuntu11.0.0~rc93-0ubuntu1~20.04.11.0.0~rc93-0ubuntu1~20.04.21.0.0~rc95-0ubuntu1~20.04.1
Show 11 moreShow less
1.0.0~rc95-0ubuntu1~20.04.21.0.1-0ubuntu2~20.04.11.1.0-0ubuntu1~20.04.11.1.0-0ubuntu1~20.04.21.1.4-0ubuntu1~20.04.11.1.4-0ubuntu1~20.04.21.1.4-0ubuntu1~20.04.31.1.7-0ubuntu1~20.04.11.1.7-0ubuntu1~20.04.21.1.7-0ubuntu1~20.04.41.1.7-0ubuntu1~20.04.5
 None known
runc-app
Ubuntu:20.04:LTS
 All versions, plus listed versions
1.1.12-0ubuntu2~20.04.1
 None known
runc
Ubuntu:22.04:LTS
 All versions, plus listed versions
1.0.1-0ubuntu21.0.1-0ubuntu31.0.3-0ubuntu11.1.0-0ubuntu11.1.0-0ubuntu1.1
Show 8 moreShow less
1.1.4-0ubuntu1~22.04.11.1.4-0ubuntu1~22.04.21.1.4-0ubuntu1~22.04.31.1.7-0ubuntu1~22.04.11.1.7-0ubuntu1~22.04.21.1.7-0ubuntu1~22.04.41.1.7-0ubuntu1~22.04.51.1.7-0ubuntu1~22.04.6
 None known
runc-app
Ubuntu:22.04:LTS
 All versions, plus listed versions
1.1.12-0ubuntu2~22.04.11.2.5-0ubuntu1~22.04.11.3.0-0ubuntu2~22.04.11.3.3-0ubuntu1~22.04.21.3.3-0ubuntu1~22.04.31.3.4-0ubuntu1~22.04.1
 None known
runc
Ubuntu:24.04:LTS
 All versions, plus listed versions
1.1.7-0ubuntu21.1.10+ds1-1ubuntu11.1.10+ds1-1ubuntu21.1.12+ds1-1ubuntu11.1.12+ds1-2ubuntu11.1.12+ds1-2ubuntu1.11.1.12+ds1-2ubuntu1.21.1.12+ds1-2ubuntu1.3
 None known
runc-app
Ubuntu:24.04:LTS
 All versions, plus listed versions
1.1.10-0ubuntu11.1.12-0ubuntu11.1.12-0ubuntu21.1.12-0ubuntu31.1.12-0ubuntu3.1
Show 5 moreShow less
1.2.5-0ubuntu1~24.04.11.3.0-0ubuntu2~24.04.11.3.3-0ubuntu1~24.04.21.3.3-0ubuntu1~24.04.31.3.4-0ubuntu1~24.04.1
 None known
runc
Ubuntu:25.10
 All versions, plus listed versions
1.1.15+ds1-2ubuntu1
 None known
runc-app
Ubuntu:25.10
 All versions, plus listed versions
1.2.5-0ubuntu11.3.0-0ubuntu11.3.0-0ubuntu21.3.3-0ubuntu1~25.10.21.3.3-0ubuntu1~25.10.31.3.4-0ubuntu1~25.10.1
 None known
runc-stable
Ubuntu:25.10
 All versions, plus listed versions
1.3.0-0ubuntu11.3.3-0ubuntu1~25.10.21.3.3-0ubuntu1~25.10.31.3.4-0ubuntu1~25.10.1
 None known
runc
Ubuntu:26.10
 All versions, plus listed versions
1.3.3+ds1-2ubuntu11.3.5+ds1-1ubuntu11.3.6+ds1-1ubuntu1
 None known
runc-app
Ubuntu:26.10
 All versions, plus listed versions
1.4.0-0ubuntu11.5.1-0ubuntu11.5.1-0ubuntu2
 None known
runc-stable
Ubuntu:26.10
 All versions, plus listed versions
1.3.4-0ubuntu11.5.1-0ubuntu11.5.1-0ubuntu2
 None known
runc
Ubuntu:26.04:LTS
 All versions, plus listed versions
1.1.15+ds1-2ubuntu11.3.3+ds1-2ubuntu1
 None known
runc-app
Ubuntu:26.04:LTS
 All versions, plus listed versions
1.3.0-0ubuntu21.3.3-0ubuntu11.3.3-0ubuntu21.4.0-0ubuntu1
 None known
runc-stable
Ubuntu:26.04:LTS
 All versions, plus listed versions
1.3.0-0ubuntu11.3.3-0ubuntu11.3.3-0ubuntu21.3.4-0ubuntu1
 None known
runc
openSUSE:Tumbleweed
 before 1.4.3-1.1
1.4.3-1.1
runc
openSUSE:Leap 16.0
From an advisory covering 3 CVEs
 before 1.3.6-160000.1.1
1.3.6-160000.1.1
govulncheck-vulndb
openSUSE:Leap 16.0
From an advisory covering 1734 CVEs
 before 0.0.20260723T184607-160000.1.1
0.0.20260723T184607-160000.1.1

History

History
RecordedChangedSources
affected, facts
affected, aliases, referencesOSV
first indexedCVE List, EUVD, GitHub Advisories, NVD, OSV

Dates are when Every CVE recorded each change. Upstream dates may differ.

In short

CVE-2026-41579 is a low vulnerability (CVSS 3.3) in Linuxfoundation Runc, published June 16, 2026. No source lists public exploit code. EPSS puts the chance of exploitation in the next 30 days at 0.19%, the 8th percentile. Fixed in github.com/opencontainers/runc 1.3.6.

References

Show 194 moreShow less
This page doesn't list everything

Left out here: 1,558 references and the rest of 3 source descriptions. The JSON record has them.

Pages All vulnerabilities Browse Docs Sources Guide Get API key
MoveEnter Open