CVE-2025-49571
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 Uncontrolled Search Path Element vulnerability that could result in arbitrary code execution in the context of the current user. If the application uses an uncontrolled search path to locate critical resources such as programs, an attacker could modify that search path to point to a malicious program, which the targeted application would then execute. Exploitation of this issue does not require user interaction.
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 confidenceSubstance3D Modeler versions 1.22.0 and earlier use an uncontrolled search path to locate and execute critical resources/programs. An attacker with local access can manipulate the search path to point to a malicious executable that the application will then load and execute, achieving arbitrary code execution in the current user's context without requiring any user interaction.
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.
-
Locate the Substance 3D Modeler installationSearch for the executable 'Adobe Substance 3D Modeler.exe' in common installation directories such as C:\Program Files\Adobe\Adobe Substance 3D Modeler, or use 'where /r C:\ Adobe Substance 3D Modeler.exe' on Windows or 'find /Applications -name "Adobe Substance 3D Modeler*"' on macOSAffected if The executable is not found or located in a non-standard directory
-
Identify the installed version numberRight-click the executable, select Properties, then view the Details tab to see the Product Version. Alternatively, run the application and check Help > About, or inspect the version from the installer if availableAffected if The version displayed is blank, unknown, or cannot be determined
-
Compare version against the affected rangeIf the version is determined, compare it to 1.22.2. Versions prior to 1.22.2 (including 1.22.0 and earlier) are affected by this vulnerabilityAffected if The installed version is lower than 1.22.2 (for example, 1.22.0, 1.21.x, 1.20.x, or any earlier release)
-
Verify the application has not been patchedCheck if version 1.22.2 or later is installed, as version 1.22.2 is the first fixed release. If the installed version shows 1.22.2 or higher, the vulnerability has been addressedAffected if The installed version remains at 1.22.0 or below and no update has been applied
A user is affected if Adobe Substance 3D Modeler is installed with a version lower than 1.22.2, as this version range contains the uncontrolled search path vulnerability.
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
Upgrade to a version newer than 1.22.0 when a patch is available. In the interim, ensure the application directory and any directories in its search path are not writable by unprivileged users.
1.22.2 or later
- Close Substance 3D Modeler if it is currently running
- Navigate to Adobe's official support page at helpx.adobe.com
- Locate the download page for Substance 3D Modeler
- Download version 1.22.2 or later of Substance 3D Modeler
- Run the installer and complete the update process
- Restart the application if it does not start automatically after installation
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation2.0 h
- Implementation4.0 h
- Testing3.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,088.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-49571 — 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-49571 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