PHP2Shell: Read our blog on the critical RCE vulnerabilities affecting 70% of the Internet

CVE-2026-75658: 
Adobe Bridge vulnerability analysis and mitigation

Overview

CVE-2026-75658 is an out-of-bounds write vulnerability (CWE-787) in Adobe Bridge that could result in arbitrary code execution in the context of the current user. It affects Adobe Bridge versions up to and including 16.0.6 (in the 16.x branch) and up to and including 15.1.7 (in the 15.x branch). The vulnerability was published on September 22, 2026, with a patch made available the same day. It carries a CVSS v3.1 base score of 7.8 (High) (GitHub Advisory, Adobe Advisory).

Technical details

The vulnerability is classified as CWE-787 (Out-of-bounds Write), meaning the application writes data beyond the boundaries of an allocated buffer when processing certain file types. Exploitation requires a victim to open a specially crafted malicious file in Adobe Bridge, making the attack vector local with required user interaction. No privileges are required on the part of the attacker to craft or deliver the malicious file. No public proof-of-concept or detailed technical write-up has been identified at this time (GitHub Advisory, Adobe Advisory).

Impact

Successful exploitation allows an unauthenticated attacker to execute arbitrary code with the privileges of the user running Adobe Bridge, resulting in high confidentiality, integrity, and availability impact on the affected system. An attacker who achieves code execution could access sensitive files, modify data, install malware, or use the compromised session as a foothold for lateral movement within the network. The scope is limited to the current user's context, meaning administrator-level compromise is not guaranteed unless the victim runs Bridge with elevated privileges (GitHub Advisory).

Exploitability

There is no evidence of active in-the-wild exploitation or a publicly available proof-of-concept at this time (GitHub Advisory). The NVD SSVC assessment confirms exploitation status as "none" and the attack is not automatable due to the required user interaction. The EPSS score is approximately 0.256% (roughly the 3rd percentile), indicating a low near-term probability of exploitation. The vulnerability is not currently listed in the CISA Known Exploited Vulnerabilities (KEV) catalog.

Exploitation steps

  1. Craft a malicious file: An attacker creates a specially crafted file (e.g., an image or media file supported by Adobe Bridge) that triggers the out-of-bounds write vulnerability when parsed.
  2. Deliver the file to the victim: The attacker distributes the malicious file via phishing email, malicious download link, shared network drive, or other social engineering methods.
  3. Victim opens the file: The victim opens the malicious file using a vulnerable version of Adobe Bridge (≤16.0.6 or ≤15.1.7).
  4. Trigger out-of-bounds write: Adobe Bridge processes the malformed file, causing the application to write data outside the intended buffer boundary (CWE-787).
  5. Achieve code execution: The memory corruption resulting from the out-of-bounds write is leveraged to redirect execution flow, allowing arbitrary code to run in the context of the current user (GitHub Advisory, Adobe Advisory).

Indicators of compromise

  • Process: Unexpected child processes spawned by Adobe Bridge (e.g., cmd.exe, powershell.exe, bash, curl, or other shells/utilities not normally launched by Bridge).
  • File System: Unusual files written to temp directories or the user's profile by the Bridge process; unexpected executables or scripts appearing after opening a file in Bridge.
  • Network: Outbound network connections initiated by the Adobe Bridge process to unknown or suspicious external IP addresses or domains shortly after file open events.
  • Logs: Application crash logs or Windows Event Logs showing access violation or memory corruption errors in the Adobe Bridge process around the time a suspicious file was opened.

Mitigation and workarounds

Adobe has released patched versions to address this vulnerability: users on the 16.x branch should update to Adobe Bridge 16.0.7 or later, and users on the 15.x branch should update to 15.1.8 or later (Adobe Advisory). As an interim workaround, users should avoid opening untrusted, unexpected, or suspicious files in Adobe Bridge until patching is complete. Organizations should implement user awareness training to reduce the risk of social engineering attacks that rely on victims opening malicious files.

Community reactions

The CIS (Center for Internet Security) issued an advisory noting that multiple vulnerabilities in Adobe products, including this one, could allow for arbitrary code execution (CIS Advisory). AusCERT also published a bulletin (ESB-2026.11485) covering the Adobe Bridge security update. General media coverage noted the vulnerability as part of Adobe's broader September 2026 security update cycle, with no significant independent researcher commentary or social media discussion identified at this time.

Additional resources


Source: This report was generated using AI

Related Adobe Bridge vulnerabilities:

CVE ID

Severity

Score

Technologies

Component name

CISA KEV exploit

Has fix

Published date

CVE-2026-100129HIGH7.8
  • Adobe Bridge logoAdobe Bridge
  • cpe:2.3:a:adobe:bridge
NoNoOct 13, 2026
CVE-2026-100128HIGH7.8
  • Adobe Bridge logoAdobe Bridge
  • cpe:2.3:a:adobe:bridge
NoNoOct 13, 2026
CVE-2026-100127HIGH7.8
  • Adobe Bridge logoAdobe Bridge
  • cpe:2.3:a:adobe:bridge
NoNoOct 13, 2026
CVE-2026-75676HIGH7.8
  • Adobe Bridge logoAdobe Bridge
  • bridge
NoYesSep 22, 2026
CVE-2026-100126MEDIUM5.5
  • Adobe Bridge logoAdobe Bridge
  • cpe:2.3:a:adobe:bridge
NoNoOct 13, 2026

Free Vulnerability Assessment

Benchmark your Cloud Security Posture

Evaluate your cloud security practices across 9 security domains to benchmark your risk level and identify gaps in your defenses.

Request assessment

Get a personalized demo

Ready to see Wiz in action?

"Best User Experience I have ever seen, provides full visibility to cloud workloads."
David EstlickCISO
"Wiz provides a single pane of glass to see what is going on in our cloud environments."
Adam FletcherChief Security Officer
"We know that if Wiz identifies something as critical, it actually is."
Greg PoniatowskiHead of Threat and Vulnerability Management