CVE-2025-49573
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.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 confidenceAn out-of-bounds write vulnerability in Adobe Substance3D Modeler versions 1.22.0 and earlier allows arbitrary code execution when a user opens a maliciously crafted file. The vulnerability stems from improper bounds checking during file parsing, allowing an attacker to write data beyond allocated memory boundaries.
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.2CVSS 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.
-
Verify if Adobe Substance3D Modeler is installedCheck the application installation directory or use system package manager. Common paths: Windows: C:\Program Files\Adobe\Adobe Substance 3D Modeler\ or macOS: /Applications/Adobe Substance 3D Modeler.appAffected if The application is present on the system
-
Determine installed version numberOpen Adobe Substance3D Modeler, then go to Help > About Adobe Substance3D Modeler, or check the version in the application metadata file within the installation folderAffected if The displayed version is 1.22.0 or earlier, or the version cannot be determined but the product is installed
-
Confirm the file parsing feature is in useCheck if the user has opened or intends to open .sbsar files or 3D model files (.obj, .fbx, .sbsar) in the applicationAffected if The user opens or has opened .sbsar or model files from potentially untrusted sources
A user is affected if Adobe Substance3D Modeler version 1.22.0 or earlier is installed and the application is used to open .sbsar or model files, since the vulnerability is triggered during file parsing.
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.2
Apply the vendor patch when released by Adobe; avoid opening untrusted .sbsar or model files in Substance3D Modeler until the update is installed.
1.22.2
- Close the Substance 3D Modeler application completely
- Navigate to the official Adobe download page at helpx.adobe.com or use the Adobe Creative Cloud desktop application
- Locate Substance 3D Modeler and check the current installed version under the application settings or info
- Download version 1.22.2 or later from the official Adobe source
- Run the installer and follow the on-screen prompts to complete the installation
- Restart the application after installation completes
- Verify the installed version is 1.22.2 or later by checking the application info or version number
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation2.0 h
- Testing1.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,200.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-49573 — 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-49573 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