Skip to main content
VulnerabilityPublished Updated

CVE-2026-35587: Glances IP Plugin has SSRF via public_api that leads to credential leakage

Affects glancesSource GCVE Database

0
Compare
Authoritative record:CVE-2026-35587· High 7.3

Public exploit available · CVSS 7.3 High : upgrade to 4.5.6 as a priority.

Data as of 9 Nov 2026, 19:50 UTC

CVSS 4.0 base score
7.3High
How severe the flaw is on the 0–10 CVSS scale.
Patch
Available – fixed in 4.5.6
CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:H/VI:H/VA:N/SC:N/SI:N/SA:N/E:P

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 20 Apr 2026

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponized: evidence found.

    CVSS exploit maturity: proof of concept public

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), CVSS vector, the Metasploit, Exploit-DB and nuclei-templates index as of 9 Nov 2026.

What to do

Upgrade glances to 4.5.6.

Affected software

ProductAffectedFixed in
Homebrewglancespkg:brew/glancesOther threatsAffected
  • <4.5.6
Fixed in
  • 4.5.6

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

AI-suggested

Upgrade Glances to version 4.5.6 or later, which contains the official fix for this SSRF vulnerability. Until patched, restrict access to configuration modification to trusted users only. No other vendor-specified mitigations are indicated.

Description

Glances versions prior to 4.5.6 contain a Server-Side Request Forgery (SSRF) vulnerability in the IP plugin due to improper validation of the public_api configuration parameter. This flaw allows an attacker who can modify the configuration to make the application send HTTP requests to arbitrary endpoints, potentially accessing internal services or cloud metadata. When public_username and public_password are configured, these credentials are included in outbound requests, leading to credential leakage. Version 4.5.6 includes a patch that fixes this issue.

References

Community reviews

Loading reviews…