<?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 14:37:40 +0000</lastBuildDate>
    <item>
      <title>EUVD-2026-272999</title>
      <link>https://cve.radiocsirt.org/vuln/euvd-2026-272999</link>
      <description>EUVD-2026-272999</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/euvd-2026-272999</guid>
    </item>
    <item>
      <title>fkie_cve-2024-22036</title>
      <link>https://cve.radiocsirt.org/vuln/fkie_cve-2024-22036</link>
      <description>&lt;p&gt;A vulnerability has been identified within Rancher where a cluster or node driver can be used to escape the chroot
 jail and gain root access to the Rancher container itself. In 
production environments, further privilege escalation is possible based 
on living off the land within the Rancher container itself. For the test
 and development environments, based on a –privileged Docker container, 
it is possible to escape the Docker container and gain execution access 
on the host system.&lt;/p&gt;
&lt;p&gt;This issue affects rancher: from 2.7.0 before 2.7.16, from 2.8.0 before 2.8.9, from 2.9.0 before 2.9.3.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;A vulnerability has been identified within Rancher where a cluster or node driver can be used to escape the chroot
 jail and gain root access to the Rancher container itself. In 
production environments, further privilege escalation is possible based 
on living off the land within the Rancher container itself. For the test
 and development environments, based on a –privileged Docker container, 
it is possible to escape the Docker container and gain execution access 
on the host system.&lt;/p&gt;
&lt;p&gt;This issue affects rancher: from 2.7.0 before 2.7.16, from 2.8.0 before 2.8.9, from 2.9.0 before 2.9.3.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/fkie_cve-2024-22036</guid>
    </item>
    <item>
      <title>GHSA-h99m-6755-rgwc — Rancher Remote Code Execution via Cluster/Node Drivers</title>
      <link>https://cve.radiocsirt.org/vuln/ghsa-h99m-6755-rgwc</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Go: github.com/rancher/rancher&lt;/p&gt;
&lt;p&gt;### Impact
A vulnerability has been identified within Rancher where a cluster or node driver can be used to escape the `chroot` jail and gain root access to the Rancher container itself. In production environments, further privilege escalation is possible based on living off the land within the Rancher container itself. For the test and development environments, based on a –privileged Docker container, it is possible to escape the Docker container and gain execution access on the host system.&lt;/p&gt;
&lt;p&gt;This happens because:
- During startup, Rancher appends the `/opt/drivers/management-state/bin` directory to the `PATH` environment variable.
- In Rancher, the binaries `/usr/bin/rancher-machine`, `/usr/bin/helm_v3`, and `/usr/bin/kustomize` are assigned a UID of 1001 and a GID of 127 instead of being owned by the root user.
- Rancher employs a jail mechanism to isolate the execution of node drivers from the main process. However, the drivers are executed with excessive permissions.
- During the registration of new node drivers, its binary is executed with the same user as the parent process, which could enable an attacker to gain elevated privileges by registering a malicious driver.
- Lack of validation on the driver file type, which allows symbolic links to be used.&lt;/p&gt;
&lt;p&gt;Please consult the associated  [MITRE ATT&amp;amp;CK - Technique - Privilege Escalation](https://attack.mitre.org/tactics/TA0004/) and [MITRE ATT&amp;amp;CK - Technique - Execution](https://attack.mitre.org/tactics/TA0002/) for furth…&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Go: github.com/rancher/rancher&lt;/p&gt;
&lt;p&gt;### Impact
A vulnerability has been identified within Rancher where a cluster or node driver can be used to escape the `chroot` jail and gain root access to the Rancher container itself. In production environments, further privilege escalation is possible based on living off the land within the Rancher container itself. For the test and development environments, based on a –privileged Docker container, it is possible to escape the Docker container and gain execution access on the host system.&lt;/p&gt;
&lt;p&gt;This happens because:
- During startup, Rancher appends the `/opt/drivers/management-state/bin` directory to the `PATH` environment variable.
- In Rancher, the binaries `/usr/bin/rancher-machine`, `/usr/bin/helm_v3`, and `/usr/bin/kustomize` are assigned a UID of 1001 and a GID of 127 instead of being owned by the root user.
- Rancher employs a jail mechanism to isolate the execution of node drivers from the main process. However, the drivers are executed with excessive permissions.
- During the registration of new node drivers, its binary is executed with the same user as the parent process, which could enable an attacker to gain elevated privileges by registering a malicious driver.
- Lack of validation on the driver file type, which allows symbolic links to be used.&lt;/p&gt;
&lt;p&gt;Please consult the associated  [MITRE ATT&amp;amp;CK - Technique - Privilege Escalation](https://attack.mitre.org/tactics/TA0004/) and [MITRE ATT&amp;amp;CK - Technique - Execution](https://attack.mitre.org/tactics/TA0002/) for furth…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/ghsa-h99m-6755-rgwc</guid>
    </item>
    <item>
      <title>gsd-2024-22036</title>
      <link>https://cve.radiocsirt.org/vuln/gsd-2024-22036</link>
      <description>gsd-2024-22036</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/gsd-2024-22036</guid>
    </item>
    <item>
      <title>openSUSE-SU-2024:0350-1 — Security update for govulncheck-vulndb</title>
      <link>https://cve.radiocsirt.org/vuln/opensuse-su-2024:0350-1</link>
      <description>&lt;p&gt;Security update for govulncheck-vulndb&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;Security update for govulncheck-vulndb&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/opensuse-su-2024:0350-1</guid>
    </item>
    <item>
      <title>SUSE-SU-2024:3911-1 — Security update for govulncheck-vulndb</title>
      <link>https://cve.radiocsirt.org/vuln/suse-su-2024:3911-1</link>
      <description>&lt;p&gt;Security update for govulncheck-vulndb&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;Security update for govulncheck-vulndb&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/suse-su-2024:3911-1</guid>
    </item>
    <item>
      <title>WID-SEC-W-2024-3273 — Rancher: Mehrere Schwachstellen</title>
      <link>https://cve.radiocsirt.org/vuln/wid-sec-w-2024-3273</link>
      <description>&lt;p&gt;Ein entfernter, authentisierter Angreifer kann mehrere Schwachstellen in Rancher ausnutzen, um Informationen offenzulegen, erhöhte Rechte zu erlangen und beliebigen Code auszuführen.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;Ein entfernter, authentisierter Angreifer kann mehrere Schwachstellen in Rancher ausnutzen, um Informationen offenzulegen, erhöhte Rechte zu erlangen und beliebigen Code auszuführen.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/wid-sec-w-2024-3273</guid>
    </item>
  </channel>
</rss>
