Security researchers have uncovered a critical vulnerability in Bing’s image processing system, where specially crafted SVG files could execute commands with elevated privileges. These SVG files, when submitted to Bing’s image search, were able to run commands as NT AUTHORITYSYSTEM on Microsoft’s servers and as root on associated Linux machines.
Discovery and Impact
The flaw was identified by XBOW, a startup specializing in offensive security. Their tests indicated that the issue was widespread across various hosts and network ranges, implicating Bing’s image processing tier rather than individual machines. Microsoft addressed the issue by releasing two critical Common Vulnerabilities and Exposures (CVEs), CVE-2026-32194 and CVE-2026-32191, both scoring 9.8 on the Common Vulnerability Scoring System (CVSS) scale.
These vulnerabilities were reported privately by XBOW, and Microsoft resolved them server-side before making any public advisories in March. It was confirmed that no customer intervention was required, as the necessary fixes had already been implemented.
Technical Breakdown of the Flaw
The flaw originated from the system’s misinterpretation of an image as a command. SVG files, which are XML-based, can reference other images. If a renderer follows these references, it could inadvertently execute commands. This vulnerability was particularly severe in systems utilizing ImageMagick or similar software, where attacker-controlled content could reach a delegate-enabled path.
The problem was exacerbated by Bing’s reverse image search functionality, which fetched image URLs from the backend. This setup resulted in a blind Server-Side Request Forgery (SSRF) with the potential for downstream parsing errors that could execute commands.
Preventative Measures and Recommendations
To mitigate such vulnerabilities, it is crucial to deny delegates in policy settings and limit the accepted file formats, especially those that can include references, like SVG. Additionally, reviewing and disabling unnecessary enabled delegates in configuration files and running conversions in a sandboxed environment with limited privileges are recommended practices.
Further, outbound network access from the worker should be restricted, preventing any server-side fetches from reaching unauthorized destinations. This approach transforms a blind bug into a managed one, reducing the risk of exploitation.
Future Outlook
ImageMagick’s past vulnerabilities, such as the 2016 ImageTragick incident, highlight the persistent risk of command injection attacks in image processing systems. Continuous vigilance and strict policy adherence are essential to safeguard against similar threats.
As XBOW’s CISO Nico Waisman noted, image helpers are often overlooked as part of the attack surface. However, attackers view them as potential parsers, capable of executing unintended actions. This incident emphasizes the need for robust security measures in handling untrusted content.
