Bing SVG Flaw Ran Code as SYSTEM on Microsoft Servers

Security firm XBOW submitted a crafted SVG to Bing’s image search and watched it execute commands as NT AUTHORITY\SYSTEM on Microsoft’s production Windows image-processing workers — and as root on Linux machines in the same fleet. The firm tested across multiple hosts and network ranges and got the same result each time, putting the problem in Bing’s image-processing tier rather than on any single misconfigured machine.

Microsoft issued multiple critical CVEs in response to XBOW’s findings. CVE-2026-32194, rated CVSS 9.8, is the confirmed identifier for the primary RCE path on the Windows side. Patches are deployed across the affected infrastructure. There is nothing to patch on the end-user side — Bing is a Microsoft-operated service and the fixes are theirs to ship, which they have.

SVG is an XML-based format with a history of causing trouble when processed by permissive parsers in privileged contexts — it can carry external resource references, scripting elements, and rendering directives that different parsers interpret differently. None of that is obscure; server-side processing of user-supplied document formats has been a recurring source of critical bugs for the better part of two decades. What the XBOW finding adds to that familiar category is the privilege level: a worker process running as SYSTEM or root removes any containment boundary that might otherwise limit blast radius. XBOW didn’t find a bug on one box — they found that the privilege assumption made the bug as severe as it could be, fleet-wide.

Microsoft has been carrying a lot of surface-level exposure this month. The SharePoint CVE-2026-50522 deserialization flaw hit CISA’s KEV catalog on July 22, with follow-on exploitation for machine key theft. The Azure DevOps MCP prompt-injection issue landed the same week. The Bing image tier finding is different in character — classic server-side code execution, not agentic or session-layer — but the pattern of service-level bugs where Microsoft’s own infrastructure is the attack surface has been consistent.

Patches are deployed. The XBOW team’s account of their testing methodology is in The Hacker News writeup for anyone who wants the technical depth.