dbcve.org
Substance 3d DesignerApplication · Adobe

CVE-2023-26412

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 Stack-based Buffer Overflow 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 · moderate confidence

Adobe Substance 3D Designer versions 12.4.0 and earlier contain a stack-based buffer overflow vulnerability that can be triggered when a user opens a specially crafted malicious file. Successful exploitation allows arbitrary code execution in the context of the current user.

MitigationUpdate Adobe Substance 3D Designer to the latest patched version as soon as available from Adobe. Until then, avoid opening .sbj or other design files from untrusted or unknown sources.

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 is installed
    Check for the application in the system: On Windows, look in Program Files or the Adobe Creative Cloud folder. On macOS, check /Applications for 'Substance 3D Designer.app'. Alternatively, search for the executable or use system inventory tools.
    Affected if The application is present on the system
  2. Determine the installed version number
    Open the application and navigate to Help > About Adobe Substance 3D Designer, or check the version in the application metadata. On Windows, you can also check the executable properties (right-click the .exe file > Details > Product Version). On macOS, right-click the .app > Get Info > Version.
    Affected if The version displayed is 12.4.0 or any version lower than 12.4.0
  3. Confirm the exact version string for accurate matching
    Record the full version string exactly as shown (for example, 12.4.0, 12.3.5, 12.0.0, etc.). Compare this against the affected range: any version <= 12.4.0 is vulnerable.
    Affected if The version string is 12.4.0 or earlier (12.4.0, 12.3.x, 12.2.x, 12.1.x, 12.0.x, or any earlier major version)
  4. Identify if .sbj or design files from external sources are processed
    Review workflow patterns: check if the user or team opens .sbj files, .sbsar files, or other design assets received via email, downloads, or from external collaborators. Inspect recent file access history or default file associations.
    Affected if The application is used to open design files from untrusted or unknown sources, as this is the exploitation vector

The system is affected if Adobe Substance 3D Designer is installed with version 12.4.0 or earlier and is used to open design files, particularly from untrusted sources.

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 the latest patched version as soon as available from Adobe. Until then, avoid opening .sbj or other design files from untrusted or unknown sources.

Recommended fix Moderate confidence

Latest version of Adobe Substance 3D Designer (newer than 12.4.0) from official Adobe sources

  1. Navigate to the Adobe Substance 3D Designer download page or open Adobe Creative Cloud desktop application
  2. Locate Adobe Substance 3D Designer in your installed applications
  3. Check for and install any available updates, or download the latest version directly from Adobe
  4. Ensure you are running a version newer than 12.4.0 after installation
Caveat Review Adobe release notes for any feature changes between your current version and the update

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
  • Implementation2.0 h
  • Testing1.0 h
  • Review / QA1.0 h
6.0 hours of engineering $1,090
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,744.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2023-26412 — 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-26412 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