dbcve.org
Substance 3d ModelerApplication · Adobe

CVE-2026-21348

MEDIUM · 5.5 CVSS v3.1 Published 2026-02-10
Fix available
A fix is available. Upgrade to 1.22.6 or later.
See remediation →
58/100
Remediation priority · Elevated
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
Substance3D - Modeler versions 1.22.5 and earlier are affected by an out-of-bounds read vulnerability that could lead to memory exposure. An attacker could leverage this vulnerability to disclose sensitive information stored in memory. 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

Out-of-bounds read vulnerability in Substance3D Modeler versions 1.22.5 and earlier allows attackers to disclose sensitive information from application memory by tricking users into opening specially crafted malicious files.

MitigationAvoid opening files from untrusted sources in Substance3D Modeler. Monitor Adobe security advisories for patched versions and update promptly when available.

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 ModelerApplication
Affected:< 1.22.6

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
None
Availability
None

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

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 Modeler is installed
    Check Windows Programs and Features, Mac Applications folder, or search for 'Substance 3D Modeler' in the system. On Windows, also check the registry at HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall for entries containing 'Substance 3D Modeler'.
    Affected if The application is found installed on the system.
  2. Determine the installed version number
    On Windows, right-click the executable (typically in C:\Program Files\Adobe\Adobe Substance 3D Modeler or C:\Program Files\Adobe\Substance 3D Modeler) and select Properties > Details to view the File Version. On macOS, right-click Adobe Substance 3D Modeler.app > Get Info to see the version.
    Affected if A version number is returned from the application binaries.
  3. Compare installed version to the affected range
    Compare the version found in step 2 against the affected range: any version 1.22.5 or earlier is vulnerable. Versions 1.22.6 and later are patched.
    Affected if The installed version is 1.22.5 or earlier, or any version lower than 1.22.6.
  4. Assess user interaction patterns
    Determine whether the application is used to open files from external or untrusted sources. Check recent file open operations or user workflows that involve importing 3D models from unknown sources.
    Affected if Users routinely open files from untrusted or unknown sources in the application.

The system is affected if Adobe Substance 3D Modeler version 1.22.5 or earlier is installed and users may open files 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 1.22.6 or later
Fixed in 1.22.6
Interim mitigation

Avoid opening files from untrusted sources in Substance3D Modeler. Monitor Adobe security advisories for patched versions and update promptly when available.

Recommended fix High confidence

1.22.6

  1. Check the current version of Substance 3D Modeler by opening the application and navigating to Help > About
  2. Download Substance 3D Modeler version 1.22.6 or later from the official Adobe website at helpx.adobe.com
  3. Run the installer and follow the on-screen prompts to complete the installation
  4. After installation, verify the version by checking Help > About to confirm version 1.22.6 or later is installed

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

Fix this in Substance 3d Modeler Scoped from the published advisory
  • Consultation2.0 h
  • Testing2.0 h
  • Review / QA1.0 h
5.0 hours of engineering $880
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,408.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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