<?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://vulnerability.circl.lu</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, 05 Oct 2026 05:48:28 +0000</lastBuildDate>
    <item>
      <title>CVE-2026-32610 — Glances's Default CORS Configuration Allows Cross-Origin Credential Theft</title>
      <link>https://vulnerability.circl.lu/vuln/cve-2026-32610</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. Prior to version 4.5.2, the Glances REST API web server ships with a default CORS configuration that sets `allow_origins=[&amp;#34;*&amp;#34;]` combined with `allow_credentials=True`. When both of these options are enabled together, Starlette&amp;#39;s `CORSMiddleware` reflects the requesting `Origin` header value in the `Access-Control-Allow-Origin` response header instead of returning the literal `*` wildcard. This effectively grants any website the ability to make credentialed cross-origin API requests to the Glances server, enabling cross-site data theft of system monitoring information, configuration secrets, and command line arguments from any user who has an active browser session with a Glances instance. Version 4.5.2 fixes the issue.&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. Prior to version 4.5.2, the Glances REST API web server ships with a default CORS configuration that sets `allow_origins=[&amp;#34;*&amp;#34;]` combined with `allow_credentials=True`. When both of these options are enabled together, Starlette&amp;#39;s `CORSMiddleware` reflects the requesting `Origin` header value in the `Access-Control-Allow-Origin` response header instead of returning the literal `*` wildcard. This effectively grants any website the ability to make credentialed cross-origin API requests to the Glances server, enabling cross-site data theft of system monitoring information, configuration secrets, and command line arguments from any user who has an active browser session with a Glances instance. Version 4.5.2 fixes the issue.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://vulnerability.circl.lu/vuln/cve-2026-32610</guid>
    </item>
    <item>
      <title>GHSA-9jfm-9rc6-2hfq — Glances's Default CORS Configuration Allows Cross-Origin Credential Theft</title>
      <link>https://vulnerability.circl.lu/vuln/ghsa-9jfm-9rc6-2hfq</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 Glances REST API web server ships with a default CORS configuration that sets `allow_origins=[&amp;#34;*&amp;#34;]` combined with `allow_credentials=True`. When both of these options are enabled together, Starlette&amp;#39;s `CORSMiddleware` reflects the requesting `Origin` header value in the `Access-Control-Allow-Origin` response header instead of returning the literal `*` wildcard. This effectively grants any website the ability to make credentialed cross-origin API requests to the Glances server, enabling cross-site data theft of system monitoring information, configuration secrets, and command line arguments from any user who has an active browser session with a Glances instance.&lt;/p&gt;
&lt;p&gt;## Details&lt;/p&gt;
&lt;p&gt;The CORS configuration is set up in `glances/outputs/glances_restful_api.py` lines 290-299:&lt;/p&gt;
&lt;p&gt;```python
# glances/outputs/glances_restful_api.py:290-299
# FastAPI Enable CORS
# https://fastapi.tiangolo.com/tutorial/cors/
self._app.add_middleware(
    CORSMiddleware,
    # Related to https://github.com/nicolargo/glances/issues/2812
    allow_origins=config.get_list_value(&amp;#39;outputs&amp;#39;, &amp;#39;cors_origins&amp;#39;, default=[&amp;#34;*&amp;#34;]),
    allow_credentials=config.get_bool_value(&amp;#39;outputs&amp;#39;, &amp;#39;cors_credentials&amp;#39;, default=True),
    allow_methods=config.get_list_value(&amp;#39;outputs&amp;#39;, &amp;#39;cors_methods&amp;#39;, default=[&amp;#34;*&amp;#34;]),
    allow_headers=config.get_list_value(&amp;#39;outputs&amp;#39;, &amp;#39;cors_headers&amp;#39;, default=[&amp;#34;*&amp;#34;]),
)
```&lt;/p&gt;
&lt;p&gt;The defaults are loaded from the config file, but when no config is provided (which is the common case for most deployment…&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 Glances REST API web server ships with a default CORS configuration that sets `allow_origins=[&amp;#34;*&amp;#34;]` combined with `allow_credentials=True`. When both of these options are enabled together, Starlette&amp;#39;s `CORSMiddleware` reflects the requesting `Origin` header value in the `Access-Control-Allow-Origin` response header instead of returning the literal `*` wildcard. This effectively grants any website the ability to make credentialed cross-origin API requests to the Glances server, enabling cross-site data theft of system monitoring information, configuration secrets, and command line arguments from any user who has an active browser session with a Glances instance.&lt;/p&gt;
&lt;p&gt;## Details&lt;/p&gt;
&lt;p&gt;The CORS configuration is set up in `glances/outputs/glances_restful_api.py` lines 290-299:&lt;/p&gt;
&lt;p&gt;```python
# glances/outputs/glances_restful_api.py:290-299
# FastAPI Enable CORS
# https://fastapi.tiangolo.com/tutorial/cors/
self._app.add_middleware(
    CORSMiddleware,
    # Related to https://github.com/nicolargo/glances/issues/2812
    allow_origins=config.get_list_value(&amp;#39;outputs&amp;#39;, &amp;#39;cors_origins&amp;#39;, default=[&amp;#34;*&amp;#34;]),
    allow_credentials=config.get_bool_value(&amp;#39;outputs&amp;#39;, &amp;#39;cors_credentials&amp;#39;, default=True),
    allow_methods=config.get_list_value(&amp;#39;outputs&amp;#39;, &amp;#39;cors_methods&amp;#39;, default=[&amp;#34;*&amp;#34;]),
    allow_headers=config.get_list_value(&amp;#39;outputs&amp;#39;, &amp;#39;cors_headers&amp;#39;, default=[&amp;#34;*&amp;#34;]),
)
```&lt;/p&gt;
&lt;p&gt;The defaults are loaded from the config file, but when no config is provided (which is the common case for most deployment…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://vulnerability.circl.lu/vuln/ghsa-9jfm-9rc6-2hfq</guid>
    </item>
    <item>
      <title>PYSEC-2026-2169</title>
      <link>https://vulnerability.circl.lu/vuln/pysec-2026-2169</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; PyPI: glances&lt;/p&gt;
&lt;p&gt;Glances is an open-source system cross-platform monitoring tool. Prior to version 4.5.2, the Glances REST API web server ships with a default CORS configuration that sets `allow_origins=[&amp;#34;*&amp;#34;]` combined with `allow_credentials=True`. When both of these options are enabled together, Starlette&amp;#39;s `CORSMiddleware` reflects the requesting `Origin` header value in the `Access-Control-Allow-Origin` response header instead of returning the literal `*` wildcard. This effectively grants any website the ability to make credentialed cross-origin API requests to the Glances server, enabling cross-site data theft of system monitoring information, configuration secrets, and command line arguments from any user who has an active browser session with a Glances instance. Version 4.5.2 fixes the issue.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; PyPI: glances&lt;/p&gt;
&lt;p&gt;Glances is an open-source system cross-platform monitoring tool. Prior to version 4.5.2, the Glances REST API web server ships with a default CORS configuration that sets `allow_origins=[&amp;#34;*&amp;#34;]` combined with `allow_credentials=True`. When both of these options are enabled together, Starlette&amp;#39;s `CORSMiddleware` reflects the requesting `Origin` header value in the `Access-Control-Allow-Origin` response header instead of returning the literal `*` wildcard. This effectively grants any website the ability to make credentialed cross-origin API requests to the Glances server, enabling cross-site data theft of system monitoring information, configuration secrets, and command line arguments from any user who has an active browser session with a Glances instance. Version 4.5.2 fixes the issue.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://vulnerability.circl.lu/vuln/pysec-2026-2169</guid>
    </item>
  </channel>
</rss>
