# CVE-2026-40032: UAC < 3.3.0-rc1 Command Injection via Placeholder Substitution


- **Severity:** High 8.5 (`CVSS:4.0/AV:L/AC:L/AT:N/PR:N/UI:P/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N`)
- **Exploited in the wild:** Not known
- **Fix available:** No
- **Published:** 8 Apr 2026
- **Updated:** 23 Jun 2026
- **Also known as:** GHSA-vv2j-m83f-q33j

## What is CVE-2026-40032?

CVE-2026-40032 is a high-severity vulnerability in tclahr UAC, published on 8 Apr 2026. 

### Official description

UAC (Unix-like Artifacts Collector) before 3.3.0-rc1 contains a command injection vulnerability in the placeholder substitution and command execution pipeline where the _run_command() function passes constructed command strings directly to eval without proper sanitization. Attackers can inject shell metacharacters or command substitutions through attacker-controlled inputs including %line% values from foreach iterators and %user% / %user_home% values derived from system files to achieve arbitrary command execution with the privileges of the UAC process.

Weakness: CWE-78 (Improper Neutralization of Special Elements used in an OS Command)

## Which versions are affected by CVE-2026-40032?


## How do I fix CVE-2026-40032?

No fix has been published for CVE-2026-40032 yet. Limit exposure of the affected software until one is available.

## Is CVE-2026-40032 being exploited?

There is no known exploitation of CVE-2026-40032 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-40032 and fix it if it is affected.

What it is: CVE-2026-40032 is a high-severity vulnerability in tclahr UAC, published on 8 Apr 2026. 
Exploitation: There is no known exploitation of CVE-2026-40032 in the wild and no public exploit code.

Affected product: tclahr UAC. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-40032/ (Markdown: https://insights.sbomify.com/CVE-2026-40032/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-40032
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-40032
- OSV: https://osv.dev/vulnerability/CVE-2026-40032

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-40032/
Summaries are generated and may contain mistakes; the official description above is the record.