CVE-2025-61839: Adobe Format Plugins · Out-of-bounds Read
Affects Adobe Format PluginsSource CVE Database V5
Not known to be exploited · CVSS 7.8 High.
Data as of 26 Oct 2026, 14:05 UTC
- EPSS
- 0.2% chance of exploitation in 30 days – higher than 18% 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 11 Nov 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 Format Plugins | Affected
| Fixed in– |
AI-suggested
Organizations should immediately implement strict email and web filtering to block suspicious or unexpected file types associated with Adobe Format Plugins. User awareness training should emphasize the risks of opening unsolicited or unexpected files, especially from unknown sources. Deploy application whitelisting and sandboxing technologies to isolate Adobe applications and limit the impact of potential exploitation. Monitor endpoint behavior for anomalies indicative of exploitation attempts, such as unusual memory access patterns or process injections. Until official patches are released, consider disabling or restricting the use of Adobe Format Plugins where feasible. Maintain up-to-date backups and incident response plans to quickly recover from potential compromises. Engage with Adobe’s security advisories to apply patches promptly once available.
Description
Format Plugins versions 1.1.1 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.