Vulnerability in glances (CVE-2026-32632)
Summary
Vulnerability in glances (CVE-2026-32632). Confidential information can be exposed externally. Exploitable via GET /api/4/status. Mitigation: upgrade to 4.5.2 or later.
Original description
The description as published by the source.
Glances is an open-source system cross-platform monitoring tool. Glances recently added DNS rebinding protection for the MCP endpoint, but prior to version 4.5.2, the main REST/WebUI FastAPI application still accepts arbitrary Host headers and does not apply TrustedHostMiddleware or an equivalent host allowlist. As a result, the REST API, WebUI, and token endpoint remain reachable through attacker-controlled domains in classic DNS rebinding scenarios. Once the victim browser has rebound the attacker domain to the Glances service, same-origin policy no longer protects the API because the browser considers the rebinding domain to be the origin. This is a distinct issue from the previously reported default CORS weakness. CORS is not required for exploitation here because DNS rebinding causes the victim browser to treat the malicious domain as same-origin with the rebinding target. Version 4.5.2 contains a patch for the issue.
Source: OSV.dev (Open Source Vulnerabilities) NVD GitHub Advisory OSV
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-32632 has been found in glances.
Attackers can target a specific entry point like GET /api/4/status over the network to misuse the product.
Confidential information can be exposed externally.
What to do: upgrade glances to 4.5.2 or later.
If unsure, ask your IT team or search "glances CVE-2026-32632" on the vendor's site.
CVE-2026-32632 (glances) — CWE-346
Attack vector: remote (network-reachable) / unauthenticated
Attack surface: GET /api/4/status / GET /api/4/all / GET /api/4/config / GET /api/4/args
Patched: 4.5.2 — 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.
A vulnerability (CWE-346) exists in glances. Attackers reach the vulnerable code path via GET /api/4/status without authentication.
Check the vendor advisory for the affected versions of glances. Attack surface: GET /api/4/status / GET /api/4/all / GET /api/4/config / GET /api/4/args.
Severity: ?. Confidential information can be exposed externally.
Update to 4.5.2.
Until the patch is applied: disable the affected feature, apply WAF rules, or restrict access via network ACLs.
Search webserver/proxy logs for unusual GET /api/4/status requests with malformed payloads or SQL meta-characters. 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
-
1Identify exposure identify
grep -r 'glances' . | grep -v node_modulesリポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で
glancesを grep し、稼働しているサービス・バージョンを把握する。 -
2Hunt for indicators of compromise detect
grep 'GET /api/4/status' /var/log/nginx/access.log | grep -E '(unusual_payload|sqli_pattern)'アクセスログで
GET /api/4/statusへの異常なリクエスト (不正な認証ヘッダ・SQLメタ文字)を過去 30〜90日分捜索。WAF/SIEM があれば該当パスのアラート発火履歴を確認。 -
3Apply patch patch
Upgrade glances to 4.5.2ステージング環境で 4.5.2 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスと、Step 2 で見つけた異常検知の続報チェックを含めること。
-
4Post-deployment verification verify
Replay attack against GET /api/4/status on staging to confirm patch closes the vectorパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番では Step 2 と同じログクエリでアラート再発が無いか継続監視。
Affected packages
Fix status by distribution
Fixed packages published by each distribution for this CVE
- Debian DEBIAN-CVE-2026-32632 glances
- Ubuntu UBUNTU-CVE-2026-32632 glances
References
- advisory github.com
- advisory nvd.nist.gov
- advisory github.com
- package github.com
- patch github.com
- web github.com