Vulnerability in glances (UBUNTU-CVE-2026-68520)

Summary

Vulnerability in glances (UBUNTU-CVE-2026-68520). Risk of unauthorized operations or information disclosure. Exploitable via GET /api/4/config. Mitigation: upgrade to 4.5.6 or later.

Original description

The description as published by the source.

Glances is an open-source system cross-platform monitoring tool. Prior to 4.5.6, as_dict_secure() in glances/config.py checks only option names and exposes public_username and credentials embedded in public_api values through unauthenticated GET /api/4/config and GET /api/4/config/ip requests. This issue is fixed in 4.5.6.

Source: OSV.dev (Open Source Vulnerabilities) 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 UBUNTU-CVE-2026-68520 has been found in glances.
Attackers can target a specific entry point like GET /api/4/config over the network to misuse the product.
Risk of unauthorized operations or information disclosure.
What to do: upgrade glances to 4.5.6 or later.
If unsure, ask your IT team or search "glances UBUNTU-CVE-2026-68520" on the vendor's site.

UBUNTU-CVE-2026-68520 (glances)
Attack vector: remote (network-reachable) / unauthenticated / no user interaction
Attack surface: GET /api/4/config / GET /api/4/config/ip
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 (unclassified) exists in glances. Attackers reach the vulnerable code path via GET /api/4/config without authentication.

📍 Affected scope

Check the vendor advisory for the affected versions of glances. Attack surface: GET /api/4/config / GET /api/4/config/ip.

🔥 Severity

Severity: ?. Risk of unauthorized operations or information disclosure.

🔧 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 GET /api/4/config 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

1
Identify exposure identify
```
grep -r 'glances' . | grep -v node_modules
```
リポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で glances を grep し、稼働しているサービス・バージョンを把握する。
2
Hunt for indicators of compromise detect
```
grep 'GET /api/4/config' /var/log/nginx/access.log | grep -E '(unusual_payload|sqli_pattern)'
```
アクセスログで GET /api/4/config への異常なリクエスト (不正な認証ヘッダ・SQLメタ文字)を過去 30〜90日分捜索。WAF/SIEM があれば該当パスのアラート発火履歴を確認。
3
Apply patch patch
```
Upgrade glances to 4.5.6
```
ステージング環境で 4.5.6 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスと、Step 2 で見つけた異常検知の続報チェックを含めること。
4
Post-deployment verification verify
```
Replay attack against GET /api/4/config on staging to confirm patch closes the vector
```
パッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番では Step 2 と同じログクエリでアラート再発が無いか継続監視。