<?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>Mon, 16 Nov 2026 20:59:08 +0000</lastBuildDate>
    <item>
      <title>bdu:2026-17370</title>
      <link>https://cve.radiocsirt.org/vuln/bdu:2026-17370</link>
      <description>bdu:2026-17370</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/bdu:2026-17370</guid>
    </item>
    <item>
      <title>BIT-virtualenv-2026-113725 — virtualenv bash activate runs commands from an environment name with a backslash before $</title>
      <link>https://cve.radiocsirt.org/vuln/bit-virtualenv-2026-113725</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Bitnami: virtualenv&lt;/p&gt;
&lt;p&gt;virtualenv is a tool for creating isolated virtual python environments. Prior to 21.14.7, the bash activate script escapes the environment name for only one of the two passes bash makes over PS1, so a backslash in the name undoes the escaping and a name containing \$(...) runs as commands in the user&amp;#39;s shell each time bash draws the prompt. This issue is fixed in version 21.14.7.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Bitnami: virtualenv&lt;/p&gt;
&lt;p&gt;virtualenv is a tool for creating isolated virtual python environments. Prior to 21.14.7, the bash activate script escapes the environment name for only one of the two passes bash makes over PS1, so a backslash in the name undoes the escaping and a name containing \$(...) runs as commands in the user&amp;#39;s shell each time bash draws the prompt. This issue is fixed in version 21.14.7.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/bit-virtualenv-2026-113725</guid>
    </item>
    <item>
      <title>BREW-charm-tools-CVE-2026-113725 — virtualenv bash activate runs commands from an environment name with a backslash before $</title>
      <link>https://cve.radiocsirt.org/vuln/brew-charm-tools-cve-2026-113725</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Homebrew: charm-tools&lt;/p&gt;
&lt;p&gt;### Summary&lt;/p&gt;
&lt;p&gt;The bash `activate` script escapes the environment name for only one of the two passes bash makes over `PS1`, so a
backslash in the name undoes the escaping and a name containing `\$(...)` runs as commands in the user&amp;#39;s shell each
time bash draws the prompt.&lt;/p&gt;
&lt;p&gt;### Affected area&lt;/p&gt;
&lt;p&gt;`src/virtualenv/activation/bash/activate.sh`, the block that prepends the environment name to `PS1`.&lt;/p&gt;
&lt;p&gt;### Attacker-controlled input&lt;/p&gt;
&lt;p&gt;The environment name: the environment directory&amp;#39;s name, or the `--prompt` or `VIRTUALENV_PROMPT` value. An attacker
needs to influence it, for example through a CI job or wrapper tool that passes a branch, project or job name through,
or a directory in a cloned repository or unpacked archive. `--prompt .` takes the current directory&amp;#39;s name.&lt;/p&gt;
&lt;p&gt;### Details&lt;/p&gt;
&lt;p&gt;bash handles `PS1` in two passes each time it draws the prompt: it first decodes backslash prompt escapes, turning `\\`
into `\` and `\$` into `$` (or `#` for root), and then runs parameter expansion, command substitution and arithmetic
expansion on the result. Since 21.13.0 the script escapes backslashes, dollar signs and backticks in the name, but only
for the second pass, so the decode pass strips the escaping that a backslash in the name precedes. Releases before
21.13.0 do not escape the name at all. A bash running as root decodes `\$` to `#`, so the payload shows the wrong text
there but runs nothing. zsh does no decode pass and is not affected.&lt;/p&gt;
&lt;p&gt;### Proof of concept&lt;/p&gt;
&lt;p&gt;```console
$ virtualenv --prompt &amp;#39;…&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Homebrew: charm-tools&lt;/p&gt;
&lt;p&gt;### Summary&lt;/p&gt;
&lt;p&gt;The bash `activate` script escapes the environment name for only one of the two passes bash makes over `PS1`, so a
backslash in the name undoes the escaping and a name containing `\$(...)` runs as commands in the user&amp;#39;s shell each
time bash draws the prompt.&lt;/p&gt;
&lt;p&gt;### Affected area&lt;/p&gt;
&lt;p&gt;`src/virtualenv/activation/bash/activate.sh`, the block that prepends the environment name to `PS1`.&lt;/p&gt;
&lt;p&gt;### Attacker-controlled input&lt;/p&gt;
&lt;p&gt;The environment name: the environment directory&amp;#39;s name, or the `--prompt` or `VIRTUALENV_PROMPT` value. An attacker
needs to influence it, for example through a CI job or wrapper tool that passes a branch, project or job name through,
or a directory in a cloned repository or unpacked archive. `--prompt .` takes the current directory&amp;#39;s name.&lt;/p&gt;
&lt;p&gt;### Details&lt;/p&gt;
&lt;p&gt;bash handles `PS1` in two passes each time it draws the prompt: it first decodes backslash prompt escapes, turning `\\`
into `\` and `\$` into `$` (or `#` for root), and then runs parameter expansion, command substitution and arithmetic
expansion on the result. Since 21.13.0 the script escapes backslashes, dollar signs and backticks in the name, but only
for the second pass, so the decode pass strips the escaping that a backslash in the name precedes. Releases before
21.13.0 do not escape the name at all. A bash running as root decodes `\$` to `#`, so the payload shows the wrong text
there but runs nothing. zsh does no decode pass and is not affected.&lt;/p&gt;
&lt;p&gt;### Proof of concept&lt;/p&gt;
&lt;p&gt;```console
$ virtualenv --prompt &amp;#39;…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/brew-charm-tools-cve-2026-113725</guid>
    </item>
    <item>
      <title>EUVD-2026-390645</title>
      <link>https://cve.radiocsirt.org/vuln/euvd-2026-390645</link>
      <description>EUVD-2026-390645</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/euvd-2026-390645</guid>
    </item>
    <item>
      <title>fkie_cve-2026-113725</title>
      <link>https://cve.radiocsirt.org/vuln/fkie_cve-2026-113725</link>
      <description>&lt;p&gt;virtualenv is a tool for creating isolated virtual python environments. Prior to 21.14.7, the bash activate script escapes the environment name for only one of the two passes bash makes over PS1, so a backslash in the name undoes the escaping and a name containing \$(...) runs as commands in the user&amp;#39;s shell each time bash draws the prompt. This issue is fixed in version 21.14.7.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;virtualenv is a tool for creating isolated virtual python environments. Prior to 21.14.7, the bash activate script escapes the environment name for only one of the two passes bash makes over PS1, so a backslash in the name undoes the escaping and a name containing \$(...) runs as commands in the user&amp;#39;s shell each time bash draws the prompt. This issue is fixed in version 21.14.7.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/fkie_cve-2026-113725</guid>
    </item>
    <item>
      <title>GHSA-vxj4-q4g9-crj7 — virtualenv bash activate runs commands from an environment name with a backslash before $</title>
      <link>https://cve.radiocsirt.org/vuln/ghsa-vxj4-q4g9-crj7</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; PyPI: virtualenv&lt;/p&gt;
&lt;p&gt;### Summary&lt;/p&gt;
&lt;p&gt;The bash `activate` script escapes the environment name for only one of the two passes bash makes over `PS1`, so a
backslash in the name undoes the escaping and a name containing `\$(...)` runs as commands in the user&amp;#39;s shell each
time bash draws the prompt.&lt;/p&gt;
&lt;p&gt;### Affected area&lt;/p&gt;
&lt;p&gt;`src/virtualenv/activation/bash/activate.sh`, the block that prepends the environment name to `PS1`.&lt;/p&gt;
&lt;p&gt;### Attacker-controlled input&lt;/p&gt;
&lt;p&gt;The environment name: the environment directory&amp;#39;s name, or the `--prompt` or `VIRTUALENV_PROMPT` value. An attacker
needs to influence it, for example through a CI job or wrapper tool that passes a branch, project or job name through,
or a directory in a cloned repository or unpacked archive. `--prompt .` takes the current directory&amp;#39;s name.&lt;/p&gt;
&lt;p&gt;### Details&lt;/p&gt;
&lt;p&gt;bash handles `PS1` in two passes each time it draws the prompt: it first decodes backslash prompt escapes, turning `\\`
into `\` and `\$` into `$` (or `#` for root), and then runs parameter expansion, command substitution and arithmetic
expansion on the result. Since 21.13.0 the script escapes backslashes, dollar signs and backticks in the name, but only
for the second pass, so the decode pass strips the escaping that a backslash in the name precedes. Releases before
21.13.0 do not escape the name at all. A bash running as root decodes `\$` to `#`, so the payload shows the wrong text
there but runs nothing. zsh does no decode pass and is not affected.&lt;/p&gt;
&lt;p&gt;### Proof of concept&lt;/p&gt;
&lt;p&gt;```console
$ virtualenv --prompt &amp;#39;…&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; PyPI: virtualenv&lt;/p&gt;
&lt;p&gt;### Summary&lt;/p&gt;
&lt;p&gt;The bash `activate` script escapes the environment name for only one of the two passes bash makes over `PS1`, so a
backslash in the name undoes the escaping and a name containing `\$(...)` runs as commands in the user&amp;#39;s shell each
time bash draws the prompt.&lt;/p&gt;
&lt;p&gt;### Affected area&lt;/p&gt;
&lt;p&gt;`src/virtualenv/activation/bash/activate.sh`, the block that prepends the environment name to `PS1`.&lt;/p&gt;
&lt;p&gt;### Attacker-controlled input&lt;/p&gt;
&lt;p&gt;The environment name: the environment directory&amp;#39;s name, or the `--prompt` or `VIRTUALENV_PROMPT` value. An attacker
needs to influence it, for example through a CI job or wrapper tool that passes a branch, project or job name through,
or a directory in a cloned repository or unpacked archive. `--prompt .` takes the current directory&amp;#39;s name.&lt;/p&gt;
&lt;p&gt;### Details&lt;/p&gt;
&lt;p&gt;bash handles `PS1` in two passes each time it draws the prompt: it first decodes backslash prompt escapes, turning `\\`
into `\` and `\$` into `$` (or `#` for root), and then runs parameter expansion, command substitution and arithmetic
expansion on the result. Since 21.13.0 the script escapes backslashes, dollar signs and backticks in the name, but only
for the second pass, so the decode pass strips the escaping that a backslash in the name precedes. Releases before
21.13.0 do not escape the name at all. A bash running as root decodes `\$` to `#`, so the payload shows the wrong text
there but runs nothing. zsh does no decode pass and is not affected.&lt;/p&gt;
&lt;p&gt;### Proof of concept&lt;/p&gt;
&lt;p&gt;```console
$ virtualenv --prompt &amp;#39;…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/ghsa-vxj4-q4g9-crj7</guid>
    </item>
    <item>
      <title>RHSA-2026:95659 — Red Hat Security Advisory: General availability of the satellite/iop-yuptoo-rhel9 container image</title>
      <link>https://cve.radiocsirt.org/vuln/rhsa-2026:95659</link>
      <description>&lt;p&gt;confluent-kafka: confluent-kafka: Information disclosure via improper TLS certificate validation in HashiCorp Vault integration virtualenv: virtualenv: Arbitrary code execution via crafted paths in activation scripts virtualenv: virtualenv: Arbitrary code execution via unverified downloaded seed wheels virtualenv: virtualenv: Arbitrary code execution via unescaped prompt in Windows activation script virtualenv: virtualenv: Arbitrary code execution via configuration injection in prompt values virtualenv: virtualenv: arbitrary code execution via improper quoting in xonsh activation scripts virtualenv: virtualenv: arbitrary code execution via improperly quoted interpreter paths in script launchers virtualenv: virtualenv: Arbitrary code execution via malicious prompt text virtualenv: virtualenv: arbitrary code execution via crafted environment name virtualenv: virtualenv: Arbitrary command execution via unescaped prompt variables in zsh virtualenv: virtualenv: Arbitrary code execution via improperly quoted Fish activation scripts virtualenv: virtualenv: Arbitrary command execution via sequential placeholder substitution in activation templates virtualenv: virtualenv: Arbitrary code execution via unescaped prompt in bash activation script&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;confluent-kafka: confluent-kafka: Information disclosure via improper TLS certificate validation in HashiCorp Vault integration virtualenv: virtualenv: Arbitrary code execution via crafted paths in activation scripts virtualenv: virtualenv: Arbitrary code execution via unverified downloaded seed wheels virtualenv: virtualenv: Arbitrary code execution via unescaped prompt in Windows activation script virtualenv: virtualenv: Arbitrary code execution via configuration injection in prompt values virtualenv: virtualenv: arbitrary code execution via improper quoting in xonsh activation scripts virtualenv: virtualenv: arbitrary code execution via improperly quoted interpreter paths in script launchers virtualenv: virtualenv: Arbitrary code execution via malicious prompt text virtualenv: virtualenv: arbitrary code execution via crafted environment name virtualenv: virtualenv: Arbitrary command execution via unescaped prompt variables in zsh virtualenv: virtualenv: Arbitrary code execution via improperly quoted Fish activation scripts virtualenv: virtualenv: Arbitrary command execution via sequential placeholder substitution in activation templates virtualenv: virtualenv: Arbitrary code execution via unescaped prompt in bash activation script&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/rhsa-2026:95659</guid>
    </item>
    <item>
      <title>UBUNTU-CVE-2026-113725</title>
      <link>https://cve.radiocsirt.org/vuln/ubuntu-cve-2026-113725</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Ubuntu:14.04:LTS: python-virtualenv, Ubuntu:16.04:LTS: python-virtualenv, Ubuntu:18.04:LTS: python-virtualenv, Ubuntu:Pro:20.04:LTS: python-virtualenv, Ubuntu:Pro:22.04:LTS: python-virtualenv, Ubuntu:Pro:24.04:LTS: python-virtualenv, Ubuntu:26.10: python-virtualenv, Ubuntu:26.04:LTS: python-virtualenv&lt;/p&gt;
&lt;p&gt;virtualenv is a tool for creating isolated virtual python environments. Prior to 21.14.7, the bash activate script escapes the environment name for only one of the two passes bash makes over PS1, so a backslash in the name undoes the escaping and a name containing \$(...) runs as commands in the user&amp;#39;s shell each time bash draws the prompt. This issue is fixed in version 21.14.7.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Ubuntu:14.04:LTS: python-virtualenv, Ubuntu:16.04:LTS: python-virtualenv, Ubuntu:18.04:LTS: python-virtualenv, Ubuntu:Pro:20.04:LTS: python-virtualenv, Ubuntu:Pro:22.04:LTS: python-virtualenv, Ubuntu:Pro:24.04:LTS: python-virtualenv, Ubuntu:26.10: python-virtualenv, Ubuntu:26.04:LTS: python-virtualenv&lt;/p&gt;
&lt;p&gt;virtualenv is a tool for creating isolated virtual python environments. Prior to 21.14.7, the bash activate script escapes the environment name for only one of the two passes bash makes over PS1, so a backslash in the name undoes the escaping and a name containing \$(...) runs as commands in the user&amp;#39;s shell each time bash draws the prompt. This issue is fixed in version 21.14.7.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/ubuntu-cve-2026-113725</guid>
    </item>
  </channel>
</rss>
