CVE-2025-6633
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 · uneditedA maliciously crafted RBG file, when parsed through Autodesk 3ds Max, can force an Out-of-Bounds Write vulnerability. A malicious actor may leverage this vulnerability to cause a crash, cause data corruption, 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 confidenceA vulnerability in Autodesk 3ds Max's RBG file parser allows a maliciously crafted RBG file to trigger an out-of-bounds memory write. This memory corruption can lead to process crash, data corruption, or arbitrary code execution within the context of the running 3ds Max process.
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>= 2026, < 2026.2CVSS 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 checksWork through these to decide whether this CVE applies to you.
-
Check if Autodesk 3ds Max is installedLook for 3ds Max in the installed programs list (Windows: Control Panel > Programs and Features, or check C:\Program Files\Autodesk\ for 3ds Max folders)Affected if 3ds Max is present on the system
-
Identify the installed 3ds Max versionOpen 3ds Max, go to Help > About Autodesk 3ds Max, or check the version in the program's file properties (right-click 3dsmax.exe > Properties > Details). Alternatively, check the registry key: HKLM\SOFTWARE\Autodesk\3dsMax\<version>Affected if The exact version number is displayed (e.g., 2026, 2026.1, etc.)
-
Compare version against vulnerable rangeDetermine if the installed version is >= 2026 AND < 2026.2. For example, versions 2026.0, 2026.1 are vulnerable; versions 2025.x and 2026.2+ are not.Affected if The version falls within >= 2026 and < 2026.2, meaning the RBG file parser vulnerability is present
-
Assess RBG file usage exposureCheck if users or automated processes import or open RBG files (scene, render, or asset files that may contain embedded RBG data). Search for .rbg files on local drives or in project directories using: dir /s /b *.rbgAffected if RBG files are routinely opened, imported, or processed in the 3ds Max environment
If 3ds Max version 2026.0 or 2026.1 is installed and the software handles RBG files, the environment is vulnerable to this out-of-bounds write flaw and should avoid opening untrusted RBG files until the vendor patch is applied.
Generated from the published advisory. Verify against your own configuration.
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 · scoped2026.2
Apply the vendor patch from Autodesk when available. Until then, avoid opening untrusted RBG files in 3ds Max and consider sandboxing or file type restrictions for untrusted 3D asset files.
3ds Max 2026.2
- Upgrade Autodesk 3ds Max from any version >= 2026 and < 2026.2 to version 2026.2 or later
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation1.0 h
- Implementation1.0 h
- Testing2.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,376.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-6633 — 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 sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2025-6633 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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