Local command execution via unsanitized AMP configuration
Published Jun 25, 2026 · Updated Jun 25, 2026
Command injection in Glances 4.0.8 through 4.5.4 allows local users to execute commands through malicious AMP configuration values. The default and SystemV AMP paths pass command and service_cmd values to secure_popen, which splits && and | into subprocesses and opens the path after > for writing without validation. Exploitation requires write access to glances.conf and runs commands or writes files with the Glances process user's permissions.
Summary
What happened
Command injection in Glances 4.0.8 through 4.5.4 allows local users to execute commands through malicious AMP configuration values. The default and SystemV AMP paths pass command and service_cmd values to secure_popen, which splits && and | into subprocesses and opens the path after > for writing without validation. Exploitation requires write access to glances.conf and runs commands or writes files with the Glances process user's permissions.
The record
- CVE
- CVE-2026-53925
- Published
- Jun 25, 2026
- Updated
- Jun 25, 2026
- Vendor
- Glances Project
- Product
- Glances
- Classifications
- CWE-22, T1059
- Attack vector
- local
- Privileges
- Unavailable
Timeline
How it unfolded
- Jun 25, 2026CVE publishedPublication date reported by the CVE source.
- Jun 25, 2026Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=>= 4.0.8, < 4.5.5
What conditions does exploitation require?
What is affected?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
- Upstream clean-checkout AMP file-write proof of conceptproof of concept · demonstrated
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo