Attack ChainAIDerived
Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain
-
AccessDeliver crafted project file + malicious DLL pair to victim
-
DeliveryVictim opens project file in Substance 3D Painter
-
ExploitApplication initiates library load using untrusted search path
-
ExecutionMalicious DLL resolved before legitimate library
-
ImpactArbitrary code executes as current user
Vulnerability Assessment
| Weakness |
CWE
OWASP Top 10:2025
A08:2025 - Software or Data Integrity Failures
ASVS 5.0
V13 - Configuration Search path verification
|
| Exploitation Conditions | Exploitation requires two concrete prerequisites: first, the victim must actively open a specially crafted Substance 3D Painter project file (UI:R per CVSS vector); second, the attacker must have pre-positioned a malicious DLL or executable - named to match a library Painter loads - in a directory that Painter searches during dependency resolution, such as the project file's containing directory or the application working directory. No authentication or system-level privileges are required of the attacker (PR:N per CVSS vector). Exploitation is bounded by the victim's account privilege level (S:U, no escalation beyond the current user context). The vulnerability does not affect installations where users exclusively open project files from fully trusted, write-controlled directories, and it cannot be triggered remotely without the file-open interaction step. |
| Impact | The CVSS 7.8 base score reflects a high-impact but locally-triggered attack: AV:L bounds the attack to situations where the attacker can place files in a path Substance 3D Painter searches, while UI:R requires a victim to actively open a crafted project file. PR:N is notable - it confirms that the attacker does not need any pre-existing privileges on the victim system, only the ability to deliver a file pair. The unchanged scope (S:U) limits the blast radius to the victim's own user account, yet C:H/I:H/A:H confirms full host-level impact within that account's privilege boundary. No EPSS score was included in available data, so exploitation probability cannot be quantified numerically; no CISA KEV listing exists, meaning active exploitation is unconfirmed. The attack technique for CWE-426 is well-documented, low-skill, and does not require specialized tooling, which means the effective exploitation bar is lower than the CVSS complexity metrics alone might suggest - any creative or digital-production environment whose users regularly exchange Substance 3D Painter project files with external collaborators should treat this as an urgent workstation patch. |
| Exploit ScenarioDerived | An attacker distributes a crafted Substance 3D Painter project file paired with a malicious DLL named to match a library the application loads at startup - delivered via email, a shared asset repository, or a compromised collaboration platform. When a victim artist opens the project file from the directory containing the malicious DLL, Painter's library loader resolves the library name to the attacker's substitute rather than the legitimate system copy, executing arbitrary code silently under the victim's account. No public POC has been identified at time of analysis, but the DLL side-loading technique underlying CWE-426 requires no specialized tooling and is well-documented in open security research. |
Get an e-mail when this CVE is exploited, patched or re-scored. Free account.
Alert meAnalysisAIv1 – Aug 25, 2026
Untrusted Search Path exploitation in Adobe Substance 3D Painter allows an attacker to achieve arbitrary code execution under the current user's account by planting a malicious DLL or executable alongside a crafted project file. The root cause (CWE-426) is the application's failure to validate the library search path when loading dependencies at runtime, enabling full compromise of confidentiality, integrity, and availability on the victim host. No public exploit code or CISA KEV listing has been identified at time of analysis; however, the low attack complexity, well-understood exploitation technique, and complete C/H/I/A/A impact triad make this a meaningful patching priority for teams whose users open externally sourced project files.
RemediationAI
Apply the vendor-released fix detailed in Adobe Security Bulletin APSB26-129 at https://helpx.adobe.com/security/products/substance3d_painter/apsb26-129.html. An exact fixed version number was not present in the available intelligence data; consult the advisory directly to confirm the minimum safe release before deploying updates. As a compensating control prior to patching, users should avoid opening Substance 3D Painter project files received from untrusted external sources such as email attachments, file-sharing platforms, or unverified collaborative repositories. Launching Substance 3D Painter only from dedicated installation directories that do not contain externally supplied files reduces DLL search-order exposure. Where technically feasible, restrict write access to directories from which Painter is commonly launched, preventing an attacker from staging a malicious library alongside a legitimate project file. Note that restricting file-open behavior may impact legitimate workflows in collaborative environments - coordinate mitigations with affected teams.
Affected VersionsENISA
Affected Packages
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 Painter is a professional 3D texturing and painting application widely used in game development and visual-effects production. CWE-426 (Untrusted Search Path) describes a class of vulnerability in which an application constructs or accepts a search path that includes directories under attacker influence - commonly the current working directory derived from a user-supplied file path, or a PATH element writable by an unprivileged user. When the application loads shared libraries or executables, the OS loader follows this path and may resolve a legitimate library name to an attacker-supplied substitute. The CPE cpe:2.3:a:adobe:adobe_substance_3d_painter:*:*:*:*:*:*:*:* uses wildcards across all version fields, indicating NVD has not bounded affected versions to a specific range. The CVSS vector AV:L/AC:L/PR:N/UI:R is consistent with a file-opening trigger: the attack surface is local (the file system), complexity is low because no race condition or special timing is required, no attacker privileges are needed to stage the malicious file, and user interaction is required because the victim must open the crafted project.
Know when Adobe Substance 3D Painter 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
AV:L/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H
Local attack vector reflects file-system staging requirement; no attacker privileges needed; mandatory user file-open interaction; full C/I/A impact within unchanged user scope.
Primary rating from Vendor (adobe).
CVSS VectorVendor: adobe
DescriptionCVE.org
Substance3D - Painter is affected by an Untrusted Search Path vulnerability that could result in arbitrary code execution in the context of the current user. An attacker could exploit this vulnerability to execute arbitrary code. Exploitation of this issue requires user interaction in that a victim must open a malicious file.
Executive ViewAI
Adobe Substance 3D Painter versions lack library path validation, allowing attackers to execute arbitrary code by distributing project files with malicious DLLs. Teams relying on this design tool face potential data theft, IP compromise, and system takeover when users open externally-sourced files, particularly impacting creative departments exchanging designs with external vendors or collaborators.
No vendor-released patch identified at time of analysis. Interim mitigations: (1) Restrict project file sources to internal repositories and trusted partners only; (2) Implement mandatory security training emphasizing risks of opening externally-sourced project files; (3) Deploy application whitelisting to prevent unsigned DLL execution within Substance 3D Painter; (4) Use endpoint detection and response (EDR) to monitor for unusual DLL loading in design tool processes; (5) Consider running Substance 3D Painter within a containerized or VM environment when processing external files.
Threat Intelligence Overview
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.
What every action level means
SSVC AssessmentENISA
Priority Score
Attack Technique
Remote Code Execution represents the critical moment when an attacker successfully runs arbitrary code on a target system without physical access.
More in Adobe Substance 3D Painter
View allHeap-based buffer overflow in Adobe Substance 3D Painter enables arbitrary code execution under the logged-in user's con
Heap-based buffer overflow in Adobe Substance 3D Painter enables arbitrary code execution within the context of the curr
Heap-based buffer overflow in Adobe Substance 3D Painter enables arbitrary code execution in the context of the current
Heap-based buffer overflow in Adobe Substance 3D Painter enables arbitrary code execution at the privilege level of the
Out-of-bounds write in Adobe Substance 3D Painter enables arbitrary code execution under the privileges of the current u
Out-of-bounds write in Adobe Substance 3D Painter enables arbitrary code execution within the current user's security co
Out-of-bounds read in Adobe Substance 3D Painter exposes sensitive process memory when a victim opens a specially crafte
EUVD-2026-65687
GHSA-chrc-jvf9-2396
NVD
CVE.org
EPSS
Vulnrichment
VulDB
Exploit-DB