Categories
CVE-2026-68517 medium CVSS 6.5

Vulnerability in glances (CVE-2026-68517)

Summary

Vulnerability in glances (CVE-2026-68517). Confidential information can be exposed externally. Exploitable via CORSMiddleware. Mitigation: upgrade to 4.5.6 or later.

Original description

The description as published by the source.

Summary

Glances's REST API server includes a documented safety check intended to guarantee that cors_credentials=True can never be combined with an unrestricted CORS origin allowlist. The check compares the configured origin list to the wildcard using exact list equality (cors_origins == ["*"]) instead of a membership test. Any multi-entry origin configuration that merely includes "*" alongside other origins (e.g. cors_origins=*,https://trusted.example.com) bypasses the check entirely, while Starlette's underlying CORSMiddleware still treats the presence of "*" anywhere in the list as "allow all origins" and reflects the request's actual Origin header together with Access-Control-Allow-Credentials: true. This allows any website to read a victim's authenticated Glances monitoring data — including full process lists with command-line arguments — by exploiting the browser's automatic replay of cached HTTP Basic Auth credentials in a cross-origin request.

Details

glances/outputs/glances_restful_api.py:298:

if cors_origins == ["*"] and cors_credentials:
    logger.warning(...)
    cors_credentials = False

The intended guarantee is documented in glances/outputs/glances_stdout_api_restful_doc.py:247-260: "Setting cors_credentials=True with cors_origins= is not allowed. Glances will automatically disable credentials and log a warning if this combination is detected."* The exact-equality comparison only matches when cors_origins is precis…

Source: GitHub Security Advisories (Global) NVD GitHub Advisory

Auto-generated summary

Assembled by SecPulse from the source data (CVSS, CWE, affected versions) using templates — no AI involved. Check the original description and references below for exact details.

A vulnerability tracked as CVE-2026-68517 has been found in glances.
Attackers can target a specific entry point like CORSMiddleware over the network to misuse the product.
Confidential information can be exposed externally. CVSS score: 6.5/10.
What to do: upgrade glances to 4.5.6 or later.
If unsure, ask your IT team or search "glances CVE-2026-68517" on the vendor's site.

CVE-2026-68517 (glances) — CWE-942 / CVSS v3 6.5
Attack vector: remote (network-reachable) / unauthenticated
Attack surface: CORSMiddleware / Origin / cors_origins
Patched: 4.5.6 — apply immediately
Plan: 1) Audit SBOM/dependencies, 2) Stage→prod upgrade, 3) Add WAF/proxy monitoring on affected endpoints, 4) Hunt IOCs in logs.
Refs: see the GHSA / vendor advisory / patched release linked on this page.

❓ What is the problem

A vulnerability (CWE-942) exists in glances. Attackers reach the vulnerable code path via CORSMiddleware without authentication.

📍 Affected scope

Check the vendor advisory for the affected versions of glances. Attack surface: CORSMiddleware / Origin / cors_origins.

🔥 Severity

Severity: Medium (CVSS 6.5/10). Confidential information can be exposed externally.

🔧 How to fix

Update to 4.5.6.

🛡️ Workaround

Until the patch is applied: disable the affected feature, apply WAF rules, or restrict access via network ACLs.

🔍 Detection

Search webserver/proxy logs for unusual request patterns matching this CVE's known IOCs. Run grep -r 'glances' . against your dependency files (package-lock.json, requirements.txt, go.sum) to find affected services.

Response actions

Concrete steps and command examples for SOC/SRE teams to execute in order

  1. 1
    Identify exposure identify
    grep -r 'glances' . | grep -v node_modules

    リポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で glances を grep し、稼働しているサービス・バージョンを把握する。

  2. 2
    Apply patch patch
    Upgrade glances to 4.5.6

    ステージング環境で 4.5.6 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスを含めること。

  3. 3
    Post-deployment verification verify
    Confirm patched version is live in production

    パッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番ではアクセスログ・WAF でアラート再発が無いか継続監視。

Affected packages

pip glances
[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"4.5.6"}]}]
PyPI glances
[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"4.5.6"}]}]

Fix status by distribution

Fixed packages published by each distribution for this CVE

References

We use cookies for analytics and ad measurement. This setting applies to all Game co., Ltd. sites. Details