SSRF (Server-Side Request Forgery) in glances (CVE-2026-35587)

Summary

SSRF in glances (CVE-2026-35587). Successful exploitation can lead to full system takeover. Exploitable via GET /ssrf-poc. Mitigation: upgrade to 4.5.4 or later.

Original description

The description as published by the source.

Summary

A Server-Side Request Forgery (SSRF) vulnerability exists in the Glances IP plugin due to improper validation of the public_api configuration parameter. The value of public_api is used directly in outbound HTTP requests without any scheme restriction or hostname/IP validation.

An attacker who can modify the Glances configuration can force the application to send requests to arbitrary internal or external endpoints. Additionally, when public_username and public_password are set, Glances automatically includes these credentials in the Authorization: Basic header, resulting in credential leakage to attacker-controlled servers.

This vulnerability can be exploited to:

Access internal network services (e.g., 127.0.0.1, 192.168.x.x)
Retrieve sensitive data from cloud metadata endpoints (e.g., 169.254.169.254)
Exfiltrate credentials via outbound HTTP requests

The issue arises because public_api is passed directly to the HTTP client (urlopen_auth) without validation, allowing unrestricted outbound connections and unintended disclosure of sensitive information.

Details

The vulnerability exists in the Glances IP plugin where the public_api configuration value is used to fetch public IP information. This value is read directly from the configuration file and passed to the HTTP client without any validation.

Root Cause
In glances/plugins/ip/init.py, the public_api parameter is retrieved from configuration and later used to initialize a background thread respo…

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-35587 has been found in glances.
Attackers can target a specific entry point like GET /ssrf-poc over the network to misuse the product.
Successful exploitation can lead to full system takeover.
What to do: upgrade glances to 4.5.4 or later.
If unsure, ask your IT team or search "glances CVE-2026-35587" on the vendor's site.

CVE-2026-35587 (glances) — CWE-918
Attack vector: remote (network-reachable) / no user interaction
Attack surface: GET /ssrf-poc / Authorization header
Patched: 4.5.4 — 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

SSRF (CWE-918) exists in glances. Attackers reach the vulnerable code path via GET /ssrf-poc.

📍 Affected scope

Check the vendor advisory for the affected versions of glances. Attack surface: GET /ssrf-poc / Authorization header.

🔥 Severity

Severity: ?. Successful exploitation can lead to full system takeover.

🔧 How to fix

Update to 4.5.4.

🛡️ 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 /ssrf-poc 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 /ssrf-poc' /var/log/nginx/access.log | grep -E '(unusual_payload|sqli_pattern)'
```
アクセスログで GET /ssrf-poc への異常なリクエスト (不正な認証ヘッダ・SQLメタ文字)を過去 30〜90日分捜索。WAF/SIEM があれば該当パスのアラート発火履歴を確認。
3
Apply patch patch
```
Upgrade glances to 4.5.4
```
ステージング環境で 4.5.4 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスと、Step 2 で見つけた異常検知の続報チェックを含めること。
4
Post-deployment verification verify
```
Replay attack against GET /ssrf-poc on staging to confirm patch closes the vector
```
パッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番では Step 2 と同じログクエリでアラート再発が無いか継続監視。

Affected packages

PyPI glances

[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"4.5.4"}]}]

Fix status by distribution

Fixed packages published by each distribution for this CVE

Debian DEBIAN-CVE-2026-35587 glances
Ubuntu UBUNTU-CVE-2026-35587 glances

References

advisory nvd.nist.gov
package github.com
web github.com
web github.com
web github.com