<?xml version='1.0' encoding='UTF-8'?>
<?xml-stylesheet href="/static/style.xsl" type="text/xsl"?>
<rss xmlns:atom="http://www.w3.org/2005/Atom" xmlns:content="http://purl.org/rss/1.0/modules/content/" version="2.0">
  <channel>
    <title>Most recent entries from all</title>
    <link>https://cve.radiocsirt.org</link>
    <description>Contains only the most 10 recent entries.</description>
    <docs>http://www.rssboard.org/rss-specification</docs>
    <generator>python-feedgen</generator>
    <language>en</language>
    <lastBuildDate>Sat, 03 Oct 2026 01:39:39 +0000</lastBuildDate>
    <item>
      <title>ALSA-2019:0975 — Important: container-tools:rhel8 security and bug fix update</title>
      <link>https://cve.radiocsirt.org/vuln/alsa-2019:0975</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; AlmaLinux:8: oci-systemd-hook, AlmaLinux:8: oci-umount&lt;/p&gt;
&lt;p&gt;The container-tools module contains tools for working with containers, notably podman, buildah, skopeo, and runc.&lt;/p&gt;
&lt;p&gt;Security Fix(es):&lt;/p&gt;
&lt;p&gt;* A flaw was found in the way runc handled system file descriptors when running containers. A malicious container could use this flaw to overwrite contents of the runc binary and consequently run arbitrary commands on the container host system. (CVE-2019-5736)&lt;/p&gt;
&lt;p&gt;For more details about the security issue(s), including the impact, a CVSS score, acknowledgments, and other related information, refer to the CVE page(s) listed in the References section.&lt;/p&gt;
&lt;p&gt;Bug Fix(es):&lt;/p&gt;
&lt;p&gt;* [stream rhel8] rebase container-selinux to 2.94 (BZ#1693675)&lt;/p&gt;
&lt;p&gt;* [stream rhel8] unable to mount disk at `/var/lib/containers` via `systemd` unit when `container-selinux` policy installed (BZ#1695669)&lt;/p&gt;
&lt;p&gt;* [stream rhel8] don&amp;#39;t allow a container to connect to random services (BZ#1695689)&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; AlmaLinux:8: oci-systemd-hook, AlmaLinux:8: oci-umount&lt;/p&gt;
&lt;p&gt;The container-tools module contains tools for working with containers, notably podman, buildah, skopeo, and runc.&lt;/p&gt;
&lt;p&gt;Security Fix(es):&lt;/p&gt;
&lt;p&gt;* A flaw was found in the way runc handled system file descriptors when running containers. A malicious container could use this flaw to overwrite contents of the runc binary and consequently run arbitrary commands on the container host system. (CVE-2019-5736)&lt;/p&gt;
&lt;p&gt;For more details about the security issue(s), including the impact, a CVSS score, acknowledgments, and other related information, refer to the CVE page(s) listed in the References section.&lt;/p&gt;
&lt;p&gt;Bug Fix(es):&lt;/p&gt;
&lt;p&gt;* [stream rhel8] rebase container-selinux to 2.94 (BZ#1693675)&lt;/p&gt;
&lt;p&gt;* [stream rhel8] unable to mount disk at `/var/lib/containers` via `systemd` unit when `container-selinux` policy installed (BZ#1695669)&lt;/p&gt;
&lt;p&gt;* [stream rhel8] don&amp;#39;t allow a container to connect to random services (BZ#1695689)&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/alsa-2019:0975</guid>
    </item>
    <item>
      <title>bdu:2019-00826</title>
      <link>https://cve.radiocsirt.org/vuln/bdu:2019-00826</link>
      <description>bdu:2019-00826</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/bdu:2019-00826</guid>
    </item>
    <item>
      <title>Withdrawn: BELL-CVE-2019-5736 — CVE-2019-5736 does not affect BellSoft software</title>
      <link>https://cve.radiocsirt.org/vuln/bell-cve-2019-5736</link>
      <description>&lt;p&gt;&lt;strong&gt;Withdrawn by the publisher.&lt;/strong&gt;&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Withdrawn by the publisher.&lt;/strong&gt;&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/bell-cve-2019-5736</guid>
    </item>
    <item>
      <title>certfr-2019-avi-070 — Une vulnérabilité a été découverte dans les produits VMware. Elle permet
à un attaquant de provoquer une exécution de c…</title>
      <link>https://cve.radiocsirt.org/vuln/certfr-2019-avi-070</link>
      <description>certfr-2019-avi-070</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/certfr-2019-avi-070</guid>
    </item>
    <item>
      <title>cisco-sa-20190215-runc — Container Privilege Escalation Vulnerability Affecting Cisco Products: February 2019</title>
      <link>https://cve.radiocsirt.org/vuln/cisco-sa-20190215-runc</link>
      <description>&lt;p&gt;A vulnerability in the Open Container Initiative runc CLI tool used by multiple products could allow an unauthenticated, remote attacker to escalate privileges on a targeted system.&#13;
&#13;
The vulnerability exists because the affected software improperly handles file descriptors related to /proc/self/exe. An attacker could exploit the vulnerability either by persuading a user to create a new container using an attacker-controlled image or by using the docker exec command to attach into an existing container that the attacker already has write access to. A successful exploit could allow the attacker to overwrite the host&amp;#39;s runc binary file with a malicious file, escape the container, and execute arbitrary commands with root privileges on the host system.&#13;
&#13;
This advisory will be updated as additional information becomes available.&#13;
&#13;
This advisory is available at the following link:&#13;
https://sec.cloudapps.cisco.com/security/center/content/CiscoSecurityAdvisory/cisco-sa-20190215-runc [&amp;#34;https://sec.cloudapps.cisco.com/security/center/content/CiscoSecurityAdvisory/cisco-sa-20190215-runc&amp;#34;]&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;A vulnerability in the Open Container Initiative runc CLI tool used by multiple products could allow an unauthenticated, remote attacker to escalate privileges on a targeted system.&#13;
&#13;
The vulnerability exists because the affected software improperly handles file descriptors related to /proc/self/exe. An attacker could exploit the vulnerability either by persuading a user to create a new container using an attacker-controlled image or by using the docker exec command to attach into an existing container that the attacker already has write access to. A successful exploit could allow the attacker to overwrite the host&amp;#39;s runc binary file with a malicious file, escape the container, and execute arbitrary commands with root privileges on the host system.&#13;
&#13;
This advisory will be updated as additional information becomes available.&#13;
&#13;
This advisory is available at the following link:&#13;
https://sec.cloudapps.cisco.com/security/center/content/CiscoSecurityAdvisory/cisco-sa-20190215-runc [&amp;#34;https://sec.cloudapps.cisco.com/security/center/content/CiscoSecurityAdvisory/cisco-sa-20190215-runc&amp;#34;]&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/cisco-sa-20190215-runc</guid>
    </item>
    <item>
      <title>CLEANSTART-2026-BP85403 — Security fix for CVE-2019-5736 applied in: runc 1.0.0_rc7-r0</title>
      <link>https://cve.radiocsirt.org/vuln/cleanstart-2026-bp85403</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; CleanStart: runc&lt;/p&gt;
&lt;p&gt;Security vulnerability affects the runc package. This issue is resolved in later releases. See references for vulnerability details.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; CleanStart: runc&lt;/p&gt;
&lt;p&gt;Security vulnerability affects the runc package. This issue is resolved in later releases. See references for vulnerability details.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/cleanstart-2026-bp85403</guid>
    </item>
    <item>
      <title>EUVD-2026-50405</title>
      <link>https://cve.radiocsirt.org/vuln/euvd-2026-50405</link>
      <description>EUVD-2026-50405</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/euvd-2026-50405</guid>
    </item>
    <item>
      <title>fkie_cve-2019-5736</title>
      <link>https://cve.radiocsirt.org/vuln/fkie_cve-2019-5736</link>
      <description>&lt;p&gt;runc through 1.0-rc6, as used in Docker before 18.09.2 and other products, allows attackers to overwrite the host runc binary (and consequently obtain host root access) by leveraging the ability to execute a command as root within one of these types of containers: (1) a new container with an attacker-controlled image, or (2) an existing container, to which the attacker previously had write access, that can be attached with docker exec. This occurs because of file-descriptor mishandling, related to /proc/self/exe.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;runc through 1.0-rc6, as used in Docker before 18.09.2 and other products, allows attackers to overwrite the host runc binary (and consequently obtain host root access) by leveraging the ability to execute a command as root within one of these types of containers: (1) a new container with an attacker-controlled image, or (2) an existing container, to which the attacker previously had write access, that can be attached with docker exec. This occurs because of file-descriptor mishandling, related to /proc/self/exe.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/fkie_cve-2019-5736</guid>
    </item>
    <item>
      <title>GHSA-gxmr-w5mj-v8hh</title>
      <link>https://cve.radiocsirt.org/vuln/ghsa-gxmr-w5mj-v8hh</link>
      <description>&lt;p&gt;runc through 1.0-rc6, as used in Docker before 18.09.2 and other products, allows attackers to overwrite the host runc binary (and consequently obtain host root access) by leveraging the ability to execute a command as root within one of these types of containers: (1) a new container with an attacker-controlled image, or (2) an existing container, to which the attacker previously had write access, that can be attached with docker exec. This occurs because of file-descriptor mishandling, related to /proc/self/exe.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;runc through 1.0-rc6, as used in Docker before 18.09.2 and other products, allows attackers to overwrite the host runc binary (and consequently obtain host root access) by leveraging the ability to execute a command as root within one of these types of containers: (1) a new container with an attacker-controlled image, or (2) an existing container, to which the attacker previously had write access, that can be attached with docker exec. This occurs because of file-descriptor mishandling, related to /proc/self/exe.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/ghsa-gxmr-w5mj-v8hh</guid>
    </item>
    <item>
      <title>gsd-2019-5736</title>
      <link>https://cve.radiocsirt.org/vuln/gsd-2019-5736</link>
      <description>gsd-2019-5736</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/gsd-2019-5736</guid>
    </item>
    <item>
      <title>msrc_CVE-2019-5736 — runc through 1.0-rc6 as used in Docker before 18.09.2 and other products allows attackers to overwrite the host runc bi…</title>
      <link>https://cve.radiocsirt.org/vuln/msrc_cve-2019-5736</link>
      <description>msrc_CVE-2019-5736</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/msrc_cve-2019-5736</guid>
    </item>
    <item>
      <title>openSUSE-SU-2019:0252-1 — Security update for docker-runc</title>
      <link>https://cve.radiocsirt.org/vuln/opensuse-su-2019:0252-1</link>
      <description>&lt;p&gt;Security update for docker-runc&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;Security update for docker-runc&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/opensuse-su-2019:0252-1</guid>
    </item>
    <item>
      <title>RHSA-2019:0303 — Red Hat Security Advisory: runc security update</title>
      <link>https://cve.radiocsirt.org/vuln/rhsa-2019:0303</link>
      <description>&lt;p&gt;runc: Execution of malicious containers allows for container escape and access to host filesystem&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;runc: Execution of malicious containers allows for container escape and access to host filesystem&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/rhsa-2019:0303</guid>
    </item>
    <item>
      <title>SUSE-SU-2019:0362-1 — Security update for docker-runc</title>
      <link>https://cve.radiocsirt.org/vuln/suse-su-2019:0362-1</link>
      <description>&lt;p&gt;Security update for docker-runc&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;Security update for docker-runc&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/suse-su-2019:0362-1</guid>
    </item>
    <item>
      <title>UBUNTU-CVE-2019-5736</title>
      <link>https://cve.radiocsirt.org/vuln/ubuntu-cve-2019-5736</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Ubuntu:16.04:LTS: docker.io, Ubuntu:16.04:LTS: runc, Ubuntu:18.04:LTS: docker.io, Ubuntu:18.04:LTS: runc&lt;/p&gt;
&lt;p&gt;runc through 1.0-rc6, as used in Docker before 18.09.2 and other products, allows attackers to overwrite the host runc binary (and consequently obtain host root access) by leveraging the ability to execute a command as root within one of these types of containers: (1) a new container with an attacker-controlled image, or (2) an existing container, to which the attacker previously had write access, that can be attached with docker exec. This occurs because of file-descriptor mishandling, related to /proc/self/exe.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Ubuntu:16.04:LTS: docker.io, Ubuntu:16.04:LTS: runc, Ubuntu:18.04:LTS: docker.io, Ubuntu:18.04:LTS: runc&lt;/p&gt;
&lt;p&gt;runc through 1.0-rc6, as used in Docker before 18.09.2 and other products, allows attackers to overwrite the host runc binary (and consequently obtain host root access) by leveraging the ability to execute a command as root within one of these types of containers: (1) a new container with an attacker-controlled image, or (2) an existing container, to which the attacker previously had write access, that can be attached with docker exec. This occurs because of file-descriptor mishandling, related to /proc/self/exe.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/ubuntu-cve-2019-5736</guid>
    </item>
  </channel>
</rss>
