<?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:48:01 +0000</lastBuildDate>
    <item>
      <title>bdu:2026-17369</title>
      <link>https://cve.radiocsirt.org/vuln/bdu:2026-17369</link>
      <description>bdu:2026-17369</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/bdu:2026-17369</guid>
    </item>
    <item>
      <title>BIT-virtualenv-2026-113723 — virtualenv: Bash prompt values can change meaning under older compatibility modes</title>
      <link>https://cve.radiocsirt.org/vuln/bit-virtualenv-2026-113723</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.9, caller-supplied prompt text can become executable syntax in the bash activation prompt. An attacker must influence the value passed to virtualenv, and a user must subsequently activate the environment and draw the prompt. This vulnerability is fixed in 21.14.9.&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.9, caller-supplied prompt text can become executable syntax in the bash activation prompt. An attacker must influence the value passed to virtualenv, and a user must subsequently activate the environment and draw the prompt. This vulnerability is fixed in 21.14.9.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/bit-virtualenv-2026-113723</guid>
    </item>
    <item>
      <title>BREW-charm-tools-CVE-2026-113723 — virtualenv: Bash prompt values can change meaning under older compatibility modes</title>
      <link>https://cve.radiocsirt.org/vuln/brew-charm-tools-cve-2026-113723</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;Caller-supplied prompt text can become executable syntax in the bash activation prompt. An attacker must influence the
value passed to virtualenv, and a user must subsequently activate the environment and draw the prompt.&lt;/p&gt;
&lt;p&gt;## Affected area&lt;/p&gt;
&lt;p&gt;Bash runs with compatibility level 4.2 and draws the environment prompt. Its replacement-string behavior differs from
newer compatibility modes, leaving prompt text subject to a second interpretation. The report concerns POSIX activation.
It does not establish exposure through unrelated activators.&lt;/p&gt;
&lt;p&gt;## Attacker-controlled input&lt;/p&gt;
&lt;p&gt;The attacker controls prompt or destination data passed as a virtualenv argument. The user later sources the generated
activation script.&lt;/p&gt;
&lt;p&gt;## Affected code&lt;/p&gt;
&lt;p&gt;The relevant 21.14.8 source is in
[bash prompt assembly](https://github.com/pypa/virtualenv/blob/a795ab116356afde11039cf2763d77e8a06da738/src/virtualenv/activation/bash/activate.sh).&lt;/p&gt;
&lt;p&gt;## Mechanism&lt;/p&gt;
&lt;p&gt;`bin/activate` copies the prompt into `PS1`. A shell expands `PS1` again when it draws a prompt, so the value must
survive both the assignment and that later expansion. The bash and zsh branches escape for their usual prompt rules.
Three other paths still interpret prompt data as commands: dash sourcing `activate` directly, a child dash inheriting an
exported `PS1` from bash, and bash running at compatibility level 4.2 or lower. A value such as `x$(touch MARKER)y` then
runs `touch` on prompt display. Creating the environment does not run the payload.&lt;/p&gt;
&lt;p&gt;##…&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;Caller-supplied prompt text can become executable syntax in the bash activation prompt. An attacker must influence the
value passed to virtualenv, and a user must subsequently activate the environment and draw the prompt.&lt;/p&gt;
&lt;p&gt;## Affected area&lt;/p&gt;
&lt;p&gt;Bash runs with compatibility level 4.2 and draws the environment prompt. Its replacement-string behavior differs from
newer compatibility modes, leaving prompt text subject to a second interpretation. The report concerns POSIX activation.
It does not establish exposure through unrelated activators.&lt;/p&gt;
&lt;p&gt;## Attacker-controlled input&lt;/p&gt;
&lt;p&gt;The attacker controls prompt or destination data passed as a virtualenv argument. The user later sources the generated
activation script.&lt;/p&gt;
&lt;p&gt;## Affected code&lt;/p&gt;
&lt;p&gt;The relevant 21.14.8 source is in
[bash prompt assembly](https://github.com/pypa/virtualenv/blob/a795ab116356afde11039cf2763d77e8a06da738/src/virtualenv/activation/bash/activate.sh).&lt;/p&gt;
&lt;p&gt;## Mechanism&lt;/p&gt;
&lt;p&gt;`bin/activate` copies the prompt into `PS1`. A shell expands `PS1` again when it draws a prompt, so the value must
survive both the assignment and that later expansion. The bash and zsh branches escape for their usual prompt rules.
Three other paths still interpret prompt data as commands: dash sourcing `activate` directly, a child dash inheriting an
exported `PS1` from bash, and bash running at compatibility level 4.2 or lower. A value such as `x$(touch MARKER)y` then
runs `touch` on prompt display. Creating the environment does not run the payload.&lt;/p&gt;
&lt;p&gt;##…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/brew-charm-tools-cve-2026-113723</guid>
    </item>
    <item>
      <title>EUVD-2026-393475</title>
      <link>https://cve.radiocsirt.org/vuln/euvd-2026-393475</link>
      <description>EUVD-2026-393475</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/euvd-2026-393475</guid>
    </item>
    <item>
      <title>fkie_cve-2026-113723</title>
      <link>https://cve.radiocsirt.org/vuln/fkie_cve-2026-113723</link>
      <description>&lt;p&gt;virtualenv is a tool for creating isolated virtual python environments. Prior to 21.14.9, caller-supplied prompt text can become executable syntax in the bash activation prompt. An attacker must influence the value passed to virtualenv, and a user must subsequently activate the environment and draw the prompt. This vulnerability is fixed in 21.14.9.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;virtualenv is a tool for creating isolated virtual python environments. Prior to 21.14.9, caller-supplied prompt text can become executable syntax in the bash activation prompt. An attacker must influence the value passed to virtualenv, and a user must subsequently activate the environment and draw the prompt. This vulnerability is fixed in 21.14.9.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/fkie_cve-2026-113723</guid>
    </item>
    <item>
      <title>GHSA-6w3r-xr62-4xcp — virtualenv: Bash prompt values can change meaning under older compatibility modes</title>
      <link>https://cve.radiocsirt.org/vuln/ghsa-6w3r-xr62-4xcp</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;Caller-supplied prompt text can become executable syntax in the bash activation prompt. An attacker must influence the
value passed to virtualenv, and a user must subsequently activate the environment and draw the prompt.&lt;/p&gt;
&lt;p&gt;## Affected area&lt;/p&gt;
&lt;p&gt;Bash runs with compatibility level 4.2 and draws the environment prompt. Its replacement-string behavior differs from
newer compatibility modes, leaving prompt text subject to a second interpretation. The report concerns POSIX activation.
It does not establish exposure through unrelated activators.&lt;/p&gt;
&lt;p&gt;## Attacker-controlled input&lt;/p&gt;
&lt;p&gt;The attacker controls prompt or destination data passed as a virtualenv argument. The user later sources the generated
activation script.&lt;/p&gt;
&lt;p&gt;## Affected code&lt;/p&gt;
&lt;p&gt;The relevant 21.14.8 source is in
[bash prompt assembly](https://github.com/pypa/virtualenv/blob/a795ab116356afde11039cf2763d77e8a06da738/src/virtualenv/activation/bash/activate.sh).&lt;/p&gt;
&lt;p&gt;## Mechanism&lt;/p&gt;
&lt;p&gt;`bin/activate` copies the prompt into `PS1`. A shell expands `PS1` again when it draws a prompt, so the value must
survive both the assignment and that later expansion. The bash and zsh branches escape for their usual prompt rules.
Three other paths still interpret prompt data as commands: dash sourcing `activate` directly, a child dash inheriting an
exported `PS1` from bash, and bash running at compatibility level 4.2 or lower. A value such as `x$(touch MARKER)y` then
runs `touch` on prompt display. Creating the environment does not run the payload.&lt;/p&gt;
&lt;p&gt;##…&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;Caller-supplied prompt text can become executable syntax in the bash activation prompt. An attacker must influence the
value passed to virtualenv, and a user must subsequently activate the environment and draw the prompt.&lt;/p&gt;
&lt;p&gt;## Affected area&lt;/p&gt;
&lt;p&gt;Bash runs with compatibility level 4.2 and draws the environment prompt. Its replacement-string behavior differs from
newer compatibility modes, leaving prompt text subject to a second interpretation. The report concerns POSIX activation.
It does not establish exposure through unrelated activators.&lt;/p&gt;
&lt;p&gt;## Attacker-controlled input&lt;/p&gt;
&lt;p&gt;The attacker controls prompt or destination data passed as a virtualenv argument. The user later sources the generated
activation script.&lt;/p&gt;
&lt;p&gt;## Affected code&lt;/p&gt;
&lt;p&gt;The relevant 21.14.8 source is in
[bash prompt assembly](https://github.com/pypa/virtualenv/blob/a795ab116356afde11039cf2763d77e8a06da738/src/virtualenv/activation/bash/activate.sh).&lt;/p&gt;
&lt;p&gt;## Mechanism&lt;/p&gt;
&lt;p&gt;`bin/activate` copies the prompt into `PS1`. A shell expands `PS1` again when it draws a prompt, so the value must
survive both the assignment and that later expansion. The bash and zsh branches escape for their usual prompt rules.
Three other paths still interpret prompt data as commands: dash sourcing `activate` directly, a child dash inheriting an
exported `PS1` from bash, and bash running at compatibility level 4.2 or lower. A value such as `x$(touch MARKER)y` then
runs `touch` on prompt display. Creating the environment does not run the payload.&lt;/p&gt;
&lt;p&gt;##…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/ghsa-6w3r-xr62-4xcp</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-113723</title>
      <link>https://cve.radiocsirt.org/vuln/ubuntu-cve-2026-113723</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.9, caller-supplied prompt text can become executable syntax in the bash activation prompt. An attacker must influence the value passed to virtualenv, and a user must subsequently activate the environment and draw the prompt. This vulnerability is fixed in 21.14.9.&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.9, caller-supplied prompt text can become executable syntax in the bash activation prompt. An attacker must influence the value passed to virtualenv, and a user must subsequently activate the environment and draw the prompt. This vulnerability is fixed in 21.14.9.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/ubuntu-cve-2026-113723</guid>
    </item>
  </channel>
</rss>
