dbcve.org
3ds MaxApplication · Autodesk

CVE-2026-0662

HIGH · 7.8 CVSS v3.1 Published 2026-02-04
Fix available
A fix is available. Upgrade to 2026.3.2 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 project directory, when opening a max file in Autodesk 3ds Max, could lead to execution of arbitrary code in the context of the current process due to an Untrusted Search Path being utilized.

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

This is an Untrusted Search Path vulnerability in Autodesk 3ds Max. When a user opens a specially crafted .max file from a malicious project directory, the application loads DLLs or other resources from that untrusted location instead of verified system paths, allowing arbitrary code execution in the context of the current process.

MitigationApply the vendor security patch from Autodesk. Until patched, avoid opening .max files from untrusted or unknown project directories, and ensure the working directory when launching 3ds Max is trusted.

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.2

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, go to Help > About Autodesk 3ds Max, or check the installed programs list in Windows Settings > Apps & Features. Note the full version number displayed.
    Affected if The version displayed is 2026.0.0 through 2026.3.1 (meaning >= 2026 but < 2026.3.2)
  2. Confirm version via executable
    Right-click the 3ds Max executable (3dsmax.exe) in the installation folder, select Properties, and view the Details tab for the Product version.
    Affected if Product version shows 2026.0.0 through 2026.3.1
  3. Identify how you launch .max files
    Check whether you typically open .max files by double-clicking them in Windows Explorer (which sets the file's directory as the working directory) or by opening 3ds Max first and then using File > Open.
    Affected if You commonly double-click .max files from project folders, or your workflow involves opening files from untrusted or unknown project directories
  4. Review project directory trust status
    Audit the folders where your .max project files reside. Identify any project directories that contain .max files but are not on a trusted internal network share or verified local drive.
    Affected if You have .max files in directories that are not verified as trusted (e.g., downloaded archives, shared drives, or unfamiliar project folders)
  5. Check working directory at launch
    Before opening any .max file, verify your current working directory by opening Command Prompt and running 'cd' to see the active path, or check the launch shortcut properties.
    Affected if The working directory when launching 3ds Max points to an untrusted location or a folder containing untrusted .max files

You are affected if your installed 3ds Max version is 2026.0.0 through 2026.3.1 and you open .max files from untrusted or unknown project directories.

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.2 or later
Fixed in 2026.3.2
Interim mitigation

Apply the vendor security patch from Autodesk. Until patched, avoid opening .max files from untrusted or unknown project directories, and ensure the working directory when launching 3ds Max is trusted.

Recommended fix High confidence

3ds Max 2026.3.2 or later

  1. Back up any important projects and files before updating
  2. Download Autodesk 3ds Max version 2026.3.2 or later from the official Autodesk website (www.autodesk.com)
  3. Run the installer for the updated version and follow the installation prompts
  4. After installation completes, verify the version by opening 3ds Max and checking Help > About Autodesk 3ds Max
  5. Test that opening max files works correctly in the updated version

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

Fix this in 3ds Max Scoped from the published advisory
  • Consultation2.0 h
  • Implementation1.0 h
  • Testing4.0 h
  • Review / QA2.0 h
9.0 hours of engineering $1,540
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-0662 — 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-0662 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