CVE-2025-61799: Adobe Dimension · Out-of-bounds Read
Affects Adobe DimensionSource CVE Database V5
Not known to be exploited · CVSS 7.8 High.
Data as of 25 Oct 2026, 19:02 UTC
- EPSS
- 0.2% chance of exploitation in 30 days – higher than 12% 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:H/A:HExploitation evidence
Disclosed: evidence found.
CVE published 14 Oct 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.
What to do
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| Adobe Dimension | Affected
| Fixed in– |
AI-suggested
Until an official patch is released, organizations should implement strict controls on file sources, only opening files from trusted origins. User awareness training should emphasize the risks of opening unsolicited or suspicious files. Employ application whitelisting and sandboxing techniques to isolate Adobe Dimension processes and limit the impact of potential exploits. Monitor network and endpoint logs for unusual file access or execution patterns related to Adobe Dimension. Consider disabling or restricting the use of Adobe Dimension in high-risk environments. Once Adobe releases a patch, prioritize immediate deployment. Additionally, maintain up-to-date endpoint protection solutions capable of detecting exploit attempts targeting this vulnerability.
Description
Dimension versions 4.1.4 and earlier are affected by an out-of-bounds read vulnerability when parsing a crafted file, which could result in a read past the end of an allocated memory structure. An attacker could leverage this vulnerability to execute code in the context of the current user. Exploitation of this issue requires user interaction in that a victim must open a malicious file.