<?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>Sun, 04 Oct 2026 00:50:05 +0000</lastBuildDate>
    <item>
      <title>BREW-codelimit-CVE-2026-54552 — sh _uid does not drop supplementary groups (incomplete privilege drop)</title>
      <link>https://cve.radiocsirt.org/vuln/brew-codelimit-cve-2026-54552</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Homebrew: codelimit&lt;/p&gt;
&lt;p&gt;### Impact
The `_uid` option performed an incomplete privilege drop on Linux/Unix-like systems.&lt;/p&gt;
&lt;p&gt;When `sh` was run from a process with elevated privileges, such as root, and a command was launched with `_uid=&amp;lt;unprivileged user&amp;gt;`, the child process changed its UID and primary GID but did not reset its supplementary groups. As a result, the child process could retain the parent process’s supplementary groups, potentially including privileged groups such as root, docker, disk, shadow, or sudo.&lt;/p&gt;
&lt;p&gt;This could allow a subprocess that was expected to run with reduced privileges to access files or resources available to the original process’s supplementary groups. Users are impacted if they rely on `_uid` as a privilege boundary when launching commands from a privileged parent process.&lt;/p&gt;
&lt;p&gt;### Patches
Upgrade to version &amp;gt;= 2.2.4&lt;/p&gt;
&lt;p&gt;### Workarounds
Avoid using `_uid` when the user represents a less-privileged user.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Homebrew: codelimit&lt;/p&gt;
&lt;p&gt;### Impact
The `_uid` option performed an incomplete privilege drop on Linux/Unix-like systems.&lt;/p&gt;
&lt;p&gt;When `sh` was run from a process with elevated privileges, such as root, and a command was launched with `_uid=&amp;lt;unprivileged user&amp;gt;`, the child process changed its UID and primary GID but did not reset its supplementary groups. As a result, the child process could retain the parent process’s supplementary groups, potentially including privileged groups such as root, docker, disk, shadow, or sudo.&lt;/p&gt;
&lt;p&gt;This could allow a subprocess that was expected to run with reduced privileges to access files or resources available to the original process’s supplementary groups. Users are impacted if they rely on `_uid` as a privilege boundary when launching commands from a privileged parent process.&lt;/p&gt;
&lt;p&gt;### Patches
Upgrade to version &amp;gt;= 2.2.4&lt;/p&gt;
&lt;p&gt;### Workarounds
Avoid using `_uid` when the user represents a less-privileged user.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/brew-codelimit-cve-2026-54552</guid>
    </item>
    <item>
      <title>EUVD-2026-355142</title>
      <link>https://cve.radiocsirt.org/vuln/euvd-2026-355142</link>
      <description>EUVD-2026-355142</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/euvd-2026-355142</guid>
    </item>
    <item>
      <title>fkie_cve-2026-54552</title>
      <link>https://cve.radiocsirt.org/vuln/fkie_cve-2026-54552</link>
      <description>&lt;p&gt;sh provides Python process launching. Prior to 2.2.4, the _uid option in sh.py performs an incomplete privilege drop on Linux and Unix-like systems. When sh runs from an elevated process and launches a command with _uid set to an unprivileged user, the child changes its UID but can retain the parent process&amp;#39;s supplementary groups because the privilege-drop sequence does not fully establish the target user&amp;#39;s UID, primary GID, and supplementary groups. The child can therefore retain access to files or resources granted to privileged groups such as root, docker, disk, shadow, or sudo, violating the expected _uid privilege boundary. This issue is fixed in version 2.2.4.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;sh provides Python process launching. Prior to 2.2.4, the _uid option in sh.py performs an incomplete privilege drop on Linux and Unix-like systems. When sh runs from an elevated process and launches a command with _uid set to an unprivileged user, the child changes its UID but can retain the parent process&amp;#39;s supplementary groups because the privilege-drop sequence does not fully establish the target user&amp;#39;s UID, primary GID, and supplementary groups. The child can therefore retain access to files or resources granted to privileged groups such as root, docker, disk, shadow, or sudo, violating the expected _uid privilege boundary. This issue is fixed in version 2.2.4.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/fkie_cve-2026-54552</guid>
    </item>
    <item>
      <title>GHSA-q38v-wp89-2w55 — sh _uid does not drop supplementary groups (incomplete privilege drop)</title>
      <link>https://cve.radiocsirt.org/vuln/ghsa-q38v-wp89-2w55</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; PyPI: sh&lt;/p&gt;
&lt;p&gt;### Impact
The `_uid` option performed an incomplete privilege drop on Linux/Unix-like systems.&lt;/p&gt;
&lt;p&gt;When `sh` was run from a process with elevated privileges, such as root, and a command was launched with `_uid=&amp;lt;unprivileged user&amp;gt;`, the child process changed its UID and primary GID but did not reset its supplementary groups. As a result, the child process could retain the parent process’s supplementary groups, potentially including privileged groups such as root, docker, disk, shadow, or sudo.&lt;/p&gt;
&lt;p&gt;This could allow a subprocess that was expected to run with reduced privileges to access files or resources available to the original process’s supplementary groups. Users are impacted if they rely on `_uid` as a privilege boundary when launching commands from a privileged parent process.&lt;/p&gt;
&lt;p&gt;### Patches
Upgrade to version &amp;gt;= 2.2.4&lt;/p&gt;
&lt;p&gt;### Workarounds
Avoid using `_uid` when the user represents a less-privileged user.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; PyPI: sh&lt;/p&gt;
&lt;p&gt;### Impact
The `_uid` option performed an incomplete privilege drop on Linux/Unix-like systems.&lt;/p&gt;
&lt;p&gt;When `sh` was run from a process with elevated privileges, such as root, and a command was launched with `_uid=&amp;lt;unprivileged user&amp;gt;`, the child process changed its UID and primary GID but did not reset its supplementary groups. As a result, the child process could retain the parent process’s supplementary groups, potentially including privileged groups such as root, docker, disk, shadow, or sudo.&lt;/p&gt;
&lt;p&gt;This could allow a subprocess that was expected to run with reduced privileges to access files or resources available to the original process’s supplementary groups. Users are impacted if they rely on `_uid` as a privilege boundary when launching commands from a privileged parent process.&lt;/p&gt;
&lt;p&gt;### Patches
Upgrade to version &amp;gt;= 2.2.4&lt;/p&gt;
&lt;p&gt;### Workarounds
Avoid using `_uid` when the user represents a less-privileged user.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/ghsa-q38v-wp89-2w55</guid>
    </item>
    <item>
      <title>openSUSE-SU-2026:11372-1 — python313-sh-2.3.0-1.1 on GA media</title>
      <link>https://cve.radiocsirt.org/vuln/opensuse-su-2026:11372-1</link>
      <description>&lt;p&gt;python313-sh-2.3.0-1.1 on GA media&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;python313-sh-2.3.0-1.1 on GA media&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/opensuse-su-2026:11372-1</guid>
    </item>
    <item>
      <title>PYSEC-2026-3540 — sh _uid does not drop supplementary groups (incomplete privilege drop)</title>
      <link>https://cve.radiocsirt.org/vuln/pysec-2026-3540</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; PyPI: sh&lt;/p&gt;
&lt;p&gt;### Impact
The `_uid` option performed an incomplete privilege drop on Linux/Unix-like systems.&lt;/p&gt;
&lt;p&gt;When `sh` was run from a process with elevated privileges, such as root, and a command was launched with `_uid=&amp;lt;unprivileged user&amp;gt;`, the child process changed its UID and primary GID but did not reset its supplementary groups. As a result, the child process could retain the parent process’s supplementary groups, potentially including privileged groups such as root, docker, disk, shadow, or sudo.&lt;/p&gt;
&lt;p&gt;This could allow a subprocess that was expected to run with reduced privileges to access files or resources available to the original process’s supplementary groups. Users are impacted if they rely on `_uid` as a privilege boundary when launching commands from a privileged parent process.&lt;/p&gt;
&lt;p&gt;### Patches
Upgrade to version &amp;gt;= 2.2.4&lt;/p&gt;
&lt;p&gt;### Workarounds
Avoid using `_uid` when the user represents a less-privileged user.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; PyPI: sh&lt;/p&gt;
&lt;p&gt;### Impact
The `_uid` option performed an incomplete privilege drop on Linux/Unix-like systems.&lt;/p&gt;
&lt;p&gt;When `sh` was run from a process with elevated privileges, such as root, and a command was launched with `_uid=&amp;lt;unprivileged user&amp;gt;`, the child process changed its UID and primary GID but did not reset its supplementary groups. As a result, the child process could retain the parent process’s supplementary groups, potentially including privileged groups such as root, docker, disk, shadow, or sudo.&lt;/p&gt;
&lt;p&gt;This could allow a subprocess that was expected to run with reduced privileges to access files or resources available to the original process’s supplementary groups. Users are impacted if they rely on `_uid` as a privilege boundary when launching commands from a privileged parent process.&lt;/p&gt;
&lt;p&gt;### Patches
Upgrade to version &amp;gt;= 2.2.4&lt;/p&gt;
&lt;p&gt;### Workarounds
Avoid using `_uid` when the user represents a less-privileged user.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/pysec-2026-3540</guid>
    </item>
    <item>
      <title>SUSE-SU-2026:23112-1 — Security update for python-sh</title>
      <link>https://cve.radiocsirt.org/vuln/suse-su-2026:23112-1</link>
      <description>&lt;p&gt;Security update for python-sh&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;Security update for python-sh&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/suse-su-2026:23112-1</guid>
    </item>
    <item>
      <title>UBUNTU-CVE-2026-54552</title>
      <link>https://cve.radiocsirt.org/vuln/ubuntu-cve-2026-54552</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Ubuntu:16.04:LTS: python-sh, Ubuntu:18.04:LTS: python-sh, Ubuntu:20.04:LTS: python-sh, Ubuntu:22.04:LTS: python-sh, Ubuntu:24.04:LTS: python-sh, Ubuntu:26.04:LTS: python-sh&lt;/p&gt;
&lt;p&gt;sh provides Python process launching. Prior to 2.2.4, the _uid option in sh.py performs an incomplete privilege drop on Linux and Unix-like systems. When sh runs from an elevated process and launches a command with _uid set to an unprivileged user, the child changes its UID but can retain the parent process&amp;#39;s supplementary groups because the privilege-drop sequence does not fully establish the target user&amp;#39;s UID, primary GID, and supplementary groups. The child can therefore retain access to files or resources granted to privileged groups such as root, docker, disk, shadow, or sudo, violating the expected _uid privilege boundary. This issue is fixed in version 2.2.4.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Ubuntu:16.04:LTS: python-sh, Ubuntu:18.04:LTS: python-sh, Ubuntu:20.04:LTS: python-sh, Ubuntu:22.04:LTS: python-sh, Ubuntu:24.04:LTS: python-sh, Ubuntu:26.04:LTS: python-sh&lt;/p&gt;
&lt;p&gt;sh provides Python process launching. Prior to 2.2.4, the _uid option in sh.py performs an incomplete privilege drop on Linux and Unix-like systems. When sh runs from an elevated process and launches a command with _uid set to an unprivileged user, the child changes its UID but can retain the parent process&amp;#39;s supplementary groups because the privilege-drop sequence does not fully establish the target user&amp;#39;s UID, primary GID, and supplementary groups. The child can therefore retain access to files or resources granted to privileged groups such as root, docker, disk, shadow, or sudo, violating the expected _uid privilege boundary. This issue is fixed in version 2.2.4.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/ubuntu-cve-2026-54552</guid>
    </item>
  </channel>
</rss>
