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.
CVE-2026-53925
This high-severity CVE scores 7.8 under a secondary CVSS source (NVD's own analysis pending). EPSS exploit probability: 0.2%, top 92% of all CVEs by exploit prediction. GitHub Security Advisory data not yet ingested — confidence will rise once GHSA publishes (typical lag: hours to days for open-source ecosystem CVEs; never for infrastructure-only CVEs).
- High severity, but no confirmed exploitation yet
No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.
- CVSS v3
- 7.8
- EG Score
- 7.8(medium)
- EPSS
- 8.2%
- KEV
- Not listed
Published
June 23, 2026
Last Modified
June 25, 2026
Advisory Details (1)
Auto-updated Jun 25, 2026Arbitrary file write and command execution via `secure_popen` redirection and chaining operators in AMP command configuration · Advisory · nicolargo/glances · GitHub
https://github.com/nicolargo/glances/security/advisories/GHSA-3vwc-qwhc-3mj7Vendor Advisories for CVE-2026-53925(1)
These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.
Weakness Classification(1)
MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.
Data Freshness Timeline
(refreshed 25× in last 7d / 46× in last 30d)
Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.
- 2026-07-07 04:01 UTCEG score recompute
- 2026-07-06 16:31 UTCEG score recompute
- 2026-07-06 16:27 UTCEPSS rescore
- 2026-07-06 16:27 UTCEPSS rescore
- 2026-07-06 05:22 UTCEG score recompute
- 2026-07-06 02:23 UTCEPSS rescore
- 2026-07-06 02:23 UTCEPSS rescore
- 2026-07-05 18:17 UTCEG score recompute
- 2026-07-05 07:12 UTCEG score recompute
- 2026-07-05 02:31 UTCEPSS rescore
- 2026-07-05 02:30 UTCEPSS rescore
- 2026-07-04 20:01 UTCEG score recompute
- 2026-07-04 08:59 UTCEG score recompute
- 2026-07-04 06:31 UTCEPSS rescore
- 2026-07-04 06:31 UTCEPSS rescore
- 2026-07-03 21:55 UTCEG score recompute
- 2026-07-03 10:51 UTCEG score recompute
- 2026-07-02 23:41 UTCEG score recompute
- 2026-07-02 12:38 UTCEG score recompute
- 2026-07-02 01:32 UTCEG score recompute
- 2026-07-01 15:07 UTCEPSS rescore
- 2026-07-01 14:28 UTCEG score recompute
- 2026-07-01 03:25 UTCEG score recompute
- 2026-06-30 23:22 UTCEPSS rescore
- 2026-06-30 16:22 UTCEG score recompute
Show 21 moreShow fewer
- 2026-06-30 05:19 UTCEG score recompute
- 2026-06-29 18:16 UTCEG score recompute
- 2026-06-29 14:06 UTCEPSS rescore
- 2026-06-29 14:06 UTCEPSS rescore
- 2026-06-29 07:12 UTCEG score recompute
- 2026-06-28 20:09 UTCEG score recompute
- 2026-06-28 14:07 UTCEPSS rescore
- 2026-06-28 09:06 UTCEG score recompute
- 2026-06-28 04:56 UTCEPSS rescore
- 2026-06-28 04:56 UTCEPSS rescore
- 2026-06-27 22:03 UTCEG score recompute
- 2026-06-27 11:00 UTCEG score recompute
- 2026-06-27 03:08 UTCEPSS rescore
- 2026-06-26 23:57 UTCEG score recompute
- 2026-06-26 12:54 UTCEG score recompute
- 2026-06-26 01:51 UTCEG score recompute
- 2026-06-25 14:48 UTCEG score recompute
- 2026-06-25 03:44 UTCEG score recompute
- 2026-06-24 16:42 UTCEG score recompute
- 2026-06-24 05:39 UTCEG score recompute
- 2026-06-23 18:21 UTCEG score recompute
Related CVEs(same CWE)
Frequently asked(5)
What is CVE-2026-53925?
When was CVE-2026-53925 disclosed?
Is CVE-2026-53925 actively exploited?
What is the CVSS score of CVE-2026-53925?
How do I remediate CVE-2026-53925?
Dependency Blast Radius
Explore the affected products and dependency analysis for CVE-2026-53925
Is Your Infrastructure Affected by CVE-2026-53925?
EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.