PatchSiren

PatchSiren cyber security CVE debrief

CVE-2026-62982 nicolargo CVE debrief

CVE-2026-62982 is a high-severity vulnerability in Glances, an open-source system monitoring tool. The issue, fixed in version 4.5.6, allows for arbitrary code execution through administrator-configured action templates due to improper sanitization of user input. This vulnerability exists in Glances versions from 4.5.2 to 4.5.5 and is caused by the _sanitize_mustache_dict() function in glances/actions.py not properly sanitizing nested list and dictionary strings, such as process cmdline values.

Vendor
nicolargo
Product
glances
CVSS
HIGH 8.8
CISA KEV
Not listed in stored evidence
Original CVE published
2026-08-17
Original CVE updated
2026-09-18
Advisory published
2026-08-17
Advisory updated
2026-09-18

Who should care

System administrators and security teams responsible for monitoring and maintaining Glances installations should assess exposure and prioritize verification and remediation efforts.

Why it matters

CVE-2026-62982 is a high-severity vulnerability in Glances that allows for arbitrary code execution through administrator-configured action templates. Defenders should prioritize verifying and upgrading to Glances version 4.5.6 or later, and review administrator-configured action templates for potential vulnerabilities.

  • Potential for arbitrary code execution through administrator-configured action templates
  • Need for verification of Glances version and administrator-configured action templates
  • Possible impact on system security and integrity if left unremediated

Technical summary

The _sanitize_mustache_dict() function in glances/actions.py does not properly sanitize nested list and dictionary strings, such as process cmdline values, allowing pipe characters to survive chevron.render() and be executed by secure_popen() through administrator-configured action templates. This issue allows for arbitrary code execution and is fixed in Glances version 4.5.6. The vulnerability has a high severity and requires immediate attention from system administrators and security teams responsible for monitoring and maintaining Glances installations.

Defensive priority

Defenders should prioritize verifying and upgrading to Glances version 4.5.6 or later, and review administrator-configured action templates for potential vulnerabilities.

Recommended defensive actions

  • Verify and upgrade to Glances version 4.5.6 or later
  • Review administrator-configured action templates for potential vulnerabilities
  • Monitor for suspicious activity in Glances installations
  • Confirm whether affected product deployments exist in managed environments and assign an owner for follow-up
  • Review the supplied official advisory or CVE record to validate affected scope, severity, and vendor guidance
  • Plan vendor-supported updates or mitigations through normal change control where exposure is confirmed
  • Check relevant monitoring, detection, and logs for exposed assets that need extra review

Evidence notes

The vulnerability exists in Glances versions from 4.5.2 to 4.5.5 due to the _sanitize_mustache_dict() function in glances/actions.py not properly sanitizing nested list and dictionary strings, such as process cmdline values. This allows pipe characters to survive chevron.render() and be executed by secure_popen() through administrator-configured action templates.

Sources and references

Verified primary and authoritative sources

  • CVE-2026-62982 CVE Program record

    Publisher, destination, and source semantics verified

    URL: https://www.cve.org/CVERecord?id=CVE-2026-62982

    CVE Program - Official CVE Program record with source-provided CVE metadata.

  • CVE-2026-62982 NVD vulnerability detail

    Publisher, destination, and source semantics verified

    URL: https://nvd.nist.gov/vuln/detail/CVE-2026-62982

    NIST National Vulnerability Database - Official NIST NVD detail page and source-specific vulnerability assessment.

Supplemental references

Methodology and review provenance

AI-assisted synthesis based on stored public vulnerability evidence. System validation, approval state, and publication status do not by themselves establish human review of this revision. PatchSiren helps prioritize defensive review and does not prove exposure or remediation on any system.