<?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>Fri, 02 Oct 2026 23:56:45 +0000</lastBuildDate>
    <item>
      <title>BREW-glances-CVE-2026-53925 — Glances: Arbitrary file write and command execution via `secure_popen` redirection and chaining operators in AMP comman…</title>
      <link>https://cve.radiocsirt.org/vuln/brew-glances-cve-2026-53925</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Homebrew: glances&lt;/p&gt;
&lt;p&gt;Glances is an open-source system cross-platform monitoring tool. From 4.0.8 until 4.5.5, the secure_popen() function in glances/secure.py interprets &amp;gt; (file redirection), | (pipe), and &amp;amp;&amp;amp; (command chaining) operators in command strings. These operators are applied without any validation on the target file path, piped command, or chained command. When Application Monitoring Process (AMP) modules load their command or service_cmd configuration values from glances.conf, those values are passed directly to secure_popen() with no sanitization. This allows an attacker who can modify the Glances configuration file to write arbitrary content to arbitrary filesystem paths (via &amp;gt;), chain arbitrary commands (via &amp;amp;&amp;amp;), or pipe command output to arbitrary programs (via |). This vulnerability is fixed in 4.5.5.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Homebrew: glances&lt;/p&gt;
&lt;p&gt;Glances is an open-source system cross-platform monitoring tool. From 4.0.8 until 4.5.5, the secure_popen() function in glances/secure.py interprets &amp;gt; (file redirection), | (pipe), and &amp;amp;&amp;amp; (command chaining) operators in command strings. These operators are applied without any validation on the target file path, piped command, or chained command. When Application Monitoring Process (AMP) modules load their command or service_cmd configuration values from glances.conf, those values are passed directly to secure_popen() with no sanitization. This allows an attacker who can modify the Glances configuration file to write arbitrary content to arbitrary filesystem paths (via &amp;gt;), chain arbitrary commands (via &amp;amp;&amp;amp;), or pipe command output to arbitrary programs (via |). This vulnerability is fixed in 4.5.5.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/brew-glances-cve-2026-53925</guid>
    </item>
    <item>
      <title>CVE-2026-53925 — Glances: Arbitrary file write and command execution via `secure_popen` redirection and chaining operators in AMP comman…</title>
      <link>https://cve.radiocsirt.org/vuln/cve-2026-53925</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; nicolargo glances&lt;/p&gt;
&lt;p&gt;Glances is an open-source system cross-platform monitoring tool. From 4.0.8 until 4.5.5, the secure_popen() function in glances/secure.py interprets &amp;gt; (file redirection), | (pipe), and &amp;amp;&amp;amp; (command chaining) operators in command strings. These operators are applied without any validation on the target file path, piped command, or chained command. When Application Monitoring Process (AMP) modules load their command or service_cmd configuration values from glances.conf, those values are passed directly to secure_popen() with no sanitization. This allows an attacker who can modify the Glances configuration file to write arbitrary content to arbitrary filesystem paths (via &amp;gt;), chain arbitrary commands (via &amp;amp;&amp;amp;), or pipe command output to arbitrary programs (via |). This vulnerability is fixed in 4.5.5.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; nicolargo glances&lt;/p&gt;
&lt;p&gt;Glances is an open-source system cross-platform monitoring tool. From 4.0.8 until 4.5.5, the secure_popen() function in glances/secure.py interprets &amp;gt; (file redirection), | (pipe), and &amp;amp;&amp;amp; (command chaining) operators in command strings. These operators are applied without any validation on the target file path, piped command, or chained command. When Application Monitoring Process (AMP) modules load their command or service_cmd configuration values from glances.conf, those values are passed directly to secure_popen() with no sanitization. This allows an attacker who can modify the Glances configuration file to write arbitrary content to arbitrary filesystem paths (via &amp;gt;), chain arbitrary commands (via &amp;amp;&amp;amp;), or pipe command output to arbitrary programs (via |). This vulnerability is fixed in 4.5.5.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/cve-2026-53925</guid>
    </item>
    <item>
      <title>GHSA-3vwc-qwhc-3mj7 — Glances has arbitrary file write and command execution via `secure_popen` redirection and chaining operators in AMP com…</title>
      <link>https://cve.radiocsirt.org/vuln/ghsa-3vwc-qwhc-3mj7</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; PyPI: glances&lt;/p&gt;
&lt;p&gt;### Summary&lt;/p&gt;
&lt;p&gt;The `secure_popen()` function in `glances/secure.py` interprets `&amp;gt;` (file redirection), `|` (pipe), and `&amp;amp;&amp;amp;` (command chaining) operators in command strings. These operators are applied without any validation on the target file path, piped command, or chained command.&lt;/p&gt;
&lt;p&gt;When Application Monitoring Process (AMP) modules load their `command` or `service_cmd` configuration values from `glances.conf`, those values are passed directly to `secure_popen()` with no sanitization. This allows an attacker who can modify the Glances configuration file to write arbitrary content to arbitrary filesystem paths (via `&amp;gt;`), chain arbitrary commands (via `&amp;amp;&amp;amp;`), or pipe command output to arbitrary programs (via `|`).&lt;/p&gt;
&lt;p&gt;Crucially, this vulnerability is **not mitigated** by the `--disable-config-exec` flag that was introduced to address CVE-2026-33641. That flag only disables backtick command execution in `config.get_value()`; it does not affect the `secure_popen()` function&amp;#39;s interpretation of shell-like operators.&lt;/p&gt;
&lt;p&gt;### Details&lt;/p&gt;
&lt;p&gt;**Affected code path 1 — Default AMP (`glances/amps/default/__init__.py:69`)**&lt;/p&gt;
&lt;p&gt;```python
res = self.get(&amp;#39;command&amp;#39;)
# ...
self.set_result(secure_popen(res).rstrip())
```&lt;/p&gt;
&lt;p&gt;The `command` config value is loaded from `[amp_&amp;lt;name&amp;gt;]` sections via `GlancesAmp.load_config()` (`glances/amps/amp.py:81`):&lt;/p&gt;
&lt;p&gt;```python
self.configs[param] = config.get_value(amp_section, param).split(&amp;#39;,&amp;#39;)
```&lt;/p&gt;
&lt;p&gt;**Affected code path 2 — SystemV AMP (`glances/amps/systemv/__init__.py:60`)**&lt;/p&gt;
&lt;p&gt;``…&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; PyPI: glances&lt;/p&gt;
&lt;p&gt;### Summary&lt;/p&gt;
&lt;p&gt;The `secure_popen()` function in `glances/secure.py` interprets `&amp;gt;` (file redirection), `|` (pipe), and `&amp;amp;&amp;amp;` (command chaining) operators in command strings. These operators are applied without any validation on the target file path, piped command, or chained command.&lt;/p&gt;
&lt;p&gt;When Application Monitoring Process (AMP) modules load their `command` or `service_cmd` configuration values from `glances.conf`, those values are passed directly to `secure_popen()` with no sanitization. This allows an attacker who can modify the Glances configuration file to write arbitrary content to arbitrary filesystem paths (via `&amp;gt;`), chain arbitrary commands (via `&amp;amp;&amp;amp;`), or pipe command output to arbitrary programs (via `|`).&lt;/p&gt;
&lt;p&gt;Crucially, this vulnerability is **not mitigated** by the `--disable-config-exec` flag that was introduced to address CVE-2026-33641. That flag only disables backtick command execution in `config.get_value()`; it does not affect the `secure_popen()` function&amp;#39;s interpretation of shell-like operators.&lt;/p&gt;
&lt;p&gt;### Details&lt;/p&gt;
&lt;p&gt;**Affected code path 1 — Default AMP (`glances/amps/default/__init__.py:69`)**&lt;/p&gt;
&lt;p&gt;```python
res = self.get(&amp;#39;command&amp;#39;)
# ...
self.set_result(secure_popen(res).rstrip())
```&lt;/p&gt;
&lt;p&gt;The `command` config value is loaded from `[amp_&amp;lt;name&amp;gt;]` sections via `GlancesAmp.load_config()` (`glances/amps/amp.py:81`):&lt;/p&gt;
&lt;p&gt;```python
self.configs[param] = config.get_value(amp_section, param).split(&amp;#39;,&amp;#39;)
```&lt;/p&gt;
&lt;p&gt;**Affected code path 2 — SystemV AMP (`glances/amps/systemv/__init__.py:60`)**&lt;/p&gt;
&lt;p&gt;``…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/ghsa-3vwc-qwhc-3mj7</guid>
    </item>
  </channel>
</rss>
