CVE-2025-43582
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 - Viewer versions 0.22 and earlier are affected by a Heap-based Buffer Overflow vulnerability that could result in arbitrary code execution in the context of the current user, scope unchanged. 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 confidenceA heap-based buffer overflow vulnerability exists in Substance3D Viewer versions 0.22 and earlier. When processing a maliciously crafted file, the software fails to properly validate input sizes before copying data into a heap-allocated buffer, leading to memory corruption and potential arbitrary code execution in the current user context.
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< 0.25CVSS 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 checksWork through these to decide whether this CVE applies to you.
-
Locate Adobe Substance 3D Viewer installationCheck common installation directories such as C:\Program Files\Adobe\Adobe Substance 3D Viewer, or search for 'Substance 3D Viewer' in the list of installed programs via Windows Settings > Apps & features or macOS Applications folderAffected if The application is found installed on the system
-
Determine installed version numberRight-click the executable (Substance3DViewer.exe or Substance3DViewer.app), select Properties, and view the Details tab for the Version field, or launch the application and check Help > AboutAffected if Version information cannot be determined or shows a version less than 0.25
-
Compare version against affected rangeCompare your detected version to the affected range: any version below 0.25 (including 0.22 and earlier) is vulnerableAffected if Installed version is less than 0.25
-
Assess file handling behaviorReview whether the system user opens or previews .substance, .sbsar, or 3D files from untrusted or unknown sources, as the vulnerability triggers upon processing a maliciously crafted fileAffected if Users routinely open files from untrusted sources without verification
You are affected if Adobe Substance 3D Viewer version 0.25 or earlier is installed AND users process files from untrusted sources.
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 · scoped0.25
Upgrade Substance3D Viewer to a version newer than 0.22. Until then, avoid opening files from untrusted sources.
Substance 3D Viewer version 0.25 or later
- Open Adobe's official Substance 3D Viewer download page at helpx.adobe.com
- Download the latest version of Substance 3D Viewer (version 0.25 or later)
- Run the installer and follow the on-screen prompts to complete the installation
- Restart Substance 3D Viewer if it was already open
- Verify the installed version by checking Help > About in the application menu
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation2.0 h
- Implementation2.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 $1,984.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-43582 — 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-2025-43582 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