dbcve.org
3ds MaxApplication · Autodesk

CVE-2025-11795

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 JPG 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

A specially crafted JPG file parsed by Autodesk 3ds Max triggers an out-of-bounds memory write, allowing an attacker to execute arbitrary code within the application's context. The vulnerability requires user interaction (opening the malicious file) but achieves code execution without requiring elevated privileges.

MitigationApply vendor-supplied patches for Autodesk 3ds Max when available; avoid opening untrusted or unsolicited JPG files in 3ds Max until the patch is deployed.

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. Identify installed 3ds Max version
    Open 3ds Max, go to Help > About Autodesk 3ds Max, or check the executable properties (right-click 3dsmax.exe > Properties > Details) to view the product version
    Affected if Version is 2026.0, 2026.1, 2026.2, or any version >= 2026 but < 2026.3
  2. Confirm 3ds Max installation path
    Locate 3dsmax.exe on the system. Typical paths: C:\Program Files\Autodesk\3ds Max 2026\3dsmax.exe or C:\Program Files\Autodesk\3ds Max 2026.1\3dsmax.exe
    Affected if Executable exists and version matches the affected range
  3. Check for recent JPG file processing activity
    Review recent files opened in 3ds Max or check the application recent files list (File > Recent). Examine any logs if file access logging is enabled
    Affected if Users have opened untrusted or unsolicited JPG files in 3ds Max
  4. Identify 3ds Max image import modules
    Check for presence of image handling DLLs in the 3ds Max program directory, particularly those related to JPG/JPEG parsing (e.g., any file with 'jpeg', 'jpg', or 'image' in the name within the bin or plug-ins folders)
    Affected if Image import modules exist and the application version is within the affected range

A user is affected if Autodesk 3ds Max version 2026.x (where x is 0, 1, or 2) is installed and users open JPG files in the application.

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 vendor-supplied patches for Autodesk 3ds Max when available; avoid opening untrusted or unsolicited JPG files in 3ds Max until the patch is deployed.

Recommended fix Moderate confidence

3ds Max 2026.3

  1. Open 3ds Max and go to Help > About Autodesk 3ds Max to verify the current installed version (should be 2026, 2026.1, or 2026.2)
  2. Close any running instances of 3ds Max
  3. Navigate to the Autodesk Account or Autodesk Support website at www.autodesk.com
  4. Locate and download 3ds Max version 2026.3 (or the latest available version that is >= 2026.3)
  5. Run the installer as an administrator and follow the on-screen prompts to complete the upgrade
  6. After installation, verify the new version by opening 3ds Max and checking Help > About (should show 2026.3 or later)
  7. As a security best practice, avoid opening untrusted or unknown JPG files in 3ds Max until the update is applied
Caveat Standard upgrade - recommend backing up existing projects and preferences before updating

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
  • Testing2.0 h
  • Review / QA1.0 h
6.0 hours of engineering $1,060
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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