CVE-2026-0535: Autodesk Fusion Stored XSS Vulnerability

CVE-2026-0535 Overview

A stored Cross-Site Scripting (XSS) vulnerability exists in the Autodesk Fusion desktop application that allows attackers to inject malicious HTML payloads through component descriptions. When a user views and interacts with a component containing a crafted malicious description, the stored XSS payload executes within the context of the desktop application. This vulnerability can be exploited to read local files from the victim's system or execute arbitrary code within the current process context, making it a significant threat to users working with shared or imported Fusion projects.

Critical Impact

Attackers can leverage this stored XSS vulnerability to achieve local file disclosure and arbitrary code execution within the Autodesk Fusion desktop application, potentially compromising sensitive design data and system integrity.

Affected Products

• Autodesk Fusion Desktop Application (Windows)
• Autodesk Fusion Desktop Application (macOS)

Discovery Timeline

• 2026-01-22 - CVE-2026-0535 published to NVD
• 2026-01-22 - Last updated in NVD database

Technical Details for CVE-2026-0535

Vulnerability Analysis

This vulnerability is classified as CWE-79 (Improper Neutralization of Input During Web Page Generation), specifically a stored XSS variant that persists within the application's data model. The Autodesk Fusion desktop application fails to properly sanitize HTML content within component description fields before rendering them in the user interface. When malicious HTML or JavaScript payloads are embedded in a component's description, they are stored persistently and executed each time a user views or interacts with that component.

The desktop application context makes this vulnerability particularly dangerous compared to typical web-based XSS. Because Fusion runs as a native desktop application with elevated privileges, successful exploitation can break out of typical browser sandbox restrictions, enabling attackers to access local file systems and execute code with the permissions of the current user process.

Root Cause

The root cause of this vulnerability is insufficient input validation and output encoding for user-supplied content in component description fields. The application accepts and stores raw HTML content without proper sanitization, and subsequently renders this content in a context that allows script execution. This failure to implement proper Content Security Policy (CSP) controls or HTML encoding in the desktop application's rendering engine creates the attack surface for stored XSS exploitation.

Attack Vector

The attack requires local access to the system and user interaction to be successful. An attacker must first craft a malicious component with an XSS payload embedded in its description field. This malicious component can then be shared through collaborative features, exported project files, or component libraries. When a victim opens a project containing the malicious component and interacts with it (such as viewing the component details), the stored payload executes in the context of the Fusion application process.

The local attack vector combined with the requirement for user interaction means an attacker would typically need to convince a victim to import or open a shared project file containing the weaponized component. Once executed, the payload can leverage the desktop application's capabilities to read sensitive local files or execute arbitrary commands on the system.

Detection Methods for CVE-2026-0535

Indicators of Compromise

• Unexpected <script> tags, event handlers (e.g., onerror, onclick), or iframe elements within Fusion component description fields
• Fusion project files (.f3d, .f3z) containing suspicious HTML or JavaScript content in metadata
• Unusual file system access patterns originating from the Autodesk Fusion process
• Network connections from the Fusion application to unexpected external domains

Detection Strategies

• Implement file integrity monitoring for Fusion project files to detect modifications that may introduce malicious payloads
• Monitor Autodesk Fusion process behavior for anomalous child process spawning or file system access outside normal operational patterns
• Deploy endpoint detection rules to alert on script execution or suspicious API calls originating from the Fusion application context
• Scan shared Fusion component libraries and project files for embedded HTML/JavaScript content

Monitoring Recommendations

• Enable detailed logging for the Autodesk Fusion application and review logs for suspicious rendering or script execution events
• Monitor network traffic from the Fusion desktop application for data exfiltration attempts to unknown external endpoints
• Implement user activity monitoring to track interactions with shared or imported Fusion projects from untrusted sources
• Configure SentinelOne Singularity to detect and alert on behavioral anomalies from the Autodesk Fusion process

How to Mitigate CVE-2026-0535

Immediate Actions Required

• Update to the latest version of Autodesk Fusion by downloading the patched installer from Autodesk's official channels
• Avoid opening Fusion projects or components from untrusted or unknown sources until patching is complete
• Review any recently imported components or shared projects for suspicious content in description fields
• Notify users in collaborative environments about the vulnerability and restrict sharing of projects until systems are patched

Patch Information

Autodesk has released security updates to address this vulnerability. Users should download and install the latest Autodesk Fusion client from the official Autodesk distribution channels. For detailed patch information and affected version specifics, refer to the Autodesk Security Advisory ADSK-SA-2026-0001.

• Windows users can obtain the updated installer from the Autodesk Fusion Client EXE Installer
• macOS users can obtain the updated installer from the Autodesk Fusion Client DMG Installer

Workarounds

• Implement strict controls on Fusion project file sharing, only accepting files from verified and trusted sources
• Review component descriptions manually before interacting with imported projects, particularly those from external collaborators
• Consider using network isolation for systems running Autodesk Fusion when working with untrusted project files
• Deploy endpoint protection solutions capable of detecting and blocking XSS-based attacks and anomalous application behavior