LiveActive security incident?Get immediate response
CVE Record

CVE-2026-0661: Out-of-Bounds Write in RGB File Parsing

A maliciously crafted RGB file, when parsed through 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.

HighCVSS 8.4Not KEV-listedUpdated
Glexia's TakeAutomated analysishigh

Security readout for executives and security teams

Plain-English summary

Autodesk 3ds Max 2026 can mishandle a malicious RGB file and corrupt memory. The published impact is arbitrary code execution in the current 3ds Max process. This matters where artists, engineers, or render pipelines import external RGB files. No provided source says exploitation is active.

Executive priority

Treat this as a high-priority workstation and creative-pipeline risk, not a broad internet-facing emergency. Patch affected 3ds Max 2026 installations and reduce exposure to untrusted RGB assets.

Technical view

CVE-2026-0661 is a CWE-787 out-of-bounds write in RGB file parsing in Autodesk 3ds Max 2026. The CVSS 3.1 score is 8.4 with high confidentiality, integrity, and availability impact. The source bundle identifies Autodesk 3ds Max 2026 as affected and other default status as unaffected.

Likely exposure

Exposure is likely limited to environments running Autodesk 3ds Max 2026 that parse RGB files, especially files from clients, vendors, asset libraries, or untrusted sources.

Exploitation context

The source bundle describes malicious RGB file parsing leading to memory corruption and arbitrary code execution in the current process. KEV status is false, and the supplied sources do not establish active exploitation or public exploit availability.

Researcher notes

The bundle does not provide fixed build numbers, proof-of-concept details, or telemetry. Analysis should stay anchored to the vendor advisory and CVE data. Validate affected scope before assuming other Autodesk versions are vulnerable.

Mitigation direction

  • Apply Autodesk guidance for ADSK-SA-2026-0002 using Autodesk Access where applicable.
  • Prioritize updating systems running Autodesk 3ds Max 2026.
  • Restrict opening RGB files from untrusted sources until remediation is confirmed.
  • Review asset ingestion workflows that automatically parse external RGB files.

Validation and detection

  • Inventory endpoints and render systems for Autodesk 3ds Max 2026.
  • Confirm installed build status against Autodesk advisory ADSK-SA-2026-0002.
  • Identify users or workflows that import RGB files into 3ds Max.
  • Check whether untrusted RGB files are blocked or routed through review.
Prepared
Confidence
high
Sources
4

Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.

Potential ATT&CK relevance

Conservative CVE-to-ATT&CK context

These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.

ATT&CK lookup starting points

Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.

cwe · low confidence lookup

CWE-787: Exact CWE lookup

Use the exact CWE identifier as the starting point before reviewing related ATT&CK behavior. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.

Open ATT&CK lookup
description · low confidence lookup

Execution behavior lookup

The CVE wording references code or command execution, so execution technique review may help defensive triage. This is a Glexia inferred lookup path, not an official MITRE, ATT&CK, or CVE Program mapping.

Open ATT&CK lookup
cve · low confidence lookup

CVE-2026-0661 mapping review

Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.

Open ATT&CK lookup
Vulnerability profileCVE Program record
Severity
High
CVSS
8.4 (3.1)
Known Exploited
No
Published

Vector: CVSS:3.1/AV:L/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H

Official CVE source material

CNA and ADP enrichment extracted from CVE v5

These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.

1CVSS vectors
3Timeline events
1ADP providers
3Source links

SSVC decision data

CISA-ADPCISA Coordinator
Timestamp
Version
2.0.3
Exploitation: noneAutomatable: noTechnical Impact: total

CVSS vector scores

1 official score

We collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.

ScoreVersionSeverityVectorExploitImpactSource
8.4CVSS 3.1HighCVSS:3.1/AV:L/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H2.55.9autodesk

Vulnerability scoring details

Base CVSS 3.1 score

8.4High
CVSS 3.1 vector shape for CVE-2026-0661Attack VectorAttack ComplexityPrivileges RequiredUser InteractionScopeConfidentiality ImpactIntegrity ImpactAvailability Impact

Vector: CVSS:3.1/AV:L/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H

Attack Vector
NetworkAdjacentLocalPhysical
Attack Complexity
LowHigh
Privileges Required
NoneLowHigh
User Interaction
NoneRequired
Scope
ChangedUnchanged
Confidentiality Impact
HighLowNone
Integrity Impact
HighLowNone
Availability Impact
HighLowNone

Vulnerability timeline

Timeline events are normalized from CVE metadata, CNA source timelines, ADP timelines, and KEV metadata when present.

  1. CVE reservedCVE Program

    The CVE ID was reserved by the assigning CNA.

  2. CVE publishedCVE Program

    The CVE record was published.

  3. CVE updatedCVE Program

    The CVE record metadata indicates this as the latest update time.

ADP provider summaries

CISA-ADPCISA ADP Vulnrichment
other:ssvc

Source materials

Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
Autodesk3ds Max2026unaffected
Weakness

CWE details

CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.

CWE-787 · source CWE mapping

Out-of-bounds Write

Out-of-bounds Write represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.