# CVE-2026-113775: Dynamic Library Loading Process Control in Autodesk Fusion Desktop


- **Severity:** High 7.8 (`CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Fix available:** No
- **Published:** 27 Oct 2026
- **Updated:** 29 Oct 2026
- **Also known as:** GHSA-9833-v35h-4xgw

## What is CVE-2026-113775?

CVE-2026-113775 is a high-severity vulnerability in Autodesk Fusion, published on 27 Oct 2026. 

### Official description

A maliciously crafted dynamic library, when loaded from an arbitrary path through the TextCommands.LoadDll command exposed by the Autodesk Fusion API, can trigger an Exposed Dangerous Function vulnerability in the Autodesk Fusion desktop application. A malicious actor may leverage this vulnerability to execute arbitrary code in the context of the current process.

Weakness: CWE-749 (Exposed Dangerous Method or Function)

## Which versions are affected by CVE-2026-113775?


## How do I fix CVE-2026-113775?

No fix has been published for CVE-2026-113775 yet. Limit exposure of the affected software until one is available.

## Is CVE-2026-113775 being exploited?

There is no known exploitation of CVE-2026-113775 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-113775 and fix it if it is affected.

What it is: CVE-2026-113775 is a high-severity vulnerability in Autodesk Fusion, published on 27 Oct 2026. 
Exploitation: There is no known exploitation of CVE-2026-113775 in the wild and no public exploit code.

Affected product: Autodesk Fusion. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-113775/ (Markdown: https://insights.sbomify.com/CVE-2026-113775/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-113775
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-113775
- OSV: https://osv.dev/vulnerability/CVE-2026-113775

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-113775/
Summaries are generated and may contain mistakes; the official description above is the record.