What is the CVSS score of CVE-2026-0533?

CVE-2026-0533 has a CVSS 3.1 base score of 8.1 (High). CVSS vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:N. EPSS exploitation probability: 0.0%.

Which versions of Autodesk Fusion are affected by CVE-2026-0533?

Autodesk Fusion contains a stored cross-site scripting vulnerability that allows attackers to embed malicious content in design file names, potentially enabling unauthorized file access or code…. A patch is available.

How to fix or mitigate CVE-2026-0533?

Within 24 hours: Inventory all Autodesk Fusion installations and assess exposure to externally sourced design files. Within 7 days: Apply vendor patch available per Autodesk security advisory to all affected Fusion deployments. Within 30 days: Conduct post-deployment verification and review design collaboration access controls to limit file uploads from untrusted sources.

Autodesk Fusion CVE-2026-0533

HIGH

Cross-site Scripting (XSS) (CWE-79)

2026-01-22 psirt@autodesk.com

XSS RCE Fusion

8.1

CVSS 3.1 · NVD

Severity by source

NVD PRIMARY

8.1 HIGH

AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:N

Primary rating from NVD · only source for this CVE.

CVSS VectorNVD

CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:N

Attack Vector

Network

Attack Complexity

Low

Privileges Required

None

User Interaction

Required

Scope

Unchanged

Confidentiality

High

Integrity

High

Availability

None

Lifecycle Timeline

Analysis Updated

Jun 03, 2026 - 14:38 vuln.today

v3 (cvss_changed)

Analysis Updated

Jun 03, 2026 - 14:37 vuln.today

v2 (cvss_changed)

Re-analysis Queued

Jun 03, 2026 - 14:22 vuln.today

cvss_changed

CVSS changed

Jun 03, 2026 - 14:22 NVD

7.1 (HIGH) 8.1 (HIGH)

Analysis Generated

Mar 12, 2026 - 21:54 vuln.today

Patch released

Jan 30, 2026 - 17:07 nvd

Patch available

CVE Published

Jan 22, 2026 - 17:16 nvd

HIGH 7.1

DescriptionCVE.org

A maliciously crafted HTML payload in a design name, when displayed during the delete confirmation dialog and clicked by a user, can trigger a Stored Cross-site Scripting (XSS) vulnerability in the Autodesk Fusion desktop application. A malicious actor may leverage this vulnerability to read local files or execute arbitrary code in the context of the current process.

AnalysisAI

Stored cross-site scripting in the Autodesk Fusion desktop application allows remote attackers to embed a malicious HTML payload in a design name that executes when a user opens the delete confirmation dialog and clicks the rendered content. Successful exploitation can lead to local file disclosure or arbitrary code execution in the context of the Fusion process. No public exploit identified at time of analysis, and EPSS exploitation probability is low (0.04%, 11th percentile).

Technical ContextAI

The flaw is a CWE-79 Improper Neutralization of Input During Web Page Generation (Cross-site Scripting) issue in the Autodesk Fusion desktop client (cpe:2.3:a:autodesk:fusion:*). Fusion is a hybrid desktop/cloud CAD/CAM/CAE platform that renders UI elements such as dialogs using an embedded web/Chromium-style rendering layer, meaning HTML supplied as a design name is interpreted rather than escaped when shown in the delete confirmation dialog. Because the rendering context is the desktop process itself rather than a sandboxed browser tab, injected script can reach beyond the DOM to read local files and invoke native code paths, escalating a classic stored XSS into an RCE-grade primitive.

RemediationAI

Patch available per vendor advisory: update the Autodesk Fusion desktop client to the fixed build referenced in ADSK-SA-2026-0001 (https://www.autodesk.com/trust/security-advisories/adsk-sa-2026-0001) using the official downloaders for macOS (Fusion Client Downloader.dmg) and Windows (Fusion Client Downloader.exe). Because the trigger is a delete confirmation dialog on a design name, an interim compensating control is to instruct users not to delete designs that originated from untrusted collaborators or shared team hubs and to rename suspicious designs through the project tree before invoking the delete action - note this is procedural and does not remove the underlying rendering flaw. Where feasible, restrict design sharing into Fusion Teams/Hubs to vetted accounts and remove untrusted external collaborators until all endpoints are confirmed patched, accepting the collaboration friction this introduces.