Arbitrary command execution via unsafe placeholder evaluation
Published Apr 8, 2026 · Updated Apr 8, 2026
Command injection in UAC before 3.3.0-rc1 allows local users to execute arbitrary shell commands through crafted placeholder values. The _run_command() pipeline evaluates command strings after foreach, user, and home-directory values are substituted without shell-safe quoting. Exploitation requires a crafted value to be consumed during collection, and commands run with the privileges of the UAC process.
Summary
What happened
Command injection in UAC before 3.3.0-rc1 allows local users to execute arbitrary shell commands through crafted placeholder values. The _run_command() pipeline evaluates command strings after foreach, user, and home-directory values are substituted without shell-safe quoting. Exploitation requires a crafted value to be consumed during collection, and commands run with the privileges of the UAC process.
The record
- CVE
- CVE-2026-40032
- Published
- Apr 8, 2026
- Updated
- Apr 8, 2026
- Vendor
- Thiago Canozzo Lahr
- Product
- Unix-like Artifacts Collector (UAC)
- Classifications
- CWE-78, T1059
- Attack vector
- local
- Privileges
- Unavailable
Timeline
How it unfolded
- Apr 8, 2026CVE publishedPublication date reported by the CVE source.
- Apr 8, 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=0 <=3.2.0
What conditions does exploitation require?
What is affected?
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
No public exploit references are available in this record.
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