dbcve.org
Path TraversalWeakness · CWE-22

CVE-2026-53925

HIGH · 7.8 CVSS v3.1 Published 2026-06-25
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
80/100
Remediation priority · High
Zero-click 8 weeks old

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
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.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

The secure_popen() function in glances/secure.py fails to sanitize shell operators (>, |, &&) when processing configuration values from glances.conf. An attacker who can modify the configuration file can inject arbitrary shell commands, write content to arbitrary filesystem paths, or chain/pipe commands through the AMP module's command execution.

MitigationUpgrade to Glances 4.5.5 or later to obtain the patched secure_popen() function. Additionally, restrict write access to the glances.conf configuration file to prevent unauthorized modification by untrusted users.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Local
Complexity
Low
Privileges
Low
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Verify Glances is installed
    Run `which glances` or `pip show glances` to locate the Glances installation.
    Affected if Glances is not installed on the system.
  2. Check the installed Glances version
    Run `glances --version` or `pip show glances | grep Version` to obtain the version number.
    Affected if The installed version is lower than 4.5.5.
  3. Locate the configuration file
    Check for glances.conf in typical locations: `/etc/glances/`, `~/.config/glances/`, or the current working directory. Use `find /etc -name glances.conf 2>/dev/null`.
    Affected if No glances.conf file exists on the system.
  4. Inspect AMP module configuration in glances.conf
    Open glances.conf and search for sections starting with [amp] to identify any AMP (Active Monitoring Plugin) entries that define commands to execute.
    Affected if The configuration contains [amp] sections with command definitions.
  5. Check write permissions on glances.conf
    Run `ls -la` on the glances.conf file to view permissions. Check if untrusted users or groups have write access (permissions showing 'w' for others or group).
    Affected if The configuration file is writable by untrusted users or the 'others' group.
  6. Examine secure_popen() function for shell operator handling
    Locate the file glances/secure.py in the Glances installation directory and inspect the secure_popen() function. Search for any filtering or removal of shell metacharacters like >, |, &&, ;, or $.
    Affected if The function does not sanitize shell operators or no filtering logic is present.

A system is affected if Glances version is below 4.5.5 AND the glances.conf file contains AMP configurations with command execution AND the configuration file is writable by untrusted users.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Upgrade to Glances 4.5.5 or later to obtain the patched secure_popen() function. Additionally, restrict write access to the glances.conf configuration file to prevent unauthorized modification by untrusted users.

Recommended fix High confidence

Glances 4.5.5

  1. Check current Glances version: glances --version or pip show glances
  2. Upgrade Glances to version 4.5.5 or later using pip: pip install --upgrade glances==4.5.5 or pip install --upgrade glances>=4.5.5
  3. Verify the upgrade was successful: glances --version

Generated from the published advisory — verify against the referenced sources before acting.

Have this fixed Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing3.0 h
  • Review / QA2.0 h
11.0 hours of engineering $1,930
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,088.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-53925 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2026-53925 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data