dbcve.org
FusionApplication · Autodesk

CVE-2026-4369

HIGH · 7.1 CVSS v3.1 Published 2026-04-14
Fix available
A fix is available. Upgrade to 2702.1.47 or later.
See remediation →
74/100
Remediation priority · Elevated
No privileges

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
A maliciously crafted HTML payload in an assembly variant 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.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · moderate confidence

A stored Cross-site Scripting vulnerability exists in Autodesk Fusion where malicious HTML/JavaScript embedded in an assembly variant name is rendered unsanitized in the delete confirmation dialog. When users interact with the dialog, the injected payload can execute with the application's privileges, enabling local file access and arbitrary code execution.

MitigationImplement context-aware output encoding/sanitization for all user-supplied data displayed in dialogs, particularly assembly variant names. Apply Content Security Policy headers to restrict script execution.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
FusionApplication
Affected:< 2702.1.47

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Local
Complexity
Low
Privileges
None
User interaction
Required
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
None

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

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Verify Autodesk Fusion installation and version
    Open Autodesk Fusion, navigate to Help > About Autodesk Fusion, or check the installed version via the desktop application properties. Compare the version number to the affected range (less than 2702.1.47).
    Affected if Fusion version is below 2702.1.47
  2. Confirm assembly variants feature usage
    In Fusion, open a design that uses assemblies. Navigate to the Browser panel and expand the assembly tree. Look for the 'Variants' folder or right-click an assembly component to see if 'Manage Variants' or similar option is available.
    Affected if The assembly variants feature is present and accessible in the Fusion interface
  3. Inspect existing assembly variant names
    Right-click on an assembly component, select Manage Variants, or access the variants panel. Review all variant names listed in the variants table or browser view.
    Affected if Any assembly variant exists in the project with a name containing HTML or script tags (e.g., <script>, javascript:, onload, onerror)
  4. Test delete confirmation dialog behavior
    Select an assembly that has variants, then initiate a delete operation (right-click > Delete or press Delete key). Observe the confirmation dialog that appears - check if the variant name is displayed in the dialog text without visible sanitization.
    Affected if The delete confirmation dialog renders the variant name in an editable field or as raw HTML without visible encoding

You are affected if Autodesk Fusion version is below 2702.1.47 AND the assembly variants feature is in use, particularly if any variant names could contain or were created with unsanitized input.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Upgrade available Upgrade to 2702.1.47 or later
Fixed in 2702.1.47
Interim mitigation

Implement context-aware output encoding/sanitization for all user-supplied data displayed in dialogs, particularly assembly variant names. Apply Content Security Policy headers to restrict script execution.

Recommended fix High confidence

2702.1.47 or later

  1. 1. Open Autodesk Fusion desktop application
  2. 2. Navigate to Help > Check for Updates or About Autodesk Fusion
  3. 3. If an update is available, download and install version 2702.1.47 or later
  4. 4. Alternatively, download the latest version from the official Autodesk website at www.autodesk.com or dl.appstreaming.autodesk.com
  5. 5. After updating, verify the version by checking Help > About Autodesk Fusion to confirm version 2702.1.47 or newer is installed
  6. 6. Restart the application to ensure all components are updated

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Fusion Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing6.0 h
  • Review / QA3.0 h
21.0 hours of engineering $3,680
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $5,888.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-4369 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2026-4369 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data