BlackTreeCVE IntelligenceUnknown · Unknown
High technical severity with public exploit material referenced by a structured source; prioritise exposed affected systems while verifying vendor guidance.
Alpine, Debian findings are scoped to the named distribution, release and source package. An absent finding does not mean a package is unaffected.
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 | runc | Vendor fix publishedAlpine records a security fix at this version. An absent entry does not mean the package is unaffected. | 1.1.4-r0, 1.1.4-r7 | 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.1.4-r0, 1.1.4-r7 | Alpine Security Database ↗Source updated 11 Sep 2026 |
| Alpine v3.21v3.21 · community | runc | Vendor fix publishedAlpine records a security fix at this version. An absent entry does not mean the package is unaffected. | 1.1.4-r0, 1.1.4-r7 | Alpine Security Database ↗Source updated 19 Aug 2026 |
| Debian trixietrixie · source | runc | Vendor fix publishedDebian records a fixed source-package version for this release. | 1.1.5+ds1-1 | Debian Security Tracker ↗Source updated 5 Oct 2026 |
| Debian bookwormbookworm · source | runc | Vendor fix publishedDebian records a fixed source-package version for this release. | 1.1.5+ds1-1 | 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.1.5+ds1-1 | 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.1.5+ds1-1 | Debian Security Tracker ↗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 | >= 1.0.0-rc95, < 1.1.5 | 1.1.5 | GitHub advisory ↗github reviewed aggregator · 6 Dec 2024 |
High technical severity with public exploit material referenced by a structured source; prioritise exposed affected systems while verifying vendor guidance.
Fix not verifiedrunc through 1.1.4 has Incorrect Access Control leading to Escalation of Privileges, related to libcontainer/rootfs_linux.go. To exploit this, an attacker must be able to spawn two containers with custom volume-mount configurations, and be able to run custom images. NOTE: this issue exists because of a CVE-2019-19921 regression.
runc through 1.1.4 has Incorrect Access Control leading to Escalation of Privileges, related to libcontainer/rootfs_linux.go. To exploit this, an attacker must be able to spawn two containers with custom volume-mount configurations, and be able to run custom images. NOTE: this issue exists because of a CVE-2019-19921 regression.
The product uses a name or reference to access a resource, but the name/reference resolves to a resource that is outside of the intended control sphere.
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 through 1.1.4 has Incorrect Access Control leading to Escalation of Privileges, related to libcontainer/rootfs_linux.go. To exploit this, an attacker must be able to spawn two containers with custom volume-mount configurations, and be able to run custom images. NOTE: this issue exists because of a CVE-2019-19921 regression.
The product uses a name or reference to access a resource, but the name/reference resolves to a resource that is outside of the intended control sphere.
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-706: Use of Incorrectly-Resolved Name or Reference. The product uses a name or reference to access a resource, but the name/reference resolves to a resource that is outside of the intended control sphere.
CVSS:3.1/AV:L/AC:H/PR:L/UI:N/S:U/C:H/I:H/A:HCommon Vulnerability Scoring System 3.1: the compact vector below is decoded into plain language.
Operational remediation based on structured source evidence.
Published 3 Mar 2023 · Last source change 16 Dec 2025, 20:02 UTC · CWE-706 · Use of Incorrectly-Resolved Name or Reference
Missing structured fields: affected product. Missing data is not evidence of low risk; review the primary advisory.
No material field changes have been recorded since change tracking began. Routine source refreshes and cosmetic edits are intentionally excluded.