CVE-2025-54201VulnerabilityPublished 12 Aug 2025

CVE-2025-54201: Adobe Substance3D – Modeler · Out-of-bounds Read

Affects Adobe Substance3D – ModelerSource CVE Database V5

Not known to be exploited · CVSS 5.5 Medium.

Data as of 25 Oct 2026, 19:02 UTC

CVSS 3.1 base score

5.5Medium

How severe the flaw is on the 0–10 CVSS scale.

EPSS: 0.1% chance of exploitation in 30 days – higher than 9% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.

CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:H/I:N/A:N

Attack Vector: Local
Attack Complexity: Low
Privileges Required: None
User Interaction: Required
Scope: Unchanged
Confidentiality: High
Integrity: None
Availability: None

Bold values are the worst case: easiest to exploit or largest impact.

Attack Vector: Local: The vulnerable component is not bound to the network stack and the attacker’s path is via read/write/execute capabilities. Either: the attacker exploits the vulnerability by accessing the target system locally (e.g., keyboard, console), or remotely (e.g., SSH); or the attacker relies on User Interaction by another person to perform actions required to exploit the vulnerability (e.g., tricking a legitimate user into opening a malicious document).
Attack Complexity: Low: Specialized access conditions or extenuating circumstances do not exist. An attacker can expect repeatable success against the vulnerable component.
Privileges Required: None: The attacker is unauthorized prior to attack, and therefore does not require any access to settings or files to carry out an attack.
User Interaction: Required: Successful exploitation of this vulnerability requires a user to take some action before the vulnerability can be exploited.
Scope: Unchanged: An exploited vulnerability can only affect resources managed by the same security authority. In this case, the vulnerable component and the impacted component are either the same, or both are managed by the same security authority.
Confidentiality: High: There is total loss of confidentiality, resulting in all resources within the impacted component being divulged to the attacker. Alternatively, access to only some restricted information is obtained, but the disclosed information presents a direct, serious impact.
Integrity: None: There is no loss of integrity within the impacted component.
Availability: None: There is no impact to availability within the impacted component.

Definitions: FIRST CVSS v3.1 specification.

Exploitation evidence

Disclosed: evidence found.
CVE published 12 Aug 2025
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 2026-10-25.

Disclosed: The CVE record is public on cve.org. Its publication is t = 0.
Detectable: A public nuclei template can find exposed instances, for defenders and attackers alike.
Weaponised: Public exploit code exists in Metasploit or Exploit-DB, or CISA SSVC reports a public proof of concept.
Exploited in the wild: CISA KEV lists it, CISA SSVC rates exploitation active, or a source reports attacks.
Observed by OffSeq Mirage: OffSeq Mirage honeypot sensors recorded attack traffic for this CVE, or found exposed hosts without attack traffic.

Moments are spaced evenly, not to scale; a dashed line marks a gap of six months or more. Deltas count from t = 0. Sources that give only a date (CISA KEV, Exploit-DB, or a time of exactly 00:00Z) read “same day” rather than hours. Metasploit modules carry the flaw’s disclosure date, not their release date, and nuclei templates carry no date, so both appear above but not on the timeline.

What to do

Affected software

Product	Affected	Fixed in
Adobe Substance3D - Modeler	Affected =0	Fixed in–

AI-suggested

1. Implement strict file validation and sandboxing: Configure Adobe Substance3D - Modeler to open files in a restricted environment or sandbox to limit potential memory exposure. 2. Enforce strict file origin policies: Educate users to only open 3D model files from trusted sources and implement email and file transfer scanning to detect potentially malicious files. 3. Monitor and restrict usage: Limit the installation and use of Substance3D - Modeler to essential personnel and isolate workstations handling untrusted content. 4. Apply application whitelisting and endpoint detection: Use endpoint security solutions to monitor for anomalous behavior related to the application. 5. 6. Employ memory protection technologies: Utilize operating system-level protections such as Data Execution Prevention (DEP) and Address Space Layout Randomization (ASLR) to reduce exploitation risk. 7. Conduct user training: Raise awareness about the risks of opening unverified files and encourage reporting of suspicious files or behavior.

Description

Substance3D - Modeler versions 1.22.0 and earlier are affected by an out-of-bounds read vulnerability that could lead to disclosure of sensitive memory. Exploitation of this issue requires user interaction in that a victim must open a malicious file.

Impact

For European organizations, the primary impact of this vulnerability lies in the potential leakage of sensitive information through crafted files opened in Adobe Substance3D - Modeler. Organizations involved in digital content creation, media production, gaming, and design sectors that utilize this software could face confidentiality breaches if malicious files are introduced via email, file sharing, or insider threats. Although the vulnerability does not allow code execution or system compromise, the exposure of sensitive memory could lead to further targeted attacks or intellectual property theft. The requirement for user interaction reduces the risk of widespread automated exploitation but does not eliminate the threat, especially in environments where users frequently exchange 3D model files. Given the medium severity and local attack vector, the threat is more relevant to endpoint security and user awareness. European companies with creative teams using Adobe Substance3D - Modeler should be vigilant about file provenance and implement controls to prevent opening untrusted files. The absence of known exploits suggests a window of opportunity for proactive mitigation before attackers develop weaponized payloads.

CWE-125Out-of-bounds Read (opens in a new tab)
Base weaknessCWE Top 25 (2025): #8
The product reads data past the end, or before the beginning, of the intended buffer.
Implementation · Input Validation
Assume all input is malicious. Use an "accept known good" input validation strategy, i.e., use a list of acceptable inputs that strictly conform to specifications. Reject any input that does not strictly conform to specifications, or transform it into something that does.
Architecture and Design · Language Selection
Use a language that provides appropriate memory abstractions.
OWASP Cheat Sheets
XML Security (opens in a new tab)
Mass Assignment (opens in a new tab)
OWASP ASVS 4.0.3
V13.3.1 (opens in a new tab)
V5.1.4 (opens in a new tab)
V5.1.3 (opens in a new tab)
Attack patterns
Overread Buffers (opens in a new tab)
From MITRE CWE, MITRE CAPEC and OWASP (Top 10, OpenCRE).

References

helpx.adobe.com/security/products/substance3d-modeler/apsb25-76.html (opens in a new tab)

Community reviews

Loading reviews…

Exploitation evidence

What to do

Affected software

Description

AI analysisMachine-generated, updated 20 Aug 2025, 02:16 UTC

WeaknessesCWE-125

Technical details

References

Community reviews

Related threats