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

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

Overview

CVE-2026-75665 is a Heap-based Buffer Overflow vulnerability (CWE-122) in Adobe Bridge that could result in arbitrary code execution in the context of the current user. The vulnerability affects Adobe Bridge versions 15.1.7 and earlier (15.x branch) and 16.0.6 and earlier (16.x branch). It was published on September 22, 2026, with a patch released the same day. The vulnerability carries a CVSS v3.1 base score of 7.8 (High) (GitHub Advisory, Adobe Advisory).

Technical details

The vulnerability is classified as CWE-122 (Heap-based Buffer Overflow), where a buffer allocated in the heap portion of memory can be overwritten due to insufficient bounds checking when processing file content. An attacker exploits this by crafting a malicious file that, when opened by a victim in Adobe Bridge, triggers the overflow and allows arbitrary code execution. The attack vector is local (AV:L), requires no privileges (PR:N), but does require user interaction (UI:R) — specifically, a victim must open the malicious file. No public proof-of-concept code has been identified (GitHub Advisory, Adobe Advisory).

Impact

Successful exploitation results in arbitrary code execution in the context of the current user, providing high confidentiality, integrity, and availability impact. An attacker could read sensitive files accessible to the user, modify or delete data, and potentially crash the application. Since execution occurs under the victim's user context, the scope is limited to that user's privileges, though it could serve as a foothold for further lateral movement if the compromised account has elevated permissions (GitHub Advisory).

Exploitability

There is no evidence of active in-the-wild exploitation or a publicly available proof-of-concept for CVE-2026-75665. The vulnerability is not listed in the CISA Known Exploited Vulnerabilities (KEV) catalog. The EPSS score is approximately 0.34% (0.003370), indicating a low probability of exploitation in the near term. The attack is not automatable, as it requires a victim to manually open a malicious file (GitHub Advisory).

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 contains malformed data designed to trigger a heap-based buffer overflow when parsed by the application.
  2. Deliver the file to the victim: The attacker distributes the malicious file via phishing email, file-sharing platform, or social engineering, convincing the target to open it with Adobe Bridge.
  3. Victim opens the file: The victim opens the malicious file in a vulnerable version of Adobe Bridge (≤15.1.7 or ≤16.0.6).
  4. Trigger the overflow: Adobe Bridge processes the malformed file content, causing a heap buffer overflow due to insufficient bounds checking.
  5. Achieve code execution: The overflow corrupts heap memory in a controlled manner, allowing the attacker to redirect execution flow and run arbitrary code in the context of the current user (GitHub 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 user-accessible directories (temp folders, AppData, Downloads) shortly after opening a file in Adobe Bridge; unexpected executables or scripts created by the Bridge process.
  • Network: Outbound network connections initiated by the Adobe Bridge process to unknown or suspicious external IP addresses or domains.
  • Logs: Application crash logs or Windows Event Logs (Event ID 1000/1001) referencing Adobe Bridge around the time of file opening; heap corruption or access violation errors in Bridge crash dumps.

Mitigation and workarounds

Adobe has released patched versions addressing this vulnerability: 15.1.8 for the 15.x branch and 16.0.7 for the 16.x branch. Users should update Adobe Bridge immediately via the Creative Cloud desktop application or Adobe's official download channels. As an interim measure, users should avoid opening files from untrusted or unknown sources in Adobe Bridge, and organizations may consider implementing application sandboxing or restricting Bridge's network access (Adobe Advisory, GitHub Advisory).

Community reactions

The Center for Internet Security (CIS) issued an advisory noting that multiple vulnerabilities in Adobe products, including this one, could allow for arbitrary code execution (CIS Advisory). Coverage was also noted in security news outlets and vulnerability tracking platforms. No significant researcher commentary or social media discussion specific to this CVE has been identified beyond standard patch-cycle reporting.

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