Skip to content
Noroxi
CVE-2009-3577· NVD / CVE Program· CNA mitre

Autodesk 3D Studio Max (3DSMax) 6 through 9 and 2008 through 2010 allows remote attackers to execute arbitrary code via a .max file with a M

Autodesk 3D Studio Max (3DSMax) 6 through 9 and 2008 through 2010 allows remote attackers to execute arbitrary code via a .max file with a MAXScript statement that calls the DOSCommand method, related to "application callbacks."

CriticalCVSS 9.3 · v2.0—Proof of concept No fix recorded

Noroxi analysis

No Noroxi analysis for this record yet

We don't hand-write analysis for the hundreds of thousands of vulnerabilities in the database; that wouldn't be honest. For notable, high-impact vulnerabilities our team writes the mechanism, detection and remediation steps.

We use this product, ask for help
Published
Nov 24, 2009
Updated
Jun 16, 2026
EPSS
5.1% · 92th percentile
Follow this CVE

Sign in to follow · You’ll be notified if a followed record enters KEV, gets an exploit or is updated.

Report tools

JSON

Action score

39

Monitor

Low priority for now.

CVSS
37 / 40 · 9.3 / 10
CISA KEV
0 / 30 · Not listed
EPSS
2 / 30 · 5.1%

Affected systems

VendorProduct
autodesk3ds max

Affected versions

NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.

  • autodesk 3ds max2008
  • autodesk 3ds max2009
  • autodesk 3ds max2010
  • autodesk 3ds max6
  • autodesk 3ds max7
  • autodesk 3ds max8
  • autodesk 3ds max9

Same product

autodesk: all records

Other highest-scoring records for the same primary product.

  • CVE-2026-0661Out-of-Bounds Write in RGB File Parsing
    33Monitor
  • CVE-2026-0660Stack Based Buffer Overflow in GIF File Parsing
    33Monitor
  • CVE-2026-0538GIF File Parsing Out-of-Bounds Write
    33Monitor
  • CVE-2026-0537RGB File Parsing Memory Corruption
    33Monitor
  • CVE-2026-7455FLT File Parsing Out-of-Bounds Write Vulnerability in Autodesk 3ds Max
    31Monitor
  • CVE-2026-19568SVG File Parsing Memory Corruption Vulnerability in Autodesk 3ds Max
    31Monitor

Remediation

Which version to upgrade to

Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.

No fix version is recorded for this entry. Check the references for vendor advisories.

Exploit status

Proof of concept available

A public proof of concept or detection signature exists. Exploit knowledge is out there; don't delay patching.

Evidence

  • Exploit-DB entry ×1

Noroxi does not host or link to exploit code. Metasploit module names and Nuclei template ids are shown (names, not code); Exploit-DB entries and PoC repositories are given as counts only.

Public exploit evidence
SourceKindDate
Exploit-DB entryremote2009-10-23

Research context

For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.

Timeline

From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.

  1. First PoC-33 d
  2. Published
  3. TodaySep 30, 2026+6154 d
EPSS, last 120 days

FIRST EPSS daily score; only changes of 0.01 or more are recorded (step chart).

Patch and commit links

Commit, PR and diff links among the references. A starting point for patch-diffing and variant hunting; fixes, not exploits.

No commit or PR link among the references.

Credits

All researchers

Finders, reporters and analysts named in the CNA record. Click a name for that researcher’s other records.

No credits in the CNA record.

Variant candidates

Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.

No nightly-computed relations.

Chain candidates

An authentication bypass and a privilege-requiring bug in the same product, published close together: combined they may become an unauthenticated path.

—

Bug bounty scope

The product’s vendor appears in a public program. Matched by name; verify the scope text in the program.

Technical details

Attack conditions

    If successful

    Confidentiality
    C · data can be read
    Integrity
    C · data or configuration can be modified
    Availability
    C · the service can be disrupted
    Attack complexity
    M
    Confidentiality impact
    C
    Integrity impact
    C
    Availability impact
    C

    Weakness class (CWE)

    CWE-94 · Improper Control of Generation of Code ('Code Injection')

    CVSS vector

    AV:N/AC:M/Au:N/C:C/I:C/A:C

    nvd-primary

    Attack context

    MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.

    Change log

    No changes recorded on tracked fields yet. Score, KEV, exploit maturity and fix status changes appear here.

    References

    Vendor advisories and official records. Exploit/PoC links are deliberately left out.

    All records