CVE-2026-68518 is an OS command-injection vulnerability in Glances versions before 4.5.6. The action-template sanitization routine sanitizes individual Mustache values before rendering, rather than validating the fully rendered command. Consequently, adjacent unescaped Mustache variables can combine attacker-controlled field values to reconstruct shell-significant operators. The resulting rendered action command is passed to the process-execution mechanism, enabling injected shell syntax to be interpreted.
Mallory correlates every CVE against your assets, your vendors, and active adversary campaigns. Know which vulnerabilities matter for you, not just which ones are loud.
What it means. What to do now. Patch path, mitigations, and the assume-compromise checklist.
What an attacker gets, and what they’ve been doing with it.
If you can’t patch tonight, do this now.
Patch, then assume compromise.
No public exploits tracked yet. Mallory keeps watching.
No public exploit code observed for this vulnerability.
Products and vendors Mallory has correlated with this vulnerability. Open in Mallory to drill down to specific CPE configurations and version ranges.
Vendor-confirmed product mapping. Mallory continuously reconciles this list against your asset inventory.
5 sources tracked across advisories, community write-ups, and news. New activity surfaces here as Mallory finds it.
A command injection vulnerability in Glances prior to version 4.5.6, caused by improper sanitization of Mustache template values that can allow shell operators to be reconstructed and executed via administrator-configured action templates.
A high-severity command-injection vulnerability in Glances before version 4.5.6. Attacker-controlled process or container fields can reconstruct shell operators in Mustache action templates, resulting in commands being executed by secure_popen().
Query your assets running an affected version, and investigate the blast radius.
Every observed campaign linking this CVE to a named adversary.
Malware families riding this exploit, with evidence and IOCs.
YARA, Sigma, Snort, and vendor rules, auto-deployed to your SIEM.
Cross-references every affected SKU, including bundled OEM variants.
Community discussion across Reddit, Mastodon, and other social sources.