Quick answers
- Is CVE-2026-53925 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-53925 being exploited in the wild.
- How severe is CVE-2026-53925?
- High severity, with a CVSS score of 7.8, published 25 June 2026.
- Which products and versions are affected?
- glances (PyPI) >= 4.0.8, < 4.5.5, ECOSYSTEM:introduced=4.0.8,fixed=4.5.5.
- Is there a fix for CVE-2026-53925?
- Yes. glances (PyPI): upgrade to 4.5.5 or later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
- How is CVE-2026-53925 attacked?
- It is attacked with local access, in a network appliance.
- Am I affected by CVE-2026-53925?
- Check whether you run glances (PyPI) at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.
How to fix
- glances (PyPI): upgrade to 4.5.5 or later
pip install "glances>=4.5.5"
Technical details
A vulnerability exists in the `secure_popen()` function within `glances/secure.py` due to the manual interpretation of shell operators including `>`, `|`, and `&&`. When Application Monitoring Process (AMP) modules load `command` or `service_cmd` values from `glances.conf`, these strings are passed to `secure_popen()` without sanitization. An attacker with the ability to modify the configuration file can achieve arbitrary file writes (via redirection) or command chaining. This flaw is distinct from CVE-2026-33641; the `--disable-config-exec` flag does not mitigate this issue as it only targets backtick execution in `config.get_value()`, whereas this vulnerability resides in the subsequent processing of the command string. The issue is resolved in version 4.5.5.
Affected products
- nicolargo Glances >= 4.0.8, < 4.5.5
Identifiers
- CVE-2026-53925
- GHSA-3vwc-qwhc-3mj7
- PYSEC-2026-2494
Timeline
- 2026-06-13: advisory: GitHub advisory published by maintainer
- 2026-06-25: disclosed: NVD publication date
- 2026-06-25: patched: Fixed in version 4.5.5