CVE-2026-16782: SVG File Parsing Out-of-Bounds Read 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.36% (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.
- Severity is disputed: the assigning authority (CNA) scores it 5.3, NVD 7.8.
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 SVG file, when parsed through Autodesk 3ds Max, can force an Out-of-Bounds Read vulnerability. A malicious actor can leverage this vulnerability to cause a crash, read sensitive data, or execute arbitrary code in the context of the current process.
- Published
- Aug 24, 2026
- Updated
- Oct 12, 2026
- EPSS
- 0.3% · 31th percentile
- CWE
- CWE-125
Report tools
Action score
31
Low priority for now.
- CVSS
- 31 / 40 · 7.8 / 10
- CISA KEV
- 0 / 30 · Not listed
- EPSS
- 0 / 30 · 0.3%
CISA SSVC decision
- Exploitation
- none
- Automatable
- no
- Technical impact
- partial
Vulnrichment: CISA's decision-tree inputs.
CNA vs NVD score
- NVD
- 7.8
- CNA · autodesk
- 5.3
- 2.5 point gap
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N
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.
Is your version affected? Check itNoroxi 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 |
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
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
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…39Monitor
- 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-7454May 26, 2026 · WRL File Parsing Memory Corruption in Autodesk 3ds Max31Monitor
- ← EarlierCVE-2026-16781Aug 24, 2026 · SVG File Parsing Stack Exhaustion Vulnerability in Autodesk 3ds Max22Monitor
- Later →CVE-2026-16783Aug 24, 2026 · ABC File Parsing Out-of-Bounds Write 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).
Variant candidates
Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.
- CVE-2025-6632383 days apartPSD File Parsing Out-of-Bounds Read Vulnerability31Monitor
Bug bounty scope
The product’s vendor appears in a public program. Matched by name; verify the scope text in the program.
Not on record for this CVE: patch commit or PR link · researcher credit.
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-125 · Out-of-bounds ReadCVSS vector
CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H
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.
Attack patterns (CAPEC)
ATT&CK techniques
—
Change log (1)
- 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.