VulnerabilityPublished 10 Jun 2025

CVE-2025-47104: Adobe InDesign Desktop · Out-of-bounds Read

Affects Adobe InDesign DesktopSource CVE Database V5

Not known to be exploited · CVSS 5.5 Medium.

Data as of 26 Oct 2026, 12:29 UTC

CVSS 3.1 base score

5.5Medium

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

EPSS: 0.2% chance of exploitation in 30 days – higher than 19% 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 10 Jun 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.

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 or the CVSS exploit maturity 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 InDesign Desktop	Affected =0	Fixed in–

AI-suggested

Specific mitigation steps include: 1) Educate users, especially designers and content creators, about the risks of opening unsolicited or unexpected InDesign files, emphasizing caution with email attachments and downloads. 2) Implement strict email filtering and sandboxing to detect and block malicious InDesign files before reaching end users. 3) Use endpoint protection solutions capable of detecting anomalous behavior related to Adobe InDesign processes. 4) Monitor network and host logs for unusual activity following file openings, such as memory access anomalies or process crashes. 5) Once Adobe releases patches, prioritize rapid deployment across all affected InDesign Desktop versions to eliminate the vulnerability. 6) Employ application whitelisting to restrict execution of unauthorized files and scripts within the design environment. 7) Consider isolating InDesign workstations from sensitive network segments to limit potential lateral movement if exploitation occurs. These measures go beyond generic advice by focusing on user behavior, detection, and environment segmentation tailored to the nature of this vulnerability.

Description

InDesign Desktop versions ID20.2, ID19.5.3 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.

Impact

For European organizations, the impact of CVE-2025-47104 centers on potential sensitive data disclosure from Adobe InDesign Desktop processes. Organizations in sectors such as media, publishing, advertising, and design—where InDesign is widely used—may face risks of intellectual property leakage or exposure of confidential project data. The ability to bypass ASLR increases the risk of subsequent targeted attacks, potentially leading to more severe compromises if combined with other vulnerabilities. Since exploitation requires user interaction, the threat is primarily from targeted phishing or social engineering campaigns delivering malicious InDesign files. The medium severity score suggests moderate risk; however, the confidentiality impact is high, which is critical for organizations handling sensitive or regulated data under GDPR. Disclosed memory could include cryptographic keys, credentials, or proprietary information. The lack of known exploits reduces immediate risk but does not eliminate it, especially as attackers may develop exploits rapidly after vulnerability disclosure. European organizations should be aware of this threat to prevent data breaches and maintain compliance with data protection regulations.

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/indesign/apsb25-53.html (opens in a new tab)

Community reviews

Loading reviews…

Exploitation evidence

What to do

Affected software

Description

AI analysisMachine-generated, updated 10 Jul 2025, 21:47 UTC

WeaknessesCWE-125

Technical details

References

Community reviews

Related threats