3ds MaxApplication · Autodesk

CVE-2026-0661

HIGH · 8.4 CVSS v3.1 Published 2026-02-04
Fix available
A fix is available. Upgrade to 2026.3.2 or later.
See remediation →
89/100
Remediation priority · High
No privileges Zero-click

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 RGB file, when parsed through Autodesk 3ds Max, can force a Memory Corruption vulnerability. A malicious actor can leverage this vulnerability to 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 · high confidence

Autodesk 3ds Max contains a memory corruption vulnerability in its RGB file parsing functionality. A specially crafted RGB file with malformed data triggers the memory corruption during parsing, allowing a malicious actor to achieve arbitrary code execution in the context of the current process.

MitigationRestrict or disable RGB file processing in 3ds Max environments until the vendor patch is applied. Sanitize or whitelist file types accepted in production 3ds Max workflows.

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
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:L/AC:L/PR:N/UI:N/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. Confirm 3ds Max installation
    Locate the 3ds Max executable. Common paths include C:\Program Files\Autodesk\3ds Max 2026\3dsmax.exe or similar version-named folders under the Autodesk program directory. If the executable exists, the product is installed.
    Affected if 3ds Max is installed on the system
  2. Determine installed version
    Right-click the 3dsmax.exe file, select Properties, then go to the Details tab. Note the 'Product version' or 'File version' field. Alternatively, run the executable with the '-version' command line flag if supported.
    Affected if The version is 2026.0.0 through 2026.3.1 (any version >= 2026 but < 2026.3.2)
  3. Verify RGB import capability
    Launch 3ds Max and attempt to access the file import functionality. Look for RGB file support in the import dialog - typically found under File > Import > Select file type. Check if .rgb files appear as an available format or can be selected.
    Affected if RGB file format is listed as an import option or .rgb files can be selected in the file open dialog

You are affected if Autodesk 3ds Max version 2026.0.0 through 2026.3.1 is installed AND RGB file import functionality is available on the system.

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

Restrict or disable RGB file processing in 3ds Max environments until the vendor patch is applied. Sanitize or whitelist file types accepted in production 3ds Max workflows.

Recommended fix High confidence

3ds Max 2026.3.2

  1. 1. Check the current version of Autodesk 3ds Max by opening the application and navigating to Help > About Autodesk 3ds Max
  2. 2. If the version is 2026.0 through 2026.3.1, navigate to the Autodesk Account or Autodesk Support website to download version 2026.3.2
  3. 3. Download the Autodesk 3ds Max 2026.3.2 installer from the official Autodesk website
  4. 4. Close any running instances of 3ds Max
  5. 5. Run the installer and follow the on-screen prompts to complete the upgrade
  6. 6. After installation, verify the version by checking Help > About Autodesk 3ds Max shows version 2026.3.2 or later

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
  • 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-0661 — 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-2026-0661 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