Skip to main content

Substance 3D Designer CVE-2026-48431

| EUVDEUVD-2026-65629 HIGH
Heap-based Buffer Overflow (CWE-122)
2026-08-25 adobe GHSA-p3jj-j6cq-5j4p
7.8
CVSS 3.1 · Vendor: adobe
View

Attack ChainAIDerived

Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain

  1. Access
    Craft malicious Designer project file
  2. Delivery
    Deliver file to victim via email or asset platform
  3. Exploit
    Victim opens file in Substance 3D Designer
  4. Execution
    Heap-based buffer overflow triggered during file parsing
  5. Impact
    Arbitrary code executed as current user

Vulnerability Assessment

Weakness
CWE
ASVS 5.0
V15 - Secure Coding and Architecture Heap buffer bounds checking
MITRE ATT&CK

1 technique across 1 tactic: Execution

The technique list with ATT&CK links and the kill-chain view is part of the Basic plan and up.

Exploitation Conditions

Exploitation requires the victim to actively open a specially crafted file in Adobe Substance 3D Designer - this is the sole prerequisite. No authentication, no network-exposed service, and no special system configuration are required on the target machine beyond having Substance 3D Designer installed. The CVSS vector PR:N confirms the attacker requires no privileges on the target system; the attacker's only role is crafting and delivering the malicious file. Exploitation is limited by UI:R: the victim must be socially engineered or otherwise induced to open the file. Scope is unchanged (S:U), meaning exploitation is bounded to the privileges of the current user running Designer - typically a non-root desktop user, which limits lateral escalation unless combined with a privilege escalation chain.

Impact

The CVSS 7.8 score reflects a High-severity local file-parsing vulnerability with full C/I/A impact, but with a critical limiting factor: UI:R requires the victim to actively open a malicious file. In practice, this is a standard phishing or watering-hole delivery mechanism targeting 3D artists and designers. Attack complexity is low (AC:L), meaning no race conditions or unusual circumstances are required once the file is opened. No EPSS data was provided, and no KEV listing exists, so exploitation probability cannot be quantified beyond inference. No public POC has been identified at time of analysis. The realistic threat model involves targeted attacks against game studios, VFX houses, or film production companies - where sharing Designer project files over email, Slack, or asset management systems is routine workflow. This makes social engineering delivery highly plausible despite the UI:R gate. Risk is meaningful for organizations in creative industries but lower for general enterprise environments where Designer is not deployed.

Exploit ScenarioDerived

An attacker crafts a malicious Substance 3D Designer project file (.sbs or similar) embedding a payload that triggers a heap-based buffer overflow during file parsing. The attacker delivers this file to a target - such as a game studio artist - via email, a shared asset repository, or a community file-sharing platform, using social engineering to convince the victim to open it. Upon opening the file in Substance 3D Designer, the overflow corrupts heap memory and redirects execution to attacker-controlled shellcode, running arbitrary commands as the logged-in user.

This Week Schedule remediation this week. Why: HIGH severity (CVSS 7.0-8.9).
No patch listed yet 0.2% exploitation probability (EPSS)

Get an e-mail when this CVE is exploited, patched or re-scored. Free account.

Alert me

AnalysisAIv1 – Aug 25, 2026

Heap-based buffer overflow in Adobe Substance 3D Designer enables arbitrary code execution in the context of the victim user when a malicious project or asset file is opened. The CVSS vector (AV:L/AC:L/PR:N/UI:R) confirms local file-based exploitation with no privileges required on the attacker side, but requiring the victim to actively open a crafted file. No public exploit code or CISA KEV listing has been identified at time of analysis; the vendor has issued advisory APSB26-115 addressing this issue.

RemediationAI

The primary fix is to apply the vendor patch identified in Adobe security advisory APSB26-115 (https://helpx.adobe.com/security/products/substance3d_designer/apsb26-115.html); the exact patched version number should be confirmed from that advisory. As a compensating control prior to patching, users should avoid opening Substance 3D Designer files received from untrusted or unverified sources, including those shared via email, messaging platforms, or third-party asset repositories. Organizations should instruct creative teams to verify file provenance before opening project files and consider scanning incoming Designer files with endpoint detection tools capable of identifying malformed binary content. Sandbox-based file inspection may help intercept malicious files before they reach end-user workstations. Note that restricting file opening does not remediate the vulnerability - it only reduces exposure until the patch is applied.

Affected VersionsENISA

Adobe Substance 3D Designer 0 ≤16.0.4
Adobe Substance 3D Designer patch: 16.0.5

Affected Packages

euvd adobe_substance_3d_designer no fix

Source: OSV (Open Source Vulnerabilities)

Affects your stack

Affects 1 package in euvd

Checking this CVE against your own stacks and servers is part of the Basic plan and up.

Technical ContextAI · show details

Adobe Substance 3D Designer is a node-based procedural texture and material authoring application widely used in game development, visual effects, and film production. The affected component parses complex proprietary file formats (such as .sbs or .sbsar project files) and processes binary asset data. CWE-122 (Heap-based Buffer Overflow) indicates that attacker-controlled data from a malicious file is written beyond the bounds of a heap-allocated buffer during parsing, corrupting adjacent heap metadata or object pointers. This class of vulnerability is commonly exploited via heap-spray or use-after-free chaining techniques to achieve reliable code execution. The CPE string cpe:2.3:a:adobe:adobe_substance_3d_designer:*:*:*:*:*:*:*:* covers all versions without a bounded upper limit, suggesting a wide version range is affected prior to the patched release.

Know when Adobe Substance 3D Designer gets its next vulnerability

  • Watch products and get an email when something new is published
  • Check this CVE against your own stack and servers
  • Exploit and PoC references, threat intelligence from 22 sources

No credit card · 7-day full trial

Severity by source

Vendor (adobe) PRIMARY 7.8 HIGH
AV:L/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H
vuln.today AI 7.8 HIGH

File-parsing vector is local (AV:L); no attacker privileges needed to craft the file (PR:N); victim must open it (UI:R); full impact to vulnerable process (C/I/A:H).

3.1 AV:L/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H
4.0 AV:L/AC:L/AT:N/PR:N/UI:A/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N

Primary rating from Vendor (adobe).

CVSS VectorVendor: adobe

Attack Vector
Local
Attack Complexity
Low
Privileges Required
None
User Interaction
Required
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

DescriptionCVE.org

Substance3D - Designer is affected by a Heap-based Buffer Overflow vulnerability that could result in arbitrary code execution in the context of the current user. Exploitation of this issue requires user interaction in that a victim must open a malicious file.

Executive ViewAI

Why It Matters

Adobe Substance 3D Designer contains a heap buffer overflow vulnerability (CVE-2026-48431) that enables arbitrary code execution when users open malicious design files. This directly threatens creative and engineering teams, enabling attackers to compromise workstations, exfiltrate intellectual property, and potentially pivot to internal networks-with no patch currently available.

Business Impact: High
Compensating Controls

No vendor-released patch identified at time of analysis. Interim mitigations: enforce file source controls (block external USB, restrict email attachments, use allowlist for trusted asset repositories); deploy application-level sandboxing if available; implement real-time monitoring for suspicious process spawning from Substance 3D Designer; require user confirmation before opening files with detailed origin verification; restrict network access from design workstations during file handling operations.

Threat Intelligence Overview

EPSS Score
0.2%
Top 90% exploitable
Prevalence
Low
specialized 3D authoring tool, used in games/VFX industry only
Data Quality
5 sources
Confidence: Medium

How this decision was reached

The engine reads each signal below and applies a fixed list of rules from top to bottom. The first rule that matches sets the recommended action – like a statement, every line is shown.

SignalValue
Severity HIGH
CISA KEV No
Public POC No
EPSS 0.2%
Patch available No
Active threat No
Deciding rule
HIGH severity (CVSS 7.0-8.9)
What every action level means
Emergency Immediate action required. Criteria: CRITICAL + in CISA KEV (actively exploited) without patch, OR CRITICAL + EPSS > 30% without patch, OR CRITICAL + active threat signals without patch.
Act Now Prioritize within 24-48h. Criteria: in KEV with patch available, OR CRITICAL + public POC, OR HIGH + EPSS > 10%, OR CRITICAL + active threat, OR any CRITICAL severity.
This Week Schedule remediation this week. Criteria: HIGH severity (CVSS 7.0-8.9). Patch within normal change window.
This Month Plan within 30 days. Criteria: MEDIUM severity (CVSS 4.0-6.9), lower exploitation probability. Include in regular patch cycle.
Monitor Track and reassess. Criteria: LOW severity (CVSS 0.1-3.9), minimal exploitation risk. No immediate action needed.

SSVC AssessmentENISA

SSVC Decision
Scheduled
Exploitation
None
System Exposure· derived
Small
Automatable
No
Human Impact
High
Technical Impact
Total

Priority Score

39
Low Medium High Critical
KEV: 0
EPSS: 0
CVSS: +39
PoC: 0
Weaponized: 0
Threat intel: 0
Gov advisory: 0

Attack Technique

A buffer overflow occurs when a program writes more data to a memory buffer than it was allocated to hold, causing the excess data to spill into adjacent memory regions.

A heap overflow occurs when a program writes data beyond the bounds of a buffer allocated in the heap memory region.

Remote Code Execution represents the critical moment when an attacker successfully runs arbitrary code on a target system without physical access.

This site uses cookies essential for authentication and security. No tracking or analytics cookies are used. Privacy Policy