3ds MaxApplication · Autodesk

CVE-2025-11797

HIGH · 7.8 CVSS v3.1 Published 2025-11-12
Fix available
A fix is available. Upgrade to 2026.3 or later.
See remediation →
81/100
Remediation priority · High
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 DWG file, when parsed through Autodesk 3ds Max, can force a Use-After-Free vulnerability. A malicious actor can leverage this vulnerability to cause a crash, read sensitive data, 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 Use-After-Free vulnerability exists in Autodesk 3ds Max when parsing maliciously crafted DWG files. The parser frees memory during processing but subsequently attempts to access that freed memory region, leading to memory corruption that can be leveraged for code execution or denial of service.

MitigationApply the vendor-supplied patch from Autodesk. Until patched, exercise caution with DWG files from untrusted sources and consider using file quarantine procedures for external DWG files.

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
3ds MaxApplication
Affected:>= 2026, < 2026.3

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
High

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

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. Check installed 3ds Max version
    Open 3ds Max and go to Help > About Autodesk 3ds Max, or right-click the 3dsmax.exe file and select Properties > Details to view the Product version
    Affected if The version listed is 2026, 2026.1, 2026.2, or any 2026.x version prior to 2026.3
  2. Verify DWG import capability is present
    Attempt to import a DWG file via File > Import or check if DWG/DXF import plugin is listed in 3ds Max plugin manager (Manage > Plugin Manager)
    Affected if DWG import functionality is available and enabled in the installation
  3. Confirm DWG file parsing occurs in your workflow
    Review recent file access logs or check for .dwg files in recent project directories, or simply note whether you or your team open DWG files in 3ds Max
    Affected if You process, open, or import DWG files using the affected 3ds Max version
  4. Identify DWG-related modules
    Check the 3ds Max installation directory (typically Program Files/Autodesk/3ds Max 2026/bin) for DLLs related to DWG parsing, such as dwg*.dll or ADSK*.dll files
    Affected if DWG parser DLLs are present in the 3ds Max bin directory

You are affected if your installed 3ds Max version is 2026 through 2026.2.x AND you import or process DWG files in your workflow.

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 2026.3 or later
Fixed in 2026.3
Interim mitigation

Apply the vendor-supplied patch from Autodesk. Until patched, exercise caution with DWG files from untrusted sources and consider using file quarantine procedures for external DWG files.

Recommended fix High confidence

3ds Max 2026.3

  1. Back up all critical projects and files before updating
  2. Navigate to the official Autodesk website or your Autodesk Account portal
  3. Download Autodesk 3ds Max version 2026.3 or later
  4. Run the installer and follow Autodesk's standard installation prompts to complete the update
  5. Launch 3ds Max and verify the version displays as 2026.3 or higher

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

Fix this in 3ds Max Scoped from the published advisory
  • Consultation4.0 h
  • Implementation16.0 h
  • Testing8.0 h
  • Review / QA4.0 h
32.0 hours of engineering $5,600
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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

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-2025-11797 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