Public mode

No access to your tenant or devices. Every item links to its source. What this means

Sources need attention Customize Public modeDiscuss ChangeIntel on Discord

n/a · Vulnerability

cve-program · severity unknowneuvd · severity unknownCVSS 3.1 · [email protected] · Primary 7.0 HIGHCVSS 2.0 · [email protected] · Primary 4.4 MEDIUMCVSS_V3 Publisher rating MODERATEFixed by github.com/opencontainers/runc 1.0.0-rc9.0.20200122160610-2fc03cc11c77osv · severity unknownFixed by github.com/opencontainers/runc 1.0.0-rc9.0.20200122160610-2fc03cc11c77KEV status unknown

cve-program · CVE-2019-19921

Published

runc through 1.0.0-rc9 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. (This vulnerability does not affect Docker due to an implementation detail that happens to block the attack.)

Read the publisher's advisory

euvd · EUVD-2021-1060

Published

runc through 1.0.0-rc9 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. (This vulnerability does not affect Docker due to an implementation detail that happens to block the attack.)

Read the publisher's advisory

nvd · CVE-2019-19921

Published

runc through 1.0.0-rc9 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. (This vulnerability does not affect Docker due to an implementation detail that happens to block the attack.)

Read the publisher's advisory

osv · GHSA-fh74-hm69-rqjw

Published

### Impact By crafting a malicious root filesystem (with `/proc` being a symlink to a directory which was inside a volume shared with another running container), an attacker in control of both containers can trick `runc` into not correctly configuring the container's security labels and not correctly masking paths inside `/proc` which contain potentially-sensitive information about the host (or even allow for direct attacks against the host). In order to exploit this bug, an untrusted user must be able to spawn custom containers with custom mount configurations (such that a volume is shared between two containers). It should be noted that we consider this to be a fairly high level of access for an untrusted user -- and we do not recommend allowing completely untrusted users to have such degrees of access without further restrictions. ### Specific Go Package Affected github.com/opencontainers/runc/libcontainer ### Patches This vulnerability has been fixed in `1.0.0-rc10`. It should be noted that the current fix is effectively a hot-fix, and there are known ways for it to be worked around (such as making the entire root filesystem a shared volume controlled by another container). We recommend that users review their access policies to ensure that untrusted users do not have such high levels of controls over container mount configuration. ### Workarounds If you are not providing the ability for untrusted users to configure mountpoints for `runc` (or through a higher-level tool such as `docker run -v`) then you are not vulnerable to this issue. This exploit requires fairly complicated levels of access (which are available for some public clouds but are not necessarily available for all deployments). Additionally, it appears as though it is not possible to exploit this vulnerability through Docker (due to the order of mounts Docker generates). However you should not depend on this, as it may be possible to work around this roadblock. ### Credits This vulnerability was discovered by Cure53, as part of a third-party security audit. ### For more information If you have any questions or comments about this advisory: * [Open an issue](https://github.com/opencontainers/runc/issues/new). * Email us at [[email protected]](mailto:[email protected]), or [[email protected]](mailto:[email protected]) if you think you've found a security bug.

Read the publisher's advisory

osv · GO-2021-0087

Published

A race while mounting volumes allows a possible symlink-exchange attack, allowing a user whom can start multiple containers with custom volume mount configurations to escape the container.

Read the publisher's advisory

Affected versions, risk and source history

cve-program · CVE-2019-19921

Published

n/a

Vendor product

Publisher's version information

Shown as published. These rules are not interpreted as NuGet package version ranges.

{
                    "vendor": "n/a",
                    "product": "n/a",
                    "versions": [
                        {
                            "version": "n/a",
                            "status": "affected"
                        }
                    ]
                }

Original source record · Cite this exact observation · Complete original publisher JSON

euvd · EUVD-2021-1060

Published

EUVD source date text has no stated timezone and is retained without inventing a UTC instant. Related bulletin membership is not an alias, common cause or applicability claim. A missing vector with a zero score is treated as unrated. Complete vendor/product and underlying source evidence remains in the original JSON.

Original publisher date fields

datePublished: Feb 12, 2020, 12:00:00 AM

dateUpdated: Aug 5, 2024, 2:32:09 AM

15 related source bulletins · separate from aliases

openSUSE-SU-2024:11358-1: runc-1.0.2-1.2 on GA media

CVE-2016-9962 · CVE-2018-16873 · CVE-2018-16874 · CVE-2018-16875 · CVE-2019-16884 · CVE-2019-19921 · CVE-2019-5736 · CVE-2021-30465

RHSA-2020:1650: Red Hat Security Advisory: container-tools:rhel8 security, bug fix, and enhancement update

CVE-2019-19921 · CVE-2020-1702 · CVE-2020-1726

RHSA-2020:0688: Red Hat Security Advisory: OpenShift Container Platform 4.2.22 runc security update

CVE-2019-19921

WID-SEC-W-2026-2253: IBM Security Verify Access: Mehrere Schwachstellen

CVE-2019-19921 · CVE-2022-48830 · CVE-2022-49024 · CVE-2022-49269 · CVE-2022-49353 · CVE-2022-49357 · CVE-2022-49432 · CVE-2022-49437 · CVE-2022-49443 · CVE-2022-49623 · CVE-2022-49627 · CVE-2022-49643 · CVE-2022-49648 · CVE-2022-49657 · CVE-2022-49670 · CVE-2022-49672 · CVE-2022-49845 · CVE-2023-40403 · CVE-2023-53034 · CVE-2024-29371 · CVE-2024-36350 · CVE-2024-36357 · CVE-2024-46689 · CVE-2024-46744 · CVE-2024-47679 · CVE-2024-47727 · CVE-2024-49570 · CVE-2024-49864 · CVE-2024-50060 · CVE-2024-50195 · CVE-2024-50294 · CVE-2024-52332 · CVE-2024-53052 · CVE-2024-53090 · CVE-2024-53119 · CVE-2024-53135 · CVE-2024-53170 · CVE-2024-53216 · CVE-2024-53229 · CVE-2024-53241 · CVE-2024-53680 · CVE-2024-54456 · CVE-2024-56603 · CVE-2024-56645 · CVE-2024-56662 · CVE-2024-56672 · CVE-2024-56675 · CVE-2024-56690 · CVE-2024-56709 · CVE-2024-56739 · CVE-2024-56786 · CVE-2024-57981 · CVE-2024-57986 · CVE-2024-57987 · CVE-2024-57988 · CVE-2024-57989 · CVE-2024-57990 · CVE-2024-57993 · CVE-2024-57995 · CVE-2024-57998 · CVE-2024-58012 · CVE-2024-58014 · CVE-2024-58015 · CVE-2024-58057 · CVE-2024-58062 · CVE-2024-58068 · CVE-2024-58072 · CVE-2024-58075 · CVE-2024-58077 · CVE-2024-58083 · CVE-2024-58088 · CVE-2025-10158 · CVE-2025-11187 · CVE-2025-12084 · CVE-2025-14104 · CVE-2025-14831 · CVE-2025-14917 · CVE-2025-14923 · CVE-2025-15467 · CVE-2025-15468 · CVE-2025-15469 · CVE-2025-21631 · CVE-2025-21647 · CVE-2025-21648 · CVE-2025-21671 · CVE-2025-21672 · CVE-2025-21691 · CVE-2025-21693 · CVE-2025-21696 · CVE-2025-21702 · CVE-2025-21714 · CVE-2025-21726 · CVE-2025-21728 · CVE-2025-21729 · CVE-2025-21738 · CVE-2025-21739 · CVE-2025-21745 · CVE-2025-21746 · CVE-2025-21765 · CVE-2025-21786 · CVE-2025-21787 · CVE-2025-21790 · CVE-2025-21791 · CVE-2025-21795 · CVE-2025-21796 · CVE-2025-21806 · CVE-2025-21826 · CVE-2025-21828 · CVE-2025-21829 · CVE-2025-21837 · CVE-2025-21839 · CVE-2025-21844 · CVE-2025-21846 · CVE-2025-21847 · CVE-2025-21848 · CVE-2025-21851 · CVE-2025-21853 · CVE-2025-21855 · CVE-2025-21861 · CVE-2025-21863 · CVE-2025-21864 · CVE-2025-22056 · CVE-2025-22097 · CVE-2025-31133 · CVE-2025-37789 · CVE-2025-37819 · CVE-2025-37994 · CVE-2025-38022 · CVE-2025-38024 · CVE-2025-38106 · CVE-2025-38116 · CVE-2025-38129 · CVE-2025-38141 · CVE-2025-38180 · CVE-2025-38206 · CVE-2025-38349 · CVE-2025-38396 · CVE-2025-38403 · CVE-2025-38415 · CVE-2025-38459 · CVE-2025-38730 · CVE-2025-38731 · CVE-2025-39760 · CVE-2025-39806 · CVE-2025-39818 · CVE-2025-39840 · CVE-2025-39843 · CVE-2025-39883 · CVE-2025-40064 · CVE-2025-40096 · CVE-2025-40135 · CVE-2025-40141 · CVE-2025-40158 · CVE-2025-40170 · CVE-2025-40240 · CVE-2025-40248 · CVE-2025-40258 · CVE-2025-40269 · CVE-2025-40271 · CVE-2025-40294 · CVE-2025-40300 · CVE-2025-40304 · CVE-2025-40318 · CVE-2025-40322 · CVE-2025-45582 · CVE-2025-47913 · CVE-2025-52565 · CVE-2025-52881 · CVE-2025-5318 · CVE-2025-59375 · CVE-2025-61662 · CVE-2025-61726 · CVE-2025-61728 · CVE-2025-61729 · CVE-2025-65018 · CVE-2025-66199 · CVE-2025-66418 · CVE-2025-66471 · CVE-2025-68121 · CVE-2025-68160 · CVE-2025-68301 · CVE-2025-68305 · CVE-2025-68349 · CVE-2025-68615 · CVE-2025-68800 · CVE-2025-68811 · CVE-2025-68973 · CVE-2025-69418 · CVE-2025-69419 · CVE-2025-69420 · CVE-2025-69421 · CVE-2025-9086 · CVE-2025-9714 · CVE-2025-9820 · CVE-2026-11904 · CVE-2026-21441 · CVE-2026-22007 · CVE-2026-22013 · CVE-2026-22016 · CVE-2026-22018 · CVE-2026-22021 · CVE-2026-22695 · CVE-2026-22795 · CVE-2026-22796 · CVE-2026-22801 · CVE-2026-22998 · CVE-2026-23001 · CVE-2026-23136 · CVE-2026-23144 · CVE-2026-23171 · CVE-2026-23191 · CVE-2026-23193 · CVE-2026-23204 · CVE-2026-23209 · CVE-2026-23270 · CVE-2026-25646 · CVE-2026-27135 · CVE-2026-31402 · CVE-2026-31431 · CVE-2026-34268 · CVE-2026-35385 · CVE-2026-35386 · CVE-2026-35387 · CVE-2026-35388 · CVE-2026-35414 · CVE-2026-4938 · CVE-2026-5516 · CVE-2026-7364 · CVE-2026-8861

SUSE-SU-2020:0376-1: Security update for docker-runc

CVE-2019-19921

RHSA-2020:0695: Red Hat Security Advisory: OpenShift Container Platform 4.1.38 security update

CVE-2019-19921

SUSE-SU-2021:1458-1: Security update for containerd, docker, runc

CVE-2018-16873 · CVE-2018-16874 · CVE-2018-16875 · CVE-2019-16884 · CVE-2019-19921 · CVE-2019-5736 · CVE-2021-21284 · CVE-2021-21285 · CVE-2021-21334

WID-SEC-W-2026-3046: IBM Concert: Mehrere Schwachstellen

CVE-2019-19921 · CVE-2021-23337 · CVE-2024-3651 · CVE-2024-39338 · CVE-2024-45590 · CVE-2025-13465 · CVE-2025-15284 · CVE-2025-15599 · CVE-2025-22874 · CVE-2025-47273 · CVE-2025-47907 · CVE-2025-52881 · CVE-2025-53643 · CVE-2025-55184 · CVE-2025-58056 · CVE-2025-58188 · CVE-2025-58189 · CVE-2025-61723 · CVE-2025-61730 · CVE-2025-64649 · CVE-2025-64756 · CVE-2025-67221 · CVE-2025-68121 · CVE-2025-68146 · CVE-2026-0540 · CVE-2026-2327 · CVE-2026-23490 · CVE-2026-23897 · CVE-2026-2391 · CVE-2026-23949 · CVE-2026-24486 · CVE-2026-25528 · CVE-2026-25547 · CVE-2026-25639 · CVE-2026-25990 · CVE-2026-26007 · CVE-2026-26019 · CVE-2026-26996 · CVE-2026-27142 · CVE-2026-27212 · CVE-2026-27699 · CVE-2026-27903 · CVE-2026-27904 · CVE-2026-28684 · CVE-2026-29063 · CVE-2026-29181 · CVE-2026-2950 · CVE-2026-31808 · CVE-2026-31900 · CVE-2026-32274 · CVE-2026-32288 · CVE-2026-32597 · CVE-2026-32630 · CVE-2026-32887 · CVE-2026-32952 · CVE-2026-33186 · CVE-2026-33532 · CVE-2026-33750 · CVE-2026-33814 · CVE-2026-33816 · CVE-2026-33916 · CVE-2026-34043 · CVE-2026-34073 · CVE-2026-34077 · CVE-2026-3520 · CVE-2026-35469 · CVE-2026-35515 · CVE-2026-3627 · CVE-2026-39823 · CVE-2026-39825 · CVE-2026-39826 · CVE-2026-39892 · CVE-2026-39984 · CVE-2026-40175 · CVE-2026-40179 · CVE-2026-40181 · CVE-2026-40190 · CVE-2026-40347 · CVE-2026-41066 · CVE-2026-41182 · CVE-2026-41238 · CVE-2026-41239 · CVE-2026-41240 · CVE-2026-41305 · CVE-2026-41324 · CVE-2026-41425 · CVE-2026-41481 · CVE-2026-41488 · CVE-2026-41602 · CVE-2026-41636 · CVE-2026-42151 · CVE-2026-42154 · CVE-2026-42198 · CVE-2026-42211 · CVE-2026-42338 · CVE-2026-42342 · CVE-2026-42561 · CVE-2026-42577 · CVE-2026-43870 · CVE-2026-44405 · CVE-2026-44431 · CVE-2026-44432 · CVE-2026-44486 · CVE-2026-44487 · CVE-2026-44488 · CVE-2026-44492 · CVE-2026-44494 · CVE-2026-44496 · CVE-2026-44728 · CVE-2026-4539 · CVE-2026-45409 · CVE-2026-45736 · CVE-2026-46625 · CVE-2026-4800 · CVE-2026-4923 · CVE-2026-4926 · CVE-2026-7246 · CVE-2026-8723

WID-SEC-W-2022-1089: Red Hat OpenShift Container Platform: Mehrere Schwachstellen

CVE-2019-19921 · CVE-2020-1726 · CVE-2020-8945

RHSA-2020:0942: Red Hat Security Advisory: runc security update

CVE-2019-19921

RHSA-2020:1485: Red Hat Security Advisory: OpenShift Container Platform 4.3.13 runc security update

CVE-2019-19921

openSUSE-SU-2020:0219-1: Security update for docker-runc

CVE-2019-19921

RHBA-2020:0581: Red Hat Bug Fix Advisory: OpenShift Container Platform 4.4 image release advisory

CVE-2019-19335 · CVE-2019-19351 · CVE-2019-19355 · CVE-2019-19921 · CVE-2020-1726 · CVE-2020-2099 · CVE-2020-2100 · CVE-2020-2101 · CVE-2020-2102 · CVE-2020-2103 · CVE-2020-2104 · CVE-2020-2105 · CVE-2020-8551 · CVE-2020-8552 · CVE-2020-8945 · CVE-2020-10696

SUSE-SU-2020:0944-1: Security update for runc

CVE-2019-19921

SUSE-SU-2020:0375-1: Security update for docker-runc

CVE-2019-19921

No normalized affected-package data is projected for this source revision. The original publisher record may contain additional product and version evidence; this does not establish that a package is unaffected.

Original source record · Cite this exact observation · Complete original publisher JSON

nvd · CVE-2019-19921

Published

NVD analysis and CPE criteria are source context, not proof that a package or your environment is affected. Complete affected data, logical configurations and SSVC are retained in the original JSON.

Source analysis status: Modified

Weakness classifications: CWE-706

Original publisher date fields

published: 2020-02-12T15:15:12.210

lastModified: 2026-06-17T02:27:27.390

17 source CPE criteria · context only
  • cpe:2.3:a:linuxfoundation:runc:*:*:*:*:*:*:*:*
  • cpe:2.3:a:linuxfoundation:runc:1.0.0:rc1:*:*:*:*:*:*
  • cpe:2.3:a:linuxfoundation:runc:1.0.0:rc2:*:*:*:*:*:*
  • cpe:2.3:a:linuxfoundation:runc:1.0.0:rc3:*:*:*:*:*:*
  • cpe:2.3:a:linuxfoundation:runc:1.0.0:rc4:*:*:*:*:*:*
  • cpe:2.3:a:linuxfoundation:runc:1.0.0:rc5:*:*:*:*:*:*
  • cpe:2.3:a:linuxfoundation:runc:1.0.0:rc6:*:*:*:*:*:*
  • cpe:2.3:a:linuxfoundation:runc:1.0.0:rc7:*:*:*:*:*:*
  • cpe:2.3:a:linuxfoundation:runc:1.0.0:rc8:*:*:*:*:*:*
  • cpe:2.3:a:linuxfoundation:runc:1.0.0:rc9:*:*:*:*:*:*
  • cpe:2.3:o:debian:debian_linux:9.0:*:*:*:*:*:*:*
  • cpe:2.3:o:debian:debian_linux:10.0:*:*:*:*:*:*:*
  • cpe:2.3:o:opensuse:leap:15.1:*:*:*:*:*:*:*
  • cpe:2.3:o:canonical:ubuntu_linux:18.04:*:*:*:lts:*:*:*
  • cpe:2.3:o:canonical:ubuntu_linux:19.10:*:*:*:*:*:*:*
  • cpe:2.3:a:redhat:openshift_container_platform:4.1:*:*:*:*:*:*:*
  • cpe:2.3:a:redhat:openshift_container_platform:4.2:*:*:*:*:*:*:*

The original JSON retains the logical configuration operators, exclusions and version bounds.

No normalized affected-package data is projected for this source revision. The original publisher record may contain additional product and version evidence; this does not establish that a package is unaffected.

Original source record · Cite this exact observation · Complete original publisher JSON

osv · GHSA-fh74-hm69-rqjw

Published

github.com/opencontainers/runc

Go

SEMVER · introduced 0 → fixed 1.0.0-rc9.0.20200122160610-2fc03cc11c77

Original source record · Cite this exact observation · Complete original publisher JSON

osv · GO-2021-0087

Published

github.com/opencontainers/runc

Go

SEMVER · introduced 0 → fixed 1.0.0-rc9.0.20200122160610-2fc03cc11c77

Original source record · Cite this exact observation · Complete original publisher JSON

ChangeIntel

An IT change radar: releases, security, known issues, retirements, documentation changes, and service status from public sources. Every item links to supporting evidence; dates and statuses can change after they are read.

Sources read 18 Nov 02:26 UTC · 273 of 275 readable · 249 fully read · 20 waiting for GitHub's hourly limit · documentation 469/469 current