dbcve.org
Substance 3d DesignerApplication · Adobe

CVE-2023-26414

HIGH · 7.8 CVSS v3.1 Published 2023-04-13
Fix available
A fix is available. Upgrade to after 12.4.0 or later.
See remediation →
81/100
Remediation priority · High
No privileges

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
Adobe Substance 3D Designer version 12.4.0 (and earlier) is affected by a Use After Free 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.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

Adobe Substance 3D Designer versions 12.4.0 and earlier contain a Use After Free (UAF) vulnerability in file parsing logic. When a user opens a specially crafted malicious file, the application improperly handles memory allocation/deallocation, allowing an attacker to free memory while a pointer still references it, potentially enabling arbitrary code execution in the user's context.

MitigationUpdate Adobe Substance 3D Designer to a version newer than 12.4.0 once the vendor releases a patch. Avoid opening untrusted or unexpected files from unknown sources until the patch is applied.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
Substance 3d DesignerApplication
Affected:<= 12.4.0

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Local
Complexity
Low
Privileges
None
User interaction
Required
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Verify Adobe Substance 3D Designer installation
    Check for the presence of the application in Program Files (typically under Adobe\Adobe Substance 3D Designer) or via Windows PowerShell command: Get-ChildItem 'C:\Program Files\Adobe' -Recurse -Filter '*Substance*Designer*' | Select-Object FullName
    Affected if The application is installed on the system
  2. Determine installed version number
    Right-click the executable (Adobe Substance 3D Designer.exe) in the installation folder, select Properties, then view the Details tab for Product Version. Alternatively, run: (Get-Item 'C:\Program Files\Adobe\Adobe Substance 3D Designer\Adobe Substance 3D Designer.exe').VersionInfo.ProductVersion
    Affected if A version number is returned from the executable
  3. Compare version to affected range
    Compare the installed version against the affected range: versions 12.4.0 and earlier are vulnerable. Check if the version string is 12.4.0, 12.3.x, 12.2.x, 12.1.x, 12.0.x, or any earlier major version
    Affected if Installed version is 12.4.0 or any earlier version (e.g., 12.3.1, 12.0, 11.x)
  4. Identify trigger condition
    The vulnerability is triggered when the application parses a specially crafted malicious file. This occurs when opening .sbs, .sbsar, or other Substance file formats from untrusted sources using the affected version
    Affected if User opens untrusted or specially crafted Substance design files with a vulnerable version installed

A user is affected if Adobe Substance 3D Designer version 12.4.0 or earlier is installed AND the user opens specially crafted malicious files.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Upgrade available Upgrade to a release after 12.4.0
Interim mitigation

Update Adobe Substance 3D Designer to a version newer than 12.4.0 once the vendor releases a patch. Avoid opening untrusted or unexpected files from unknown sources until the patch is applied.

Recommended fix Moderate confidence

Latest available version of Adobe Substance 3D Designer (after 12.4.0)

  1. Navigate to the Adobe Substance 3D Designer download page or open Adobe Creative Cloud desktop application
  2. Check for available updates to Substance 3D Designer
  3. Download and install the latest version of Adobe Substance 3D Designer available from Adobe
  4. Verify the installed version is newer than 12.4.0
Caveat Review Adobe release notes for any feature changes between your current version and the new version

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Substance 3d Designer Scoped from the published advisory
  • Consultation2.0 h
  • Implementation1.0 h
  • Testing2.0 h
  • Review / QA1.0 h
6.0 hours of engineering $1,060
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,696.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2023-26414 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2023-26414 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data