dbcve.org
3ds MaxApplication · Autodesk

CVE-2025-6632

HIGH · 7.8 CVSS v3.1 Published 2025-08-06
Fix available
A fix is available. Upgrade to 2026.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 PSD file, when linked or imported into Autodesk 3ds Max, can force an Out-of-Bounds Read 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 · high confidence

Autodesk 3ds Max contains an out-of-bounds read vulnerability when parsing PSD (Photoshop Document) files. When a user links or imports a maliciously crafted PSD file, the software reads memory beyond allocated buffer boundaries. This can expose sensitive process memory, cause a crash, or potentially enable arbitrary code execution in the current process context.

MitigationAvoid opening or importing PSD files from untrusted or unknown sources in 3ds Max until a vendor patch is available. Apply the latest Autodesk security updates when released.

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.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. Verify 3ds Max is installed
    Open 3ds Max and go to Help > About Autodesk 3ds Max, or check Program Files/Autodesk/3ds Max <version> for installation directories
    Affected if 3ds Max 2026.x is installed (versions 2026.0 through 2026.1 are affected)
  2. Confirm installed version number
    In 3ds Max, go to Help > About Autodesk 3ds Max and note the exact version string (e.g., 2026.0, 2026.1)
    Affected if Version starts with 2026 but is earlier than 2026.2 (for example, 2026.0 or 2026.1)
  3. Identify PSD file usage
    Search for .psd files in recent 3ds Max project folders, or check the Asset Tracking menu to see if PSD textures are linked or imported
    Affected if PSD files have been imported or linked into 3ds Max scenes using the Texture/PSD Link features
  4. Review security event logs
    Check Windows Event Viewer for application crashes or access violations related to 3ds Max when opening PSD files
    Affected if Crashes or errors occurred when importing or linking PSD files in 3ds Max 2026.x

You are affected if you have Autodesk 3ds Max version 2026.0 or 2026.1 installed and have imported or linked PSD files from untrusted sources.

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

Avoid opening or importing PSD files from untrusted or unknown sources in 3ds Max until a vendor patch is available. Apply the latest Autodesk security updates when released.

Recommended fix High confidence

3ds Max 2026.2

  1. Back up all current 3ds Max projects and custom configurations before upgrading
  2. Download Autodesk 3ds Max version 2026.2 or later from the official Autodesk website (www.autodesk.com)
  3. Run the installer as an administrator and follow the on-screen prompts to upgrade
  4. After installation, launch 3ds Max and verify the version by checking Help > About Autodesk 3ds Max - it should show 2026.2 or higher
  5. Test that PSD file import functionality works normally with the updated version
Caveat Standard upgrade caveats apply - review Autodesk's release notes for any feature changes or migration considerations

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-6632 — 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-6632 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