<?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>Tue, 06 Oct 2026 19:34:11 +0000</lastBuildDate>
    <item>
      <title>EUVD-2026-260226</title>
      <link>https://cve.radiocsirt.org/vuln/euvd-2026-260226</link>
      <description>EUVD-2026-260226</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/euvd-2026-260226</guid>
    </item>
    <item>
      <title>fkie_cve-2025-62596</title>
      <link>https://cve.radiocsirt.org/vuln/fkie_cve-2025-62596</link>
      <description>&lt;p&gt;Youki is a container runtime written in Rust. In versions 0.5.6 and below, youki’s apparmor handling performs insufficiently strict write-target validation, and when combined with path substitution during pathname resolution, can allow writes to unintended procfs locations. While resolving a path component-by-component, a shared-mount race can substitute intermediate components and redirect the final target. This issue is fixed in version 0.5.7.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;Youki is a container runtime written in Rust. In versions 0.5.6 and below, youki’s apparmor handling performs insufficiently strict write-target validation, and when combined with path substitution during pathname resolution, can allow writes to unintended procfs locations. While resolving a path component-by-component, a shared-mount race can substitute intermediate components and redirect the final target. This issue is fixed in version 0.5.7.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/fkie_cve-2025-62596</guid>
    </item>
    <item>
      <title>GHSA-vf95-55w6-qmrf — youki container escape and denial of service due to arbitrary write gadgets and procfs write redirects</title>
      <link>https://cve.radiocsirt.org/vuln/ghsa-vf95-55w6-qmrf</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; crates.io: youki&lt;/p&gt;
&lt;p&gt;### Impact ###&lt;/p&gt;
&lt;p&gt;youki’s apparmor handling performs insufficiently strict write-target validation, which—combined with path substitution during pathname resolution—can allow writes to unintended procfs locations.&lt;/p&gt;
&lt;p&gt;**Weak write-target check**
youki only verifies that the destination lies somewhere under procfs. As a result, a write intended for `/proc/self/attr/apparmor/exec` can succeed even if the path has been redirected to `/proc/sys/kernel/hostname`(which is also in procfs).&lt;/p&gt;
&lt;p&gt;**Path substitution**
While resolving a path component-by-component, a shared-mount race can substitute intermediate components and redirect the final target.&lt;/p&gt;
&lt;p&gt;This is a different project, but the core logic is similar to the CVE in runc. Issues were identified in runc, and verification was also conducted in youki to confirm the problems.
https://github.com/opencontainers/runc/security/advisories/GHSA-cgrx-mc8f-2prm&lt;/p&gt;
&lt;p&gt;### Credits ###&lt;/p&gt;
&lt;p&gt;Thanks to Li Fubang (@lifubang from acmcoder.com, CIIC) and Tõnis Tiigi (@tonistiigi from Docker) for both independently discovering runc&amp;#39;s original vulnerability, as well as Aleksa Sarai (@cyphar from SUSE) for the original research into this class of security issues and solutions.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; crates.io: youki&lt;/p&gt;
&lt;p&gt;### Impact ###&lt;/p&gt;
&lt;p&gt;youki’s apparmor handling performs insufficiently strict write-target validation, which—combined with path substitution during pathname resolution—can allow writes to unintended procfs locations.&lt;/p&gt;
&lt;p&gt;**Weak write-target check**
youki only verifies that the destination lies somewhere under procfs. As a result, a write intended for `/proc/self/attr/apparmor/exec` can succeed even if the path has been redirected to `/proc/sys/kernel/hostname`(which is also in procfs).&lt;/p&gt;
&lt;p&gt;**Path substitution**
While resolving a path component-by-component, a shared-mount race can substitute intermediate components and redirect the final target.&lt;/p&gt;
&lt;p&gt;This is a different project, but the core logic is similar to the CVE in runc. Issues were identified in runc, and verification was also conducted in youki to confirm the problems.
https://github.com/opencontainers/runc/security/advisories/GHSA-cgrx-mc8f-2prm&lt;/p&gt;
&lt;p&gt;### Credits ###&lt;/p&gt;
&lt;p&gt;Thanks to Li Fubang (@lifubang from acmcoder.com, CIIC) and Tõnis Tiigi (@tonistiigi from Docker) for both independently discovering runc&amp;#39;s original vulnerability, as well as Aleksa Sarai (@cyphar from SUSE) for the original research into this class of security issues and solutions.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/ghsa-vf95-55w6-qmrf</guid>
    </item>
  </channel>
</rss>
