Memory Corruption RCE via Malicious TGA in Autodesk 3ds Max
CVE-2025-6634 Published on August 6, 2025

TGA File Parsing Memory Corruption Vulnerability
A maliciously crafted TGA file, when linked or imported into Autodesk 3ds Max, can force a Memory Corruption vulnerability. A malicious actor can leverage this vulnerability to execute arbitrary code in the context of the current process.

Vendor Advisory NVD

Vulnerability Analysis

CVE-2025-6634 is exploitable with local system access, requires user interaction. This vulnerability is considered to have a low attack complexity. The potential impact of an exploit of this vulnerability is considered to be very high.

Attack Vector:
LOCAL
Attack Complexity:
LOW
Privileges Required:
NONE
User Interaction:
REQUIRED
Scope:
UNCHANGED
Confidentiality Impact:
HIGH
Integrity Impact:
HIGH
Availability Impact:
HIGH

Weakness Type

What is a Classic Buffer Overflow Vulnerability?

The program copies an input buffer to an output buffer without verifying that the size of the input buffer is less than the size of the output buffer, leading to a buffer overflow. A buffer overflow condition exists when a program attempts to put more data in a buffer than it can hold, or when a program attempts to put data in a memory area outside of the boundaries of a buffer. The simplest type of error, and the most common cause of buffer overflows, is the "classic" case in which the program copies the buffer without restricting how much is copied. Other variants exist, but the existence of a classic overflow strongly suggests that the programmer is not considering even the most basic of security protections.

CVE-2025-6634 has been classified to as a Classic Buffer Overflow vulnerability or weakness.


Products Associated with CVE-2025-6634

You can be notified by email with stack.watch whenever vulnerabilities like CVE-2025-6634 are published in AutoDesk 3ds Max:

 

Affected Versions

Autodesk 3ds Max:

Exploit Probability

EPSS
0.03%
Percentile
6.94%

EPSS (Exploit Prediction Scoring System) scores estimate the probability that a vulnerability will be exploited in the wild within the next 30 days. The percentile shows you how this score compares to all other vulnerabilities.