BlackTreeCVE Intelligenceopencontainers · runc
Official source articles: GitHub GHSA-CGRX-MC8F-2PRM ↗ · GitHub GHSA-QW9X-CQR3-WC7R ↗ · GitHub GHSA-9493-H29P-RFM2 ↗. Check the applicable product and release in the original source.
High technical severity with public exploit material referenced by a structured source; prioritise exposed affected systems while verifying vendor guidance. Verified remediation exists for at least one product or source, but 2 structured product or package states remain unresolved. Apply remediation only to the exact product branch confirmed by its source.
Verified remediation exists for at least one product or source, but 2 structured product or package states remain unresolved. Apply remediation only to the exact product branch confirmed by its source.
Alpine, Debian, ubuntu findings are scoped to the named distribution, release and source package. An absent finding does not mean a package is unaffected.
BlackTree has verified remediation for at least one product or source, but the relevant distribution still reports no fixed package for 2 affected package states shown here. Treat those rows as affected with no fix until that distribution publishes a fixed version.
A published vendor fix does not prove that a matching update is enabled and installable on a particular asset. Confirm the local package candidate before scheduling remediation.
| Distribution release | Source package | Vendor state | Fixed version | Evidence |
|---|---|---|---|---|
| Alpine v3.23v3.23 · community | buildah | Vendor fix publishedAlpine records a security fix at this version. An absent entry does not mean the package is unaffected. | 1.42.1-r0 | Alpine Security Database ↗Source updated 11 Sep 2026 |
| Alpine v3.23v3.23 · community | podman | Vendor fix publishedAlpine records a security fix at this version. An absent entry does not mean the package is unaffected. | 5.7.0-r0 | Alpine Security Database ↗Source updated 11 Sep 2026 |
| Alpine v3.23v3.23 · community | runc | Vendor fix publishedAlpine records a security fix at this version. An absent entry does not mean the package is unaffected. | 1.3.3-r0 | Alpine Security Database ↗Source updated 11 Sep 2026 |
| Alpine v3.22v3.22 · community | buildah | Vendor fix publishedAlpine records a security fix at this version. An absent entry does not mean the package is unaffected. | 1.41.6-r0 | Alpine Security Database ↗Source updated 11 Sep 2026 |
| Alpine v3.22v3.22 · community | podman | Vendor fix publishedAlpine records a security fix at this version. An absent entry does not mean the package is unaffected. | 5.6.2-r1 | Alpine Security Database ↗Source updated 11 Sep 2026 |
| Alpine v3.22v3.22 · community | runc | Vendor fix publishedAlpine records a security fix at this version. An absent entry does not mean the package is unaffected. | 1.3.3-r0 | Alpine Security Database ↗Source updated 11 Sep 2026 |
| Debian trixietrixie · source | runc | Affected, no fix publishedDebian currently tracks this release as open. | Not published in this feed | Debian Security Tracker ↗Source updated 5 Oct 2026 |
| Debian bookwormbookworm · source | runc | Affected, no fix publishedDebian currently tracks this release as open. | Not published in this feed | Debian Security Tracker ↗Source updated 5 Oct 2026 |
| Debian forkyforky · source | runc | Vendor fix publishedDebian records a fixed source-package version for this release. | 1.3.3+ds1-2 | Debian Security Tracker ↗Source updated 5 Oct 2026 |
| Debian sidsid · source | runc | Vendor fix publishedDebian records a fixed source-package version for this release. | 1.3.3+ds1-2 | Debian Security Tracker ↗Source updated 5 Oct 2026 |
| Ubuntu 24.04 LTSnoble · standard archive | runc | Under evaluationCanonical reports that the package might be affected and still needs evaluation or fixing. | Not published in this feed | Canonical Ubuntu Security ↗Source updated 5 Oct 2026 |
| Ubuntu 24.04 LTSnoble · standard archive | runc-app | Vendor fix publishedCanonical reports that a fixed source package version has been published. Repository candidate availability is not checked by BlackTree. | 1.3.3-0ubuntu1~24.04.2 | Canonical Ubuntu Security ↗Source updated 5 Oct 2026 |
These OSV and GitHub advisory ranges apply only to the named package and ecosystem. A listed fixed version is not a universal product patch or proof that an update is installed.
| Ecosystem and package | Affected range | First fixed version | Evidence |
|---|---|---|---|
| Gogithub.com/opencontainers/runc | SEMVER: introduced 0; fixed 1.2.8 | 1.2.8 | OSV record ↗aggregator derived · 10 Sep 2026 |
| Gogithub.com/opencontainers/runc | SEMVER: introduced 1.3.0-rc.1; fixed 1.3.3 | 1.3.3 | OSV record ↗aggregator derived · 10 Sep 2026 |
| Gogithub.com/opencontainers/runc | SEMVER: introduced 1.4.0-rc.1; fixed 1.4.0-rc.3 | 1.4.0-rc.3 | OSV record ↗aggregator derived · 10 Sep 2026 |
| Gogithub.com/opencontainers/selinux | SEMVER: introduced 0; fixed 1.13.0 | 1.13.0 | OSV record ↗aggregator derived · 10 Sep 2026 |
| gogithub.com/opencontainers/runc | <= 1.2.7 | 1.2.8 | GitHub advisory ↗upstream repository advisory · 7 Nov 2025 |
| gogithub.com/opencontainers/runc | >= 1.3.0-rc.1, <= 1.3.2 | 1.3.3 | GitHub advisory ↗upstream repository advisory · 7 Nov 2025 |
| gogithub.com/opencontainers/runc | >= 1.4.0-rc.1, <= 1.4.0-rc.2 | 1.4.0-rc.3 | GitHub advisory ↗upstream repository advisory · 7 Nov 2025 |
| gogithub.com/opencontainers/selinux | <= 1.12.0 | 1.13.0 | GitHub advisory ↗upstream repository advisory · 7 Nov 2025 |
Structured product status and remediation from the issuing vendor. Product-state explanations are always visible; large lists can be searched or downloaded.
The vendor explicitly identifies these products as affected by this CVE.
The vendor explicitly identifies these products as affected by this CVE.
High technical severity with public exploit material referenced by a structured source; prioritise exposed affected systems while verifying vendor guidance. Verified remediation exists for at least one product or source, but 2 structured product or package states remain unresolved. Apply remediation only to the exact product branch confirmed by its source.
Fix availability varies by productrunc 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 shared mounts (we have also verified this attack is possible to exploit using a standard Dockerfile with docker buildx build as that also permits triggering parallel execution of containers with custom shared mounts configured). This redirect could be through symbolic links in a tmpfs or theoretically other methods such as regular bind-mounts. While similar, the mitigation applied for the related CVE, CVE-2019-19921, was fairly limited and effectively only caused runc to verify that when LSM labels are written they are actually procfs files. This issue is fixed in versions 1.2.8, 1.3.3, and 1.4.0-rc.3.
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 shared mounts (we have also verified this attack is possible to exploit using a standard Dockerfile with docker buildx build as that also permits triggering parallel execution of containers with custom shared mounts configured). This redirect could be through symbolic links in a tmpfs or theoretically other methods such as regular bind-mounts. While similar, the mitigation applied for the related CVE, CVE-2019-19921, was fairly limited and effectively only caused runc to verify that when LSM labels are written they are actually procfs files. This issue is fixed in versions 1.2.8, 1.3.3, and 1.4.0-rc.3.
The product, when opening a file or directory, does not sufficiently account for when the file is a symbolic link that resolves to a target outside of the intended control sphere. This could allow an attacker to cause the product to operate on unauthorized files.
An attacker operating through local access may attempt exploitation with low privileges. If successful, the issue may cause the confidentiality, integrity or availability impact described by the vendor.
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 shared mounts (we have also verified this attack is possible to exploit using a standard Dockerfile with docker buildx build as that also permits triggering parallel execution of containers with custom shared mounts configured). This redirect could be through symbolic links in a tmpfs or theoretically other methods such as regular bind-mounts. While similar, the mitigation applied for the related CVE, CVE-2019-19921, was fairly limited and effectively only caused runc to verify that when LSM labels are written they are actually procfs files. This issue is fixed in versions 1.2.8, 1.3.3, and 1.4.0-rc.3.
The product, when opening a file or directory, does not sufficiently account for when the file is a symbolic link that resolves to a target outside of the intended control sphere. This could allow an attacker to cause the product to operate on unauthorized files.
An attacker operating through local access may attempt exploitation with low privileges. If successful, the issue may cause the confidentiality, integrity or availability impact described by the vendor.
CVSS severity, EPSS forecast probability, public exploit material and CISA-confirmed exploitation are separate signals.
No CISA KEV match was present at the last successful refresh. This means no confirmation from that source, not proof of no exploitation.
A structured CVE source labels at least one public reference as exploit material. BlackTree has not independently validated that it is safe, reliable or weaponised.
CWE-61: UNIX Symbolic Link (Symlink) Following. The product, when opening a file or directory, does not sufficiently account for when the file is a symbolic link that resolves to a target outside of the intended control sphere. This could allow an attacker to cause the product to operate on unauthorized files.
CVSS:4.0/AV:L/AC:L/AT:P/PR:L/UI:A/VC:H/VI:H/VA:H/SC:H/SI:H/SA:HCommon Vulnerability Scoring System 4.0: the compact vector below is decoded into plain language.
Operational remediation based on structured source evidence.
Published 6 Nov 2025 · Last source change 6 Nov 2025, 21:07 UTC · CWE-61 · UNIX Symbolic Link (Symlink) Following
Core structured fields are present and their contributing authorities are shown above.