# CVE-2026-53925: Glances has arbitrary file write and command execution via `secure_popen` redirection and chaining operators in AMP command configuration

> Attackers with config file access can execute arbitrary commands and write files via unsanitized operators in Glances AMP configurations.

- **Severity:** High 7.8 (`CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 25 Jun 2026
- **Updated:** 25 Jun 2026
- **Also known as:** DEBIAN-CVE-2026-53925, GHSA-3vwc-qwhc-3mj7, PYSEC-2026-2494, UBUNTU-CVE-2026-53925

## What is CVE-2026-53925?

CVE-2026-53925 is a high-severity command injection vulnerability in nicolargo glances, published on 25 Jun 2026. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

Glances is an open-source system cross-platform monitoring tool. From 4.0.8 until 4.5.5, the secure_popen() function in glances/secure.py interprets > (file redirection), | (pipe), and && (command chaining) operators in command strings. These operators are applied without any validation on the target file path, piped command, or chained command. When Application Monitoring Process (AMP) modules load their command or service_cmd configuration values from glances.conf, those values are passed directly to secure_popen() with no sanitization. This allows an attacker who can modify the Glances configuration file to write arbitrary content to arbitrary filesystem paths (via >), chain arbitrary commands (via &&), or pipe command output to arbitrary programs (via |). This vulnerability is fixed in 4.5.5.

Weakness: CWE-22 (Improper Limitation of a Pathname to a Restricted Directory)

## Which versions are affected by CVE-2026-53925?

3 open source packages ship an affected version, including glances.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `glances` | PyPI | From 4.0.8 | 4.5.5 |
| `glances` | PyPI | From 4.0.8 | 4.5.5 |
| `glances` | PyPI | From 4.0.8 | 4.5.5 |

## How do I fix CVE-2026-53925?

Upgrade glances to 4.5.5 or later.

## Is CVE-2026-53925 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-53925 exists.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-53925 and fix it if it is affected.

What it is: CVE-2026-53925 is a high-severity command injection vulnerability in nicolargo glances, published on 25 Jun 2026. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-53925 exists.

Affected packages and fixed versions:
- glances (PyPI): affected from 4.0.8; fixed in 4.5.5
- glances (PyPI): affected from 4.0.8; fixed in 4.5.5
- glances (PyPI): affected from 4.0.8; fixed in 4.5.5

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-53925/ (Markdown: https://insights.sbomify.com/CVE-2026-53925/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-53925
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-53925
- OSV: https://osv.dev/vulnerability/CVE-2026-53925

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-53925/
Summaries are generated and may contain mistakes; the official description above is the record.