Autodesk Fusion CVE-2026-0534

Exploitation requires the attacker to author or modify a Fusion design so that a malicious HTML payload is persisted in a part's attribute, then deliver that design to a victim running the Fusion desktop application; the victim must then click the element bearing the poisoned attribute (CVSS UI:R), which limits drive-by scenarios. No authentication to the victim's instance is required (PR:N), and no special non-default configuration is called out in the description - any Fusion desktop install that opens the malicious part is in scope. Practical limits: the attacker needs a delivery channel for the malicious design (shared project, parts library, email attachment) and the victim must interact with the crafted element, so workstations that only open internally-produced designs face materially lower exposure.

The CVSS 3.1 score of 8.1 (AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:N) reflects a network-reachable, low-complexity, unauthenticated attack that requires user interaction (clicking the malicious element) and yields high confidentiality and integrity impact with no availability impact. However, EPSS is only 0.02% (4th percentile) and the CVE is not on the CISA KEV list, indicating no observed mass exploitation; combined with the UI:R requirement and the need to deliver a poisoned design file or shared part to a victim, real-world risk is moderate and targeted rather than wormable. The CVSS network vector is somewhat aspirational for a desktop CAD app - exploitation realistically depends on social engineering or supply-chain delivery of a malicious Fusion design - and security teams should weight this as a credible threat to engineering workstations handling untrusted CAD files rather than an internet-facing emergency.

An attacker authoring a Fusion design embeds a malicious HTML/JavaScript payload in a part attribute and shares the file via a collaboration link, email, or compromised parts library; when a victim opens the design and clicks the affected element, the stored payload executes in the Fusion process and can read local files or run arbitrary code as the user. No public exploit identified at time of analysis, but the attack pattern is well understood and straightforward for an attacker who can author Fusion content.