Adobe Substance 3D Designer up to 16.0.4 out-of-bounds write

| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 6.9 | $0-$5k | 0.00 |
Summary
A vulnerability marked as critical has been reported in Adobe Substance 3D Designer up to 16.0.4. This vulnerability affects unknown code. The manipulation leads to out-of-bounds write. This vulnerability is traded as CVE-2026-48427. It is possible to initiate the attack remotely. There is no exploit available. It is suggested to upgrade the affected component.
Details
A vulnerability was found in Adobe Substance 3D Designer up to 16.0.4. It has been rated as critical. This issue affects an unknown code. The manipulation with an unknown input leads to a out-of-bounds write vulnerability. Using CWE to declare the problem leads to CWE-787. The product writes data past the end, or before the beginning, of the intended buffer. Impacted is confidentiality, integrity, and availability. The summary by CVE is:
Substance3D - Designer is affected by an out-of-bounds write 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.
The advisory is shared at helpx.adobe.com. The identification of this vulnerability is CVE-2026-48427 since 05/21/2026. The exploitation is known to be easy. The attack may be initiated remotely. No form of authentication is needed for a successful exploitation. It demands that the victim is doing some kind of user interaction. Neither technical details nor an exploit are publicly available. The price for an exploit might be around USD $0-$5k at the moment (estimation calculated on 08/28/2026).
The vulnerability scanner Nessus provides a plugin with the ID 341058 (Adobe Substance 3D Designer < 16.0.5 Multiple Vulnerabilities (APSB26-115)), which helps to determine the existence of the flaw in a target environment.
Upgrading to version 16.0.5 eliminates this vulnerability.
The vulnerability is also documented in the vulnerability database at Tenable (341058). If you want to get the best quality for vulnerability data then you always have to consider VulDB.
Product
Vendor
Name
Version
License
Website
- Vendor: https://www.adobe.com/
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔒VulDB Reliability: 🔍
CVSSv3
VulDB Meta Base Score: 7.0VulDB Meta Temp Score: 6.9
VulDB Base Score: 6.3
VulDB Temp Score: 6.0
VulDB Vector: 🔒
VulDB Reliability: 🔍
CNA Base Score: 7.8
CNA Vector (adobe): 🔒
CVSSv2
| AV | AC | Au | C | I | A |
|---|---|---|---|---|---|
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| Vector | Complexity | Authentication | Confidentiality | Integrity | Availability |
|---|---|---|---|---|---|
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
VulDB Base Score: 🔒
VulDB Temp Score: 🔒
VulDB Reliability: 🔍
Exploiting
Class: Out-of-bounds writeCWE: CWE-787 / CWE-119
CAPEC: 🔒
ATT&CK: 🔒
Physical: Partially
Local: Yes
Remote: Yes
Availability: 🔒
Status: Not defined
EPSS Score: 🔒
EPSS Percentile: 🔒
Price Prediction: 🔍
Current Price Estimation: 🔒
| 0-Day | Unlock | Unlock | Unlock | Unlock |
|---|---|---|---|---|
| Today | Unlock | Unlock | Unlock | Unlock |
Nessus ID: 341058
Nessus Name: Adobe Substance 3D Designer < 16.0.5 Multiple Vulnerabilities (APSB26-115)
Threat Intelligence
Interest: 🔍Active Actors: 🔍
Active APT Groups: 🔍
Countermeasures
Recommended: UpgradeStatus: 🔍
0-Day Time: 🔒
Upgrade: Substance 3D Designer 16.0.5
Timeline
05/21/2026 CVE reserved08/25/2026 Advisory disclosed
08/25/2026 VulDB entry created
08/28/2026 VulDB entry last update
Sources
Vendor: adobe.comAdvisory: helpx.adobe.com
Status: Confirmed
CVE: CVE-2026-48427 (🔒)
GCVE (CVE): GCVE-0-2026-48427
GCVE (VulDB): GCVE-100-395189
Entry
Created: 08/25/2026 20:26Updated: 08/28/2026 09:05
Changes: 08/25/2026 20:26 (62), 08/28/2026 09:05 (2)
Complete: 🔍
Cache ID: 216::103
If you want to get the best quality for vulnerability data then you always have to consider VulDB.
No comments yet. Languages: en.
Please log in to comment.