Command Injection in BOSH PackagePersister.validate_tgz
CVE-2026-41011 is a command injection vulnerability in BOSH's package processing path. In PackagePersister.validate_tgz, the code constructs a shell command of the form tar -tf #{tgz} 2>&1, where tgz is derived from File.join(release_dir, 'packages', "#{name}.tgz"). The name value comes directly from package_meta['name'] in release.MF inside an uploaded tarball. This command string is then passed to Bosh::Common::Exec.sh, which executes via %x{} and therefore /bin/sh -c. Because no Shellwords.escape or equivalent sanitization is applied, attacker-controlled shell metacharacters in the package name can alter command execution. Although the Models::Package Sequel validation (VALID_ID = /^[-0-9A-Za-z_+.]+$/i) would reject an invalid package name, that validation occurs too late: in create_package, the shell-out in save_package_source_blob executes before package.save, so the unsafe shell invocation is reachable prior to validation. Affected versions are all BOSH versions prior to v282.1.12.
Are you exposed to this one?
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.
Impact, mitigation & remediation
What it means. What to do now. Patch path, mitigations, and the assume-compromise checklist.
Impact
What an attacker gets, and what they’ve been doing with it.
Mitigation
If you can’t patch tonight, do this now.
release.MF package names. Where feasible, harden the execution environment of the BOSH component that processes packages by reducing privileges, isolating the service, and monitoring for anomalous shell execution during package import. However, these are only partial mitigations; upgrading is the definitive fix.Remediation
Patch, then assume compromise.
/bin/sh -c, and by ensuring validation occurs before any use of package metadata in command construction.Exploits
No public exploits tracked yet. Mallory keeps watching.
No public exploit code observed for this vulnerability.
Recent activity
7 sources tracked across advisories and community write-ups. News coverage will land here when it surfaces.
No news coverage yet. Advisories and community discussion only.
The version that knows your environment.
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.