Code execution via malicious RBG file parsing
Published Aug 6, 2025 · Updated Feb 26, 2026
Out-of-bounds write in Autodesk 3ds Max 2026 allows attackers to execute code in the current process by opening a crafted RBG file. The RBG parser writes outside an allocated memory buffer while processing attacker-controlled file data; Autodesk has not disclosed the affected routine or malformed field. Exploitation requires a user to open the file, and successful corruption can crash 3ds Max, damage process data, or run code with the user’s privileges.
Summary
What happened
Out-of-bounds write in Autodesk 3ds Max 2026 allows attackers to execute code in the current process by opening a crafted RBG file. The RBG parser writes outside an allocated memory buffer while processing attacker-controlled file data; Autodesk has not disclosed the affected routine or malformed field. Exploitation requires a user to open the file, and successful corruption can crash 3ds Max, damage process data, or run code with the user’s privileges.
The record
- CVE
- CVE-2025-6633
- Published
- Aug 6, 2025
- Updated
- Feb 26, 2026
- Vendor
- Autodesk
- Product
- 3ds Max
- Classifications
- CWE-787, T1204.002, T1203
- Attack vector
- local
- Privileges
- unauthenticated
Timeline
How it unfolded
- Aug 6, 2025CVE publishedPublication date reported by the CVE source.
- Feb 26, 2026Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=2026 <2026.2
What conditions does exploitation require?
What is affected?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo