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.
CVE-2026-41449
Score 7.8 from GitHub Security Advisory (severity: HIGH) published 2026-08-21. a secondary CVSS source baseline 7.8; sources differ by 0.0.
- High severity, but no confirmed exploitation yet
No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.
- CVSS v3
- 7.8
- EG Score
- 7.8(high)
- EG Risk
- 40(Track)EG Risk 40/100SSVC: Track
EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).
How it’s computedSeverity78% × 45%Exploitation0% × 40%Automatability30% × 15%Action: Routine — remediate on your standard cadence. - EPSS PROB
- —
- EPSS %ILE
- —
- KEV
- Not listed
Published
August 21, 2026
Last Modified
August 21, 2026
Advisory Details (3)
Auto-updated Aug 21, 2026UAC < 3.3.0 Command Injection via run_command.sh | Advisories | VulnCheck
https://www.vulncheck.com/advisories/uac-command-injection-via-run-command-shcommit 2cc367d8ead3 (tclahr/uac)
Patch available: tclahr/uac v3.3.0 (contains commit 2cc367d8ead3)
https://github.com/tclahr/uac/commit/2cc367d8ead388f05abd3cfb8af537788a124e72fix: escape runtime placeholders before eval
Patch available: tclahr/uac v3.3.0 (PR #443 merged 2026-03-28)
https://github.com/tclahr/uac/pull/443Vendor Advisories for CVE-2026-41449(1)
These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.
Weakness Classification(1)
MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.
Data Freshness Timeline
(refreshed 5× in last 7d / 5× in last 30d)
Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.
- 2026-08-21 19:22 UTCEG score recompute
- 2026-08-21 19:21 UTCGHSA enrichment
- 2026-08-21 18:18 UTCEG score recompute
- 2026-08-21 17:40 UTCEG score recompute
- 2026-08-21 17:39 UTCMITRE cvelistV5first tracked
Frequently asked(4)
What is CVE-2026-41449?
When was CVE-2026-41449 disclosed?
What is the CVSS score of CVE-2026-41449?
How do I remediate CVE-2026-41449?
Dependency Blast Radius
Explore the affected products and dependency analysis for CVE-2026-41449
Is Your Infrastructure Affected by CVE-2026-41449?
EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.