dbcve.org
Substance 3d DesignerApplication · Adobe

CVE-2023-26409

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 an out-of-bounds read vulnerability when parsing a crafted file, which could result in a read past the end of an allocated memory structure. An attacker could leverage this vulnerability 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.

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

Out-of-bounds read vulnerability in Adobe Substance 3D Designer versions 12.4.0 and earlier when parsing crafted files. The software fails to properly validate buffer boundaries during file parsing, allowing read operations past the end of allocated memory structures. This memory disclosure can be leveraged for arbitrary code execution in the context of the current user.

MitigationUpdate Adobe Substance 3D Designer to a version newer than 12.4.0. Avoid opening files from untrusted sources, as exploitation requires user interaction to open a malicious crafted file.

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. Check if Adobe Substance 3D Designer is installed
    Look for the application in the system. On Windows, check the installation directory (typically C:\Program Files\Adobe\Adobe Substance 3D Designer) or search for the executable. On macOS, check /Applications for Adobe Substance 3D Designer.app
    Affected if The application is present on the system
  2. Determine the installed version of Adobe Substance 3D Designer
    Open the application and navigate to Help > About Adobe Substance 3D Designer, or right-click the executable and select Properties to view version information. The version number is displayed in the format such as 12.x.x
    Affected if Version cannot be determined or is 12.4.0 or earlier
  3. Compare installed version against affected range
    Compare the version you found in the previous step. The affected range is any version less than or equal to 12.4.0. If the version starts with 12 and the minor version is 4 or lower, or if it is any version below 12.4.0, the installed version is affected
    Affected if Installed version is 12.4.0 or any earlier version (for example, 12.3.0, 12.2.1, 11.x, etc.)
  4. Verify file parsing functionality is present
    Confirm the application can open and parse project files. The vulnerability is triggered when parsing crafted files. The application must have the ability to open .sbsar, .sbs, or other supported file formats
    Affected if The application can open and parse design files and the version is 12.4.0 or earlier

If Adobe Substance 3D Designer version 12.4.0 or earlier is installed and the file parsing feature is available, the environment is affected by this vulnerability.

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. Avoid opening files from untrusted sources, as exploitation requires user interaction to open a malicious crafted file.

Recommended fix Moderate confidence

Latest version of Adobe Substance 3D Designer (version higher than 12.4.0)

  1. 1. Open Adobe Substance 3D Designer.
  2. 2. Navigate to the Help menu and select 'Check for Updates' to see if a newer version is available.
  3. 3. Alternatively, visit the official Adobe Substance 3D Designer download page at adobe.com and download the latest version.
  4. 4. Before upgrading, backup any existing projects and custom packages.
  5. 5. Install the updated version and verify the application launches successfully.
  6. 6. Re-test any critical workflows to ensure functionality is preserved.
Caveat Minor: Verify custom packages and plugins are compatible with the new version before production use

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

Fix this in Substance 3d Designer Scoped from the published advisory
  • Consultation4.0 h
  • Implementation2.0 h
  • Testing4.0 h
  • Review / QA2.0 h
12.0 hours of engineering $2,120
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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