<?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>Wed, 07 Oct 2026 08:35:19 +0000</lastBuildDate>
    <item>
      <title>BREW-glances-CVE-2026-32611 — Glances has a SQL Injection in DuckDB Export via Unparameterized DDL Statements</title>
      <link>https://cve.radiocsirt.org/vuln/brew-glances-cve-2026-32611</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. The GHSA-x46r fix (commit 39161f0) addressed SQL injection in the TimescaleDB export module by converting all SQL operations to use parameterized queries and `psycopg.sql` composable objects. However, the DuckDB export module (`glances/exports/glances_duckdb/__init__.py`) was not included in this fix and contains the same class of vulnerability: table names and column names derived from monitoring statistics are directly interpolated into SQL statements via f-strings. While DuckDB INSERT values already use parameterized queries (`?` placeholders), the DDL construction and table name references do not escape or parameterize identifier names. Version 4.5.3 provides a more complete fix.&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. The GHSA-x46r fix (commit 39161f0) addressed SQL injection in the TimescaleDB export module by converting all SQL operations to use parameterized queries and `psycopg.sql` composable objects. However, the DuckDB export module (`glances/exports/glances_duckdb/__init__.py`) was not included in this fix and contains the same class of vulnerability: table names and column names derived from monitoring statistics are directly interpolated into SQL statements via f-strings. While DuckDB INSERT values already use parameterized queries (`?` placeholders), the DDL construction and table name references do not escape or parameterize identifier names. Version 4.5.3 provides a more complete fix.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/brew-glances-cve-2026-32611</guid>
    </item>
    <item>
      <title>CVE-2026-32611 — Glances has a SQL Injection in DuckDB Export via Unparameterized DDL Statements</title>
      <link>https://cve.radiocsirt.org/vuln/cve-2026-32611</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. The GHSA-x46r fix (commit 39161f0) addressed SQL injection in the TimescaleDB export module by converting all SQL operations to use parameterized queries and `psycopg.sql` composable objects. However, the DuckDB export module (`glances/exports/glances_duckdb/__init__.py`) was not included in this fix and contains the same class of vulnerability: table names and column names derived from monitoring statistics are directly interpolated into SQL statements via f-strings. While DuckDB INSERT values already use parameterized queries (`?` placeholders), the DDL construction and table name references do not escape or parameterize identifier names. Version 4.5.3 provides a more complete fix.&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. The GHSA-x46r fix (commit 39161f0) addressed SQL injection in the TimescaleDB export module by converting all SQL operations to use parameterized queries and `psycopg.sql` composable objects. However, the DuckDB export module (`glances/exports/glances_duckdb/__init__.py`) was not included in this fix and contains the same class of vulnerability: table names and column names derived from monitoring statistics are directly interpolated into SQL statements via f-strings. While DuckDB INSERT values already use parameterized queries (`?` placeholders), the DDL construction and table name references do not escape or parameterize identifier names. Version 4.5.3 provides a more complete fix.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/cve-2026-32611</guid>
    </item>
    <item>
      <title>GHSA-49g7-2ww7-3vf5 — Glances has a SQL Injection in DuckDB Export via Unparameterized DDL Statements</title>
      <link>https://cve.radiocsirt.org/vuln/ghsa-49g7-2ww7-3vf5</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 GHSA-x46r fix (commit 39161f0) addressed SQL injection in the TimescaleDB export module by converting all SQL operations to use parameterized queries and `psycopg.sql` composable objects. However, the DuckDB export module (`glances/exports/glances_duckdb/__init__.py`) was not included in this fix and contains the same class of vulnerability: table names and column names derived from monitoring statistics are directly interpolated into SQL statements via f-strings. While DuckDB INSERT values already use parameterized queries (`?` placeholders), the DDL construction and table name references do not escape or parameterize identifier names.&lt;/p&gt;
&lt;p&gt;## Details&lt;/p&gt;
&lt;p&gt;The DuckDB export module constructs SQL DDL statements by directly interpolating stat field names and plugin names into f-strings.&lt;/p&gt;
&lt;p&gt;**Vulnerable CREATE TABLE construction** (`glances/exports/glances_duckdb/__init__.py:156-162`):&lt;/p&gt;
&lt;p&gt;```python
create_query = f&amp;#34;&amp;#34;&amp;#34;
CREATE TABLE {plugin} (
{&amp;#39;, &amp;#39;.join(creation_list)}
);&amp;#34;&amp;#34;&amp;#34;
self.client.execute(create_query)
```&lt;/p&gt;
&lt;p&gt;The `creation_list` is built from stat dictionary keys in the `update()` method (`glances/exports/glances_duckdb/__init__.py:117-118`):&lt;/p&gt;
&lt;p&gt;```python
for key, value in plugin_stats.items():
    creation_list.append(f&amp;#34;{key} {convert_types[type(self.normalize(value)).__name__]}&amp;#34;)
```&lt;/p&gt;
&lt;p&gt;The INSERT statement also uses the unescaped `plugin` name (`glances/exports/glances_duckdb/__init__.py:172-174`):&lt;/p&gt;
&lt;p&gt;```python
insert_query = f&amp;#34;&amp;#34;&amp;#34;
INSERT INTO {plugin} VALUES (
{&amp;#39;, &amp;#39;.join([…&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 GHSA-x46r fix (commit 39161f0) addressed SQL injection in the TimescaleDB export module by converting all SQL operations to use parameterized queries and `psycopg.sql` composable objects. However, the DuckDB export module (`glances/exports/glances_duckdb/__init__.py`) was not included in this fix and contains the same class of vulnerability: table names and column names derived from monitoring statistics are directly interpolated into SQL statements via f-strings. While DuckDB INSERT values already use parameterized queries (`?` placeholders), the DDL construction and table name references do not escape or parameterize identifier names.&lt;/p&gt;
&lt;p&gt;## Details&lt;/p&gt;
&lt;p&gt;The DuckDB export module constructs SQL DDL statements by directly interpolating stat field names and plugin names into f-strings.&lt;/p&gt;
&lt;p&gt;**Vulnerable CREATE TABLE construction** (`glances/exports/glances_duckdb/__init__.py:156-162`):&lt;/p&gt;
&lt;p&gt;```python
create_query = f&amp;#34;&amp;#34;&amp;#34;
CREATE TABLE {plugin} (
{&amp;#39;, &amp;#39;.join(creation_list)}
);&amp;#34;&amp;#34;&amp;#34;
self.client.execute(create_query)
```&lt;/p&gt;
&lt;p&gt;The `creation_list` is built from stat dictionary keys in the `update()` method (`glances/exports/glances_duckdb/__init__.py:117-118`):&lt;/p&gt;
&lt;p&gt;```python
for key, value in plugin_stats.items():
    creation_list.append(f&amp;#34;{key} {convert_types[type(self.normalize(value)).__name__]}&amp;#34;)
```&lt;/p&gt;
&lt;p&gt;The INSERT statement also uses the unescaped `plugin` name (`glances/exports/glances_duckdb/__init__.py:172-174`):&lt;/p&gt;
&lt;p&gt;```python
insert_query = f&amp;#34;&amp;#34;&amp;#34;
INSERT INTO {plugin} VALUES (
{&amp;#39;, &amp;#39;.join([…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/ghsa-49g7-2ww7-3vf5</guid>
    </item>
  </channel>
</rss>
