3ds MaxApplication · Autodesk

CVE-2026-0538

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 GIF file, when parsed through Autodesk 3ds Max, can force an Out-of-Bounds Write 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 · moderate confidence

Autodesk 3ds Max contains a parsing vulnerability when processing GIF image files. A specially crafted GIF file can trigger an out-of-bounds memory write, allowing an attacker to achieve arbitrary code execution within the application's process context.

MitigationUsers should avoid opening untrusted or unexpected GIF files in Autodesk 3ds Max until an official vendor patch is available. Monitor Autodesk's security advisories for updates.

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. Identify installed 3ds Max version
    Open 3ds Max, go to Help > About Autodesk 3ds Max, or check Programs and Features for the installed version number
    Affected if The version shown is 2026.x where x is less than 3.2 (e.g., 2026, 2026.1, 2026.2, 2026.3.0, 2026.3.1)
  2. Confirm 3ds Max installation
    Check for the presence of 3ds Max in the system: look in C:\Program Files\Autodesk\ for a 3ds Max folder, or run 'Get-ItemProperty HKLM:\Software\Microsoft\Windows\CurrentVersion\Uninstall\* | Where-Object {$_.DisplayName -like "*3ds Max*"}' in PowerShell
    Affected if 3ds Max 2026 is found installed on the system
  3. Check exact build number
    Within 3ds Max, go to Help > About Autodesk 3ds Max and note the full version/build string (for example, 2026.3.1.12345), or check the uninstall registry key for the exact version value
    Affected if The build/version is 2026.0 through 2026.3.1 (any version below 2026.3.2)

You are affected if Autodesk 3ds Max version 2026.x (where x < 3.2) is installed on your 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

Users should avoid opening untrusted or unexpected GIF files in Autodesk 3ds Max until an official vendor patch is available. Monitor Autodesk's security advisories for updates.

Recommended fix High confidence

Autodesk 3ds Max 2026.3.2

  1. 1. Verify current Autodesk 3ds Max version by opening the application and navigating to Help > About Autodesk 3ds Max
  2. 2. Confirm the version is >= 2026 and < 2026.3.2, which is affected by this vulnerability
  3. 3. Download Autodesk 3ds Max version 2026.3.2 or later from the official Autodesk website (www.autodesk.com) or your Autodesk Account
  4. 4. Close any running instances of 3ds Max
  5. 5. Run the installer for version 2026.3.2 and follow the on-screen prompts to complete the installation
  6. 6. After installation, verify the new version by checking Help > About Autodesk 3ds Max to confirm version 2026.3.2 is installed

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
  • Implementation2.0 h
  • Testing4.0 h
  • Review / QA2.0 h
12.0 hours of engineering $2,120
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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