<?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, 24 Oct 2026 05:49:38 +0000</lastBuildDate>
    <item>
      <title>EUVD-2026-20664</title>
      <link>https://cve.radiocsirt.org/vuln/euvd-2026-20664</link>
      <description>EUVD-2026-20664</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/euvd-2026-20664</guid>
    </item>
    <item>
      <title>fkie_cve-2021-3013</title>
      <link>https://cve.radiocsirt.org/vuln/fkie_cve-2021-3013</link>
      <description>&lt;p&gt;ripgrep before 13 on Windows allows attackers to trigger execution of arbitrary programs from the current working directory via the -z/--search-zip or --pre flag.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;ripgrep before 13 on Windows allows attackers to trigger execution of arbitrary programs from the current working directory via the -z/--search-zip or --pre flag.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/fkie_cve-2021-3013</guid>
    </item>
    <item>
      <title>GHSA-g4xg-fxmg-vcg5 — OS command injection in ripgrep</title>
      <link>https://cve.radiocsirt.org/vuln/ghsa-g4xg-fxmg-vcg5</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; crates.io: ripgrep, crates.io: grep-cli&lt;/p&gt;
&lt;p&gt;ripgrep before 13 on Windows allows attackers to trigger execution of arbitrary programs from the current working directory via the -z/--search-zip or --pre flag.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; crates.io: ripgrep, crates.io: grep-cli&lt;/p&gt;
&lt;p&gt;ripgrep before 13 on Windows allows attackers to trigger execution of arbitrary programs from the current working directory via the -z/--search-zip or --pre flag.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/ghsa-g4xg-fxmg-vcg5</guid>
    </item>
    <item>
      <title>gsd-2021-3013</title>
      <link>https://cve.radiocsirt.org/vuln/gsd-2021-3013</link>
      <description>gsd-2021-3013</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/gsd-2021-3013</guid>
    </item>
    <item>
      <title>openSUSE-SU-2024:11300-1 — ripgrep-13.0.0-2.2 on GA media</title>
      <link>https://cve.radiocsirt.org/vuln/opensuse-su-2024:11300-1</link>
      <description>&lt;p&gt;ripgrep-13.0.0-2.2 on GA media&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;ripgrep-13.0.0-2.2 on GA media&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/opensuse-su-2024:11300-1</guid>
    </item>
    <item>
      <title>RUSTSEC-2021-0071 — `grep-cli` may run arbitrary executables on Windows</title>
      <link>https://cve.radiocsirt.org/vuln/rustsec-2021-0071</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; crates.io: grep-cli&lt;/p&gt;
&lt;p&gt;On Windows in versions of `grep-cli` prior to `0.1.6`, it&amp;#39;s possible for some
of the routines to execute arbitrary executables. In particular, a quirk of
the Windows process execution API is that it will automatically consider the
current directory before other directories when resolving relative binary
names. Therefore, if you use `grep-cli` to read decompressed files in an
untrusted directory with that directory as the CWD, a malicious actor to could
put, e.g., a `gz.exe` binary in that directory and `grep-cli` will use the
malicious actor&amp;#39;s version of `gz.exe` instead of the system&amp;#39;s.&lt;/p&gt;
&lt;p&gt;This is also technically possible on Unix as well, but only if the `PATH`
variable contains `.`. Conventionally, they do not.&lt;/p&gt;
&lt;p&gt;A `DecompressionReader` has been fixed to automatically resolve binary names
using `PATH`, instead of relying on the Windows API to do it.&lt;/p&gt;
&lt;p&gt;If you use `grep-cli`&amp;#39;s `CommandReader` with a `std::process::Command` value
on Windows, then it is recommended to either construct the `Command` with an
absolute binary name, or use `grep-cli`&amp;#39;s new
[`resolve_binary`](https://docs.rs/grep-cli/0.1.6/grep_cli/fn.resolve_binary.html)
helper function.&lt;/p&gt;
&lt;p&gt;To be clear, `grep-cli 0.1.6` mitigates this issue in two ways:&lt;/p&gt;
&lt;p&gt;* A `DecompressionReader` will resolve decompression programs to absolute
paths automatically using the `PATH` environment variable, instead of relying
on Windows APIs to do it (which would result in the undesirable behavior of
checking the CWD for a program first).
* A…&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; crates.io: grep-cli&lt;/p&gt;
&lt;p&gt;On Windows in versions of `grep-cli` prior to `0.1.6`, it&amp;#39;s possible for some
of the routines to execute arbitrary executables. In particular, a quirk of
the Windows process execution API is that it will automatically consider the
current directory before other directories when resolving relative binary
names. Therefore, if you use `grep-cli` to read decompressed files in an
untrusted directory with that directory as the CWD, a malicious actor to could
put, e.g., a `gz.exe` binary in that directory and `grep-cli` will use the
malicious actor&amp;#39;s version of `gz.exe` instead of the system&amp;#39;s.&lt;/p&gt;
&lt;p&gt;This is also technically possible on Unix as well, but only if the `PATH`
variable contains `.`. Conventionally, they do not.&lt;/p&gt;
&lt;p&gt;A `DecompressionReader` has been fixed to automatically resolve binary names
using `PATH`, instead of relying on the Windows API to do it.&lt;/p&gt;
&lt;p&gt;If you use `grep-cli`&amp;#39;s `CommandReader` with a `std::process::Command` value
on Windows, then it is recommended to either construct the `Command` with an
absolute binary name, or use `grep-cli`&amp;#39;s new
[`resolve_binary`](https://docs.rs/grep-cli/0.1.6/grep_cli/fn.resolve_binary.html)
helper function.&lt;/p&gt;
&lt;p&gt;To be clear, `grep-cli 0.1.6` mitigates this issue in two ways:&lt;/p&gt;
&lt;p&gt;* A `DecompressionReader` will resolve decompression programs to absolute
paths automatically using the `PATH` environment variable, instead of relying
on Windows APIs to do it (which would result in the undesirable behavior of
checking the CWD for a program first).
* A…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/rustsec-2021-0071</guid>
    </item>
    <item>
      <title>UBUNTU-CVE-2021-3013</title>
      <link>https://cve.radiocsirt.org/vuln/ubuntu-cve-2021-3013</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Ubuntu:20.04:LTS: rust-ripgrep, Ubuntu:22.04:LTS: rust-ripgrep&lt;/p&gt;
&lt;p&gt;ripgrep before 13 on Windows allows attackers to trigger execution of arbitrary programs from the current working directory via the -z/--search-zip or --pre flag.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Ubuntu:20.04:LTS: rust-ripgrep, Ubuntu:22.04:LTS: rust-ripgrep&lt;/p&gt;
&lt;p&gt;ripgrep before 13 on Windows allows attackers to trigger execution of arbitrary programs from the current working directory via the -z/--search-zip or --pre flag.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/ubuntu-cve-2021-3013</guid>
    </item>
  </channel>
</rss>
