dbcve.org
Substance 3d SamplerApplication · Adobe

CVE-2026-48305

HIGH · 7.8 CVSS v3.1 Published 2026-06-09
Fix available
A fix is available. Upgrade to 6.0.1 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
Substance3D - Sampler versions 6.0.0 and earlier are affected by an out-of-bounds write 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 · high confidence

Substance3D Sampler versions 6.0.0 and earlier contain an out-of-bounds write vulnerability that allows arbitrary code execution in the context of the current user. The vulnerability is triggered when a victim opens a specially crafted malicious file, requiring user interaction for exploitation.

MitigationUpdate Substance3D Sampler to a version newer than 6.0.0 to address the out-of-bounds write vulnerability. Users should avoid opening untrusted files until the patch is applied.

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 SamplerApplication
Affected:< 6.0.1

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. Identify installed Adobe Substance 3D Sampler version
    On Windows, open Add or Remove Programs and locate 'Adobe Substance 3D Sampler' to view the installed version. On macOS, navigate to Applications, right-click the app, select Get Info, and check the version field. Alternatively, locate the main executable (typically named 'Adobe Substance 3D Sampler.exe' on Windows or the app bundle on macOS), right-click it, select Properties, and inspect the File version or Product version field.
    Affected if The displayed version is 6.0.0 or any version lower than 6.0.1 (for example, 5.0.x, 4.x, or earlier releases).
  2. Confirm the application is actively used or accessible
    Verify that Adobe Substance 3D Sampler is installed and can be launched by a user on the system. Check for the application shortcut in the Start menu (Windows) or Launchpad/Applications folder (macOS).
    Affected if The application is installed and executable on the system, making it possible to open a malicious file with it.
  3. Determine if the application processes untrusted input files
    Review typical usage patterns: check the application's file open dialog for supported import formats (such as .jpg, .png, .tga, .exr, or other image formats that Sampler can load and process). Look for recent project files or sample assets that indicate the app is used to import images or 3D assets.
    Affected if Users routinely open files from varied sources (downloads, external drives, email attachments) using this application, creating an attack surface for maliciously crafted files.

You are affected if Adobe Substance 3D Sampler version 6.0.0 or earlier is installed and users can open files with it, since the out-of-bounds write vulnerability triggers upon opening a specially crafted malicious file.

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 6.0.1 or later
Fixed in 6.0.1
Interim mitigation

Update Substance3D Sampler to a version newer than 6.0.0 to address the out-of-bounds write vulnerability. Users should avoid opening untrusted files until the patch is applied.

Recommended fix High confidence

Adobe Substance 3D Sampler 6.0.1 or later

  1. 1. Open Adobe Substance 3D Sampler and navigate to Help > About to verify the current installed version
  2. 2. Navigate to the official Adobe Substance 3D Sampler download page at helpx.adobe.com
  3. 3. Download version 6.0.1 or later of Adobe Substance 3D Sampler
  4. 4. Run the installer and follow the on-screen prompts to complete the upgrade
  5. 5. Restart Adobe Substance 3D Sampler after installation completes
  6. 6. Verify the version is now 6.0.1 or later via Help > About

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

Fix this in Substance 3d Sampler Scoped from the published advisory
  • Consultation1.0 h
  • Implementation2.0 h
  • Testing2.0 h
  • Review / QA1.0 h
6.0 hours of engineering $1,040
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,664.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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