Loading vulnerability…
CVE-2026-16658 is an OS command injection vulnerability in the community.proxmox Ansible collection's proxmox_pct_remote connection plugin. Its _build_pct_command() method builds a pct exec command through unquoted string concatenation and submits it to the Proxmox host shell using Paramiko. Shell metacharacters in values incorporated into the constructed command can therefore be evaluated by the hypervisor shell rather than being passed as data to the intended LXC container.
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.
What it means. What to do now. Patch path, mitigations, and the assume-compromise checklist.
What an attacker gets, and what they’ve been doing with it.
No public exploits tracked yet. Mallory keeps watching.
No public exploit code observed for this vulnerability.
Products and vendors Mallory has correlated with this vulnerability. Open in Mallory to drill down to specific CPE configurations and version ranges.
Vendor-confirmed product mapping. Mallory continuously reconciles this list against your asset inventory.
2 sources tracked across advisories, community write-ups, and news. New activity surfaces here as Mallory finds it.
A medium-severity command-injection flaw in the community.proxmox Ansible collection's proxmox_pct_remote connection plugin. Improper shell quoting in the exec path lets shell metacharacters escape the intended LXC-container context and execute on the Proxmox hypervisor host as root, crossing the container-to-host trust boundary.
An unpatched vulnerability identified as CVE-2026-16658, detected by a Unix-focused assessment plugin. The reference associates it with Ubuntu Linux, Debian Linux, and their Ansible/ansible-core packages, but does not describe the flaw type or impact.
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.