CVE-2026-108744 MinaSaad1 CVE debrief

Who should care

Defenders responsible for pbi-cli deployments, particularly those using versions 3.10.1 through 3.12.0, should assess exposure and prioritize remediation. This includes verifying and remediating affected versions, restricting access to .pbip files, and monitoring for suspicious activity. Security teams and vulnerability management teams should also review the vulnerability and implement compensating controls where necessary.

Why it matters

Defenders should prioritize verifying and remediating pbi-cli versions 3.10.1 through 3.12.0 due to an OS command injection vulnerability that could allow an attacker to run commands with victim privileges.

• An attacker could run commands with victim privileges during report write or reload.
• Victims may be lured into opening a Power BI project from a space-free path containing & to exploit the vulnerability.
• The vulnerability requires verification of pbi-cli versions and potential remediation or compensating controls.

Technical summary

The pbi-cli 3.10.1 through 3.12.0 contains an OS command injection vulnerability in desktop_sync.py. Attackers can lure victims into opening a Power BI project from a space-free path containing & to run commands with victim privileges during report write or reload. The vulnerability requires verification of pbi-cli versions and potential remediation or compensating controls. This issue is particularly concerning because it can be exploited by luring victims into opening malicious Power BI projects, potentially leading to unauthorized command execution.

Defensive priority

Defenders should prioritize verifying and remediating pbi-cli versions 3.10.1 through 3.12.0, as an attacker could exploit this vulnerability to run commands with victim privileges.

Recommended defensive actions

• Verify pbi-cli versions 3.10.1 through 3.12.0 are not in use or apply vendor-provided patches.
• Restrict access to .pbip files and monitor for suspicious activity.
• Implement additional security measures, such as input validation and sanitization, to prevent similar vulnerabilities.
• Review compensating controls for exposed systems while remediation is scheduled and verified.
• Check relevant monitoring, detection, and logs for exposed assets that need extra review.
• Track exceptions, retest remediated assets, and close the item only after evidence is documented.
• Confirm whether affected product deployments exist in managed environments and assign an owner for follow-up.

Evidence notes

The CVE record and source item provide details on the OS command injection vulnerability in pbi-cli 3.10.1 through 3.12.0. The vulnerability is located in the desktop_sync.py file, which passes unquoted .pbip paths to cmd /c start when reopening projects.

Sources and references

Methodology and review provenance

AI-assisted synthesis based on stored public vulnerability evidence. System validation, approval state, and publication status do not by themselves establish human review of this revision. PatchSiren helps prioritize defensive review and does not prove exposure or remediation on any system.