PatchSiren cyber security CVE debrief
CVE-2026-21341 Adobe CVE debrief
Substance3D - Stager versions 3.1.6 and earlier are 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. This vulnerability has a high CVSS score of 7.8, indicating a high severity level. The affected product, Substance3D - Stager, is vulnerable to this out-of-bounds write issue, which can lead to code execution. To verify and assess this vulnerability, defenders should review the official CVE Program record and NIST NVD detail page for source-provided CVE metadata and vulnerability assessment. Additionally, defenders should check for any vendor advisories or guidance on mitigating the vulnerability, and prioritize patching vulnerable systems and monitoring for suspicious activity.
- Vendor
- Adobe
- Product
- Substance 3D Stager
- CVSS
- HIGH 7.8
- CISA KEV
- Not listed in stored evidence
- Original CVE published
- 2026-02-10
- Original CVE updated
- 2026-08-28
- Advisory published
- 2026-02-10
- Advisory updated
- 2026-08-28
Who should care
Security teams and administrators responsible for Substance3D - Stager systems, as well as users who may be targeted by malicious files, should prioritize patching vulnerable systems and monitoring for suspicious activity. Additionally, security teams should review the official CVE Program record and NIST NVD detail page for source-provided CVE metadata and vulnerability assessment.
Technical summary
The vulnerability is an out-of-bounds write issue in Substance3D - Stager versions 3.1.6 and earlier, which could result in arbitrary code execution in the context of the current user. Exploitation requires user interaction, as a victim must open a malicious file. The affected product is Substance3D - Stager, and the vulnerability has a high CVSS score of 7.8. To defend against this vulnerability, security teams should prioritize patching vulnerable systems and monitoring for suspicious activity.
Defensive priority
High priority due to high CVSS score and potential for code execution.
Recommended defensive actions
- Apply vendor patch
- Inventory vulnerable systems
- Monitor for suspicious activity
- Restrict user access
- Implement compensating controls
- Review compensating controls for exposed systems while remediation is scheduled and verified
- Track exceptions, retest remediated assets, and close the item only after evidence is documented
Evidence notes
The CVE record and NVD entry provide details on the vulnerability, including its high CVSS score of 7.8 and the need for user interaction to exploit it. The vulnerability is an out-of-bounds write issue in Substance3D - Stager versions 3.1.6 and earlier. To verify and assess the vulnerability, defenders should review the official CVE Program record and NIST NVD detail page for source-provided CVE metadata and vulnerability assessment. Additionally, defenders should check for any vendor advisories or guidance on mitigating the vulnerability.
Sources and references
Verified primary and authoritative sources
-
CVE-2026-21341 CVE Program record
Publisher, destination, and source semantics verified
URL: https://www.cve.org/CVERecord?id=CVE-2026-21341
CVE Program - Official CVE Program record with source-provided CVE metadata.
-
CVE-2026-21341 NVD vulnerability detail
Publisher, destination, and source semantics verified
URL: https://nvd.nist.gov/vuln/detail/CVE-2026-21341
NIST National Vulnerability Database - Official NIST NVD detail page and source-specific vulnerability assessment.
Supplemental references
-
Source reference
Unverified legacy reference
URL: https://helpx.adobe.com/security/products/substance3d_stager/apsb26-20.html
[email protected] - Vendor Advisory
Methodology and review provenance
AI-assisted synthesis based on stored public vulnerability evidence. System validation, approval state, and publication status do not by themselves establish human review of this revision. PatchSiren helps prioritize defensive review and does not prove exposure or remediation on any system.