FLT File Parsing Out-of-Bounds Write Vulnerability in Autodesk 3ds Max
Noroxi assessment
Priority: Monitor (action score 31/100)
- The sources we track (CISA KEV, Exploit-DB, Metasploit, Nuclei, GitHub) show no public exploit code or exploitation in the wild.
- Probability of exploitation in the next 30 days: 0.19% (FIRST EPSS).
- Someone with local access to the system can trigger it. No account or password is required. A user must open a link or visit a page. No special conditions are required; it is repeatable.
- Fixed version: Autodesk 3ds Max 2026.3.4, 2027.2.0.
Low priority for now. Upgrade to Autodesk 3ds Max 2026.3.4, 2027.2.0 or later.
Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it
Primary sources: NVD · CVE.org · FIRST EPSS
A maliciously crafted FLT 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.
- Published
- Aug 24, 2026
- Updated
- Oct 12, 2026
- EPSS
- 0.1% · 8th percentile
- CWE
- CWE-787
Report tools
Action score
31
Monitor
Low priority for now.
- CVSS
- 31 / 40 · 7.8 / 10
- CISA KEV
- 0 / 30 · Not listed
- EPSS
- 0 / 30 · 0.1%
CISA SSVC decision
- Exploitation
- none
- Automatable
- no
- Technical impact
- total
Vulnrichment: CISA's decision-tree inputs.
CNA vs NVD score
- NVD
- —
- CNA · autodesk
- 7.8
- NVD has not scored this yet; the score shown is the CNA’s.
The score given by the assigning authority versus NVD’s independent score. A gap means the severity is contested.
Get told when this record changes
- Not in KEV: no record of exploitation in the wild
- No public exploit code on record
- A fix has been released
If any of these changes, we'll tell you in the daily email digest.
Running WordPress? Scan your site free with WP Lens
Noroxi analysis
What does it mean in your environment?
The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.
We use this product, ask for helpAffected systems
Is your version affected?
Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.
| Vendor | Product | CPE |
|---|---|---|
| autodesk | 3ds max | cpe:2.3:a:autodesk:3ds_max |
Affected versions
NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.
- autodesk 3ds max2026 and later · before 2026.3.4
- autodesk 3ds max2027 and later · before 2027.2
Versions reported by the vendor
Affected version ranges reported by the assigning authority (autodesk). Independent of NVD's CPE analysis and usually ahead of it.
Autodesk 3ds Max
- 2027.0.0 and later · before 2027.2.0affected · semver
- 2026.0.0 and later · before 2026.3.4affected · semver
Same product
autodesk: all recordsOther highest-scoring records for the same primary product.
- CVE-2009-3577Autodesk 3D Studio Max (3DSMax) 6 through 9 and 2008 through 2010 allows remote attackers to execute arbitrary code via a .max file with a M39Monitor
- CVE-2026-0661Out-of-Bounds Write in RGB File Parsing33Monitor
- CVE-2026-0660Stack Based Buffer Overflow in GIF File Parsing33Monitor
Published before and after this one in the same product
- ← EarlierCVE-2026-16782Aug 24, 2026 · SVG File Parsing Out-of-Bounds Read Vulnerability in Autodesk 3ds Max31Monitor
- ← EarlierCVE-2026-16783Aug 24, 2026 · ABC File Parsing Out-of-Bounds Write Vulnerability in Autodesk 3ds Max31Monitor
- ← EarlierCVE-2026-19568Aug 24, 2026 · SVG File Parsing Memory Corruption Vulnerability in Autodesk 3ds Max31Monitor
Remediation
Which version to upgrade to
Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.
| Product / package | Fixed version | Source |
|---|---|---|
| Autodesk 3ds Max | 2026.3.4 | Vendor (CNA) |
| Autodesk 3ds Max | 2027.2.0 | Vendor (CNA) |
Exploit status
No known public exploit
No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.
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.
No dated events beyond publication.
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 researchersFinders, 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.
- CVE-2026-0537201 days apartRGB File Parsing Memory Corruption33Monitor
- CVE-2026-0538201 days apartGIF File Parsing Out-of-Bounds Write33Monitor
- CVE-2026-0661201 days apartOut-of-Bounds Write in RGB File Parsing33Monitor
- CVE-2026-167830 days apartABC File Parsing Out-of-Bounds Write Vulnerability in Autodesk 3ds Max31Monitor
- CVE-2026-745190 days apartTIF File Parsing Out-of-Bounds Write in Autodesk 3ds Max31Monitor
- CVE-2026-0536201 days apartGIF File Parsing Stack Based Buffer Overflow31Monitor
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
- Someone with local access to the system can trigger it.
- No account or password is required.
- A user must open a link or visit a page.
- No special conditions are required; it is repeatable.
If successful
- Confidentiality
- high · data can be read
- Integrity
- high · data or configuration can be modified
- Availability
- high · the service can be disrupted
- Attack vector
- Local
- Attack complexity
- Low
- Privileges required
- None
- User interaction
- Required
- Scope
- Unchanged
- Confidentiality impact
- High
- Integrity impact
- High
- Availability impact
- High
Weakness class (CWE)
CWE-787 · Out-of-bounds WriteCVSS vector
CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H
nvd-secondary
Attack context
MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.
MITRE has no CAPEC/ATT&CK mapping for this CWE.
Change log
- Fix✗ → ✓
For records you follow, these changes also arrive as notifications. →
References
Show all references (1 more)Show less
Vendor advisories and official records. Exploit/PoC links are deliberately left out.