PatchSiren

PatchSiren cyber security CVE debrief

CVE-2026-21344 Adobe CVE debrief

Substance3D - Stager versions 3.1.6 and earlier are affected by an out-of-bounds read vulnerability when parsing a crafted file. This vulnerability could result in a read past the end of an allocated memory structure, potentially allowing an attacker to execute code in the context of the current user if a victim opens a malicious file. The vulnerability is caused by an out-of-bounds read when parsing a crafted file, which could result in a read past the end of an allocated memory structure. This could potentially allow an attacker to execute code in the context of the current user. Exploitation of this issue requires user interaction in that a victim must open a malicious file. Security teams should verify the affected systems and apply patches. Further analysis and verification are recommended.

Vendor
Adobe
Product
Substance3D - 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 should prioritize patching and monitoring. Security teams should verify the affected systems and apply patches. IT teams and system administrators should review and implement compensating controls for exposed systems while remediation is scheduled and verified.

Technical summary

The vulnerability is caused by an out-of-bounds read when parsing a crafted file, which could result in a read past the end of an allocated memory structure. This could potentially allow an attacker to execute code in the context of the current user. The vulnerability affects Substance3D - Stager versions 3.1.6 and earlier. Exploitation of this issue requires user interaction in that a victim must open a malicious file.

Defensive priority

High priority due to potential code execution.

Recommended defensive actions

  • Verify and apply vendor patches
  • Inventory affected systems
  • Monitor for suspicious file parsing activity
  • Review compensating controls for exposed systems while remediation is scheduled and verified
  • Check relevant monitoring, detection, and logs for exposed assets that need extra review
  • Track exceptions, retest remediated assets, and close the item only after evidence is documented
  • Confirm whether affected product deployments exist in managed environments and assign an owner for follow-up

Evidence notes

The CVE record and NVD entry provide details on the vulnerability. Further analysis and verification are recommended. The vulnerability is caused by an out-of-bounds read when parsing a crafted file, which could result in a read past the end of an allocated memory structure. This could potentially allow an attacker to execute code in the context of the current user. Security teams should verify the affected systems and apply patches. The CVE Program and NVD provide official records and details.

Sources and references

Verified primary and authoritative sources

  • CVE-2026-21344 CVE Program record

    Publisher, destination, and source semantics verified

    URL: https://www.cve.org/CVERecord?id=CVE-2026-21344

    CVE Program - Official CVE Program record with source-provided CVE metadata.

  • CVE-2026-21344 NVD vulnerability detail

    Publisher, destination, and source semantics verified

    URL: https://nvd.nist.gov/vuln/detail/CVE-2026-21344

    NIST National Vulnerability Database - Official NIST NVD detail page and source-specific vulnerability assessment.

Supplemental references

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.