Skip to main content
CVE Vulnerability Database
Vulnerability Database/CVE-2025-27175

CVE-2025-27175: Adobe InDesign RCE Vulnerability

CVE-2025-27175 is an out-of-bounds write RCE vulnerability in Adobe InDesign that enables arbitrary code execution. Attackers exploit it via malicious files. This article covers technical details, affected versions, and mitigations.

Published:

CVE-2025-27175 Overview

CVE-2025-27175 is an out-of-bounds write vulnerability [CWE-787] affecting Adobe InDesign Desktop versions ID20.1, ID19.5.2, and earlier. The flaw allows arbitrary code execution in the context of the current user when a victim opens a malicious file. The vulnerability impacts InDesign installations on both Microsoft Windows and Apple macOS platforms. Exploitation requires user interaction, limiting mass exploitation but enabling targeted phishing and social engineering campaigns against designers and publishing professionals.

Critical Impact

Successful exploitation grants attackers arbitrary code execution with the privileges of the user running InDesign, enabling malware installation, credential theft, and lateral movement.

Affected Products

  • Adobe InDesign Desktop ID20.1 and earlier
  • Adobe InDesign Desktop ID19.5.2 and earlier
  • Microsoft Windows and Apple macOS host platforms

Discovery Timeline

  • 2025-03-11 - CVE-2025-27175 published to the National Vulnerability Database
  • 2025-03-11 - Adobe published security advisory APSB25-19 with patched versions
  • 2025-04-28 - Last updated in NVD database

Technical Details for CVE-2025-27175

Vulnerability Analysis

The vulnerability is an out-of-bounds write condition within Adobe InDesign's file parsing logic. When InDesign processes a crafted document, the application writes data past the boundary of an allocated buffer. This memory corruption can be leveraged to overwrite adjacent control structures, function pointers, or return addresses on the stack or heap.

Out-of-bounds writes in document parsers are commonly exploited through carefully constructed object layouts that influence control flow once the corrupted memory is dereferenced. Because InDesign runs without elevated privileges by default, the resulting code execution occurs in the current user's security context. That context is typically sufficient for credential harvesting, persistence, and access to project files containing intellectual property.

Root Cause

The root cause is improper validation of bounds during a write operation while parsing a malicious InDesign file format structure. The application fails to verify that the destination buffer can accommodate the size or offset derived from attacker-controlled fields. This category of defect, classified under [CWE-787], is a recurring issue in complex binary file format parsers that handle nested objects and variable-length records.

Attack Vector

The attack vector is local and requires user interaction. An attacker delivers a weaponized .indd or related InDesign file through phishing email, file-sharing services, compromised websites, or supply-chain channels targeting creative agencies. The victim must open the file in a vulnerable version of InDesign to trigger the parsing path containing the out-of-bounds write. No network exposure or authentication bypass is involved, but the social engineering component is straightforward against design and marketing teams that routinely exchange InDesign documents.

No public proof-of-concept exploit code or in-the-wild exploitation has been reported for this CVE. See the Adobe InDesign Security Advisory APSB25-19 for vendor-provided technical context.

Detection Methods for CVE-2025-27175

Indicators of Compromise

  • InDesign process (InDesign.exe on Windows, Adobe InDesign on macOS) spawning unexpected child processes such as cmd.exe, powershell.exe, bash, or scripting interpreters
  • Unusual outbound network connections originating from the InDesign process after opening a document from an untrusted source
  • InDesign documents (.indd, .idml) arriving via email or download from unverified senders, especially with unusual file sizes or embedded resources
  • Creation of executables, scheduled tasks, or LaunchAgents shortly after an InDesign document is opened

Detection Strategies

  • Monitor parent-child process relationships where Adobe InDesign launches non-Adobe binaries, which is anomalous for normal design workflows
  • Hunt for crash events or Windows Error Reporting entries referencing the InDesign process, which may indicate failed exploitation attempts
  • Inspect email gateways and file shares for InDesign attachments originating from external senders and quarantine for sandbox analysis

Monitoring Recommendations

  • Enable endpoint behavioral telemetry on workstations running InDesign and forward events to a centralized SIEM or data lake for correlation
  • Track installed InDesign versions across the fleet and alert when hosts run versions at or below ID20.1 or ID19.5.2
  • Apply file integrity monitoring to user profile directories for unexpected binary creation following InDesign session activity

How to Mitigate CVE-2025-27175

Immediate Actions Required

  • Update Adobe InDesign to the fixed versions identified in Adobe Security Bulletin APSB25-19 across all Windows and macOS endpoints
  • Inventory all systems running Adobe InDesign and prioritize patching for users who frequently receive external documents
  • Instruct users not to open InDesign files received from untrusted or unverified sources until patching is complete

Patch Information

Adobe released fixed versions of InDesign Desktop addressing this out-of-bounds write through security bulletin APSB25-19. Administrators should deploy the updated InDesign builds via Adobe Creative Cloud or enterprise deployment tooling. Reference the Adobe InDesign Security Advisory APSB25-19 for exact patched version numbers and download instructions.

Workarounds

  • Restrict InDesign file handling to users with a documented business need and remove the application from systems where it is not required
  • Open suspect InDesign documents only inside isolated virtual machines or sandboxed environments disconnected from production resources
  • Enforce application allowlisting to block child processes spawned by Adobe InDesign, reducing post-exploitation impact
bash
# Verify installed Adobe InDesign version on macOS
defaults read "/Applications/Adobe InDesign 2024/Adobe InDesign 2024.app/Contents/Info.plist" CFBundleShortVersionString

# Verify installed Adobe InDesign version on Windows (PowerShell)
Get-ItemProperty "HKLM:\SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall\*" |
  Where-Object { $_.DisplayName -like "*InDesign*" } |
  Select-Object DisplayName, DisplayVersion

Disclaimer: This content was generated using AI. While we strive for accuracy, please verify critical information with official sources.

Default Legacy - Prefooter | Experience the World’s Most Advanced Cybersecurity Platform

Experience the Most Advanced Cybersecurity Platform

See how the world’s most intelligent, autonomous cybersecurity platform can protect your organization today and into the future.