CVE-2025-47135: Adobe Dimension · Out-of-bounds Read
Affects Adobe DimensionSource CVE Database V5
Not known to be exploited · CVSS 5.5 Medium.
Data as of 26 Oct 2026, 12:29 UTC
- EPSS
- 0.2% chance of exploitation in 30 days – higher than 10% 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:NExploitation evidence
Disclosed: evidence found.
CVE published 8 Jul 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 26 Oct 2026.
What to do
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| Adobe Dimension | Affected
| Fixed in– |
AI-suggested
European organizations should implement the following specific mitigations: 1) Immediately restrict the use of Adobe Dimension versions 4.1.2 and earlier until a vendor patch is available. 2) Educate users on the risks of opening files from untrusted sources, emphasizing the need for caution with files received via email or external media. 3) Employ advanced email filtering and endpoint protection solutions capable of detecting and blocking malicious files targeting Adobe Dimension. 4) Monitor network and endpoint logs for unusual activity related to Adobe Dimension processes, especially file open events. 5) Use application whitelisting to limit execution of unauthorized or suspicious files within Adobe Dimension. 6) Where possible, isolate Adobe Dimension usage to segmented network zones to limit lateral movement in case of compromise. 7) Stay updated with Adobe security advisories and apply patches promptly once released. 8) Consider deploying memory protection technologies and exploit mitigation tools that can detect or prevent out-of-bounds memory reads.
Description
Dimension versions 4.1.2 and earlier are affected by an out-of-bounds read vulnerability that could lead to disclosure of sensitive memory. An attacker could leverage this vulnerability to bypass mitigations such as ASLR. Exploitation of this issue requires user interaction in that a victim must open a malicious file.