CVE-2026-21302
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 · uneditedSubstance3D - Modeler versions 1.22.4 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 · high confidenceAdobe Substance3D Modeler versions 1.22.4 and earlier contain an out-of-bounds read vulnerability that allows memory exposure. Successful exploitation requires a victim to open a specially crafted malicious file, leading to disclosure of sensitive information stored in process memory.
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< 1.22.5CVSS 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 checksWork through these to decide whether this CVE applies to you.
-
Check installed Adobe Substance 3D Modeler versionOpen Adobe Substance 3D Modeler and navigate to Help > About, or check the Windows Programs and Features list / macOS Applications folder for the installed versionAffected if Version displayed is 1.22.4 or earlier (any version number below 1.22.5)
-
Confirm file handling workflowObserve whether the application is configured to automatically open or preview 3D model files (.obj, .fbx, .stl, .blend, etc.)Affected if Users can directly open files by double-clicking them or drag-and-dropping into the application without additional security inspection
-
Identify untrusted file sourcesReview how users obtain 3D model files: from downloads, email attachments, external drives, or untrusted websitesAffected if Users open 3D model files from untrusted or unknown sources without prior sandboxing or antivirus scanning
The environment is affected if Adobe Substance 3D Modeler version is 1.22.4 or earlier AND users open 3D model files from untrusted sources, as exploitation requires opening a specially crafted malicious file.
Generated from the published advisory. Verify against your own configuration.
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 · scoped1.22.5
Update Substance3D Modeler to a version later than 1.22.4. Additionally, exercise caution when opening files from untrusted sources and consider deploying file sandboxing or endpoint protection to inspect potentially malicious files before execution.
Substance 3D Modeler 1.22.5 or later
- Ensure all important projects and files in Substance 3D Modeler are backed up
- Close any running instances of Substance 3D Modeler
- Update Substance 3D Modeler to version 1.22.5 or later by using the Adobe Creative Cloud desktop application or downloading from the official Adobe website
- Verify the update was successful by checking the application version
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation2.0 h
- Implementation4.0 h
- Testing2.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,560.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-21302 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2026-21302 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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