Autodesk 3ds Max out-of-bounds read in SBSAR file parsing
- Exploited
- No known exploitation
- Fix
- Fixed in 2027.3.0
- Who is exposed
- Not reported
Summary
A flaw in how Autodesk 3ds Max handles SBSAR files lets a malicious file cause an out-of-bounds read when it is imported or loaded through the Substance in 3ds Max plugin. An attacker would need a local setup and a user to open the crafted file, and the result is most likely an application crash, with possible exposure of sensitive data from the running process.
Written by a model
Original description
A maliciously crafted SBSAR file, when imported or loaded through the Substance in 3ds Max plugin in Autodesk 3ds Max, can trigger an Out-of-Bounds Read (unvalidated element begin-pointer) vulnerability. A malicious actor may leverage this vulnerability to cause an application crash or potentially read sensitive data from the current process.
What to do
Upgrade to a fixed version: 2027.3.0.
Check your systems with an agent
Paste this into a coding or ops agent. It checks your systems read-only and reports a table per asset.
Check whether my systems are affected by CVE-2026-126824 (SBSAR File Parsing Out-of-Bounds Read in Autodesk 3ds Max), using the cve.now data below.
Rules: work read-only. Do not run exploit code, proof-of-concept scripts or scanners that send attack payloads, and do not change any configuration, package, image or deployment. Report findings only.
What cve.now has for CVE-2026-126824 (entry last updated 2026-11-19):
Affected:
- Autodesk 3ds Max: from 2027.0.0, fixed in 2027.3.0
Fixed versions: 2027.3.0.
Setup: unknown whether the bug needs a non-default feature or setting. Check the advisory.
CISA KEV: CVE-2026-126824 is not listed as of cve.now's last read.
This KEV status is for CVE-2026-126824 only. If you also check another CVE, look up its own KEV status; never assume it from this one.
How to check:
- Installed software: check what is actually running, not what a repo declares. Read the version from each host, container image and Kubernetes node (the binary's version output, the OS package database, image layers), and check whether the conditions above hold there. Distribution packages may carry a backported fix under an older version number; confirm against the distribution's own advisory.
Verify against the linked advisories before concluding, and cite the date you read each one:
- https://www.autodesk.com/trust/security-advisories/adsk-sa-2026-0022
- https://www.autodesk.com/products/autodesk-access/overview
Do not conclude an asset is unaffected unless you checked it and the evidence covers both its version and the conditions above. If you could not check something, mark it unknown and say what is missing.
Report a table with one row per asset and these columns: Asset | Version or build | Status (affected, fixed, not applicable, unknown) | Compensating controls | Exposure (internet-facing, internal, none) | Evidence | Next action.
Entry: https://cve.now/CVE-2026-126824
For follow-up questions, use the cve.now MCP server at https://mcp.cve.now/mcp (no authentication), for example execute with name cve.get and arguments {"id": "CVE-2026-126824"}.Affected versions
- Autodesk 3ds MaxFrom 2027.0.0 · fixed in 2027.3.0
cve.now Index
- Exploitation0/40No signal
- Exposure?/25Unknown. No advisory context yet
- Reach?/20Unknown. No tracked technology or package matched
- Severity5.5/10CVSS 5.5
- No patch0/5No signal
What would change the score
- Would score about 61 if added to CISA KEV
- Would score about 56 if CISA's SSVC rates exploitation active
- Would score about 28 if advisories confirm default setups are exposed
Timeline
- CVE published
- First seen by cve.now
- CISA SSVC assessment
Exploitation: none · Automatable: no · Technical impact: partial
- Record last updated
Evidence 4
| Kind | Source |
|---|---|
| Vendor advisory 2Establishes: Affected and fixed versions. | |
| Advisory | autodesk.com · trust/security-advisories/adsk-sa-2026-0022 |
| Patch | autodesk.com · products/autodesk-access/overview |
| CVE record 2Establishes: The identifier and description. | |
| Record | CVE List · CVE-2026-126824 |
| Record | NVD · CVE-2026-126824 |
Questions about CVE-2026-126824
Is CVE-2026-126824 being exploited?
It is not in CISA's Known Exploited Vulnerabilities catalog, and CISA's SSVC assessment does not mark exploitation as active. That does not mean it has not been attacked: vendors and researchers can report attacks before CISA lists them. No public exploit code is tracked.
Source: cve.now feed data
Which versions are affected by CVE-2026-126824?
3ds Max: from 2027.0.0 before 2027.3.0.
Source: cve.now feed data
How do I fix CVE-2026-126824?
Upgrade to a fixed version: 2027.3.0.
Source: cve.now feed data
Related
- CVE-2026-0660Stack Based Buffer Overflow in GIF File Parsing
- CVE-2026-0661Out-of-Bounds Write in RGB File Parsing
- CVE-2026-0537RGB File Parsing Memory Corruption
- CVE-2026-0538GIF File Parsing Out-of-Bounds Write
- CVE-2026-126826SBSAR File Parsing Out-of-Bounds Write in Autodesk 3ds Max
- CVE-2026-19568SVG File Parsing Memory Corruption Vulnerability in Autodesk 3ds Max
No corrections so far. Something wrong on this page? Report an error.