Skip to main content
Mallory
← Back to News
privilege-escalation-methodendpoint-software-vulnerabilitywidely-deployed-product-advisoryproof-of-concept-release

Qubes OS qvm-copy-to-vm Flaw Enabled Command Execution in Dom0

Attack Tradecraft · 5 sources · Updated 3mo ago · First seen Sep 8, 2026

Qubes OS qvm-copy-to-vm Flaw Enabled Command Execution in Dom0

Qubes OS fixed a vulnerability in qvm-copy-to-vm that could let an attacker execute arbitrary commands in the privileged Dom0 administrative domain through a specially crafted file name. Because Dom0 manages the isolated virtual machines, successful exploitation could result in full compromise of the host’s security boundary.

The flaw occurred when the file-transfer utility invoked localized kdialog or zenity dialogs via system() and passed attacker-controlled file and VM names into the command line. Validation did not safely handle certain non-ASCII characters, allowing shell metacharacters such as backticks and dollar signs to reach the shell; the fix is included in qubes-core-dom0-linux version 4.3.22.

Who uses this technique?Get the actors, campaigns, and ATT&CK mapping behind it.
Get the tradecraft
Event timeline

How this story unfolded

Events from the most recent confirmed update back to the earliest known activity.

1 event
  1. Reported Sep 8, 20263mo ago

    Qubes OS fixes Dom0 command-execution flaw in qvm-copy-to-vm

    Qubes OS fixed a vulnerability in qvm-copy-to-vm that could allow a crafted non-ASCII filename containing shell metacharacters to execute commands in the privileged Dom0 domain when localized kdialog or zenity dialogs were invoked through system(). The fix was released in qubes-core-dom0-linux version 4.3.22.

    ���������� � �� Qubes, ����������� ������ �������� � ��������� ��� �� ������ Dom0
Linked entities

Related entities

Vulnerabilities, threat actors, malware, products, organizations, and breaches Mallory has linked to this story.

Open in app →

Organizations

1 linked
Qubes OS
Do you run this?Get the adversaries, campaigns, and ATT&CK mapping behind this technique, with detections ready to deploy.
See Who Uses This Technique
Mallory platform

See the full picture, correlated to your attack surface.

This page covers what’s public. Mallory adds the parts that aren’t: which of your assets are affected, which threat actors are using it right now, and what to deploy next.

Exposure mappingMap indicators from this story to your assets and identify affected systems in minutes.
Threat actor evidenceEvery observed campaign, victim, and pivot linked to actors named in this story.
Associated malwareMalware, exploits, and IOCs connected to the activity described here.
Detection signaturesYARA, Sigma, and Snort rules deployed to your SIEM as soon as they’re published.
Scheduled alertsGet matching new stories delivered to your team as they break, not the next morning.
AI threadsAsk questions about this story and take action on the answers.