Skip to main content

Adobe Bridge CVE-2026-100129

| EUVDEUVD-2026-100623 HIGH
Out-of-bounds Write (CWE-787)
2026-10-13 psirt@adobe.com GHSA-whpv-mq67-5fx5
7.8
CVSS 3.1 · Vendor: adobe
View

Attack ChainAIDerived

Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain

  1. Access
    Craft malicious asset file
  2. Delivery
    Deliver to victim via email or download
  3. Exploit
    Victim opens file in Adobe Bridge
  4. Execution
    Trigger out-of-bounds write
  5. Impact
    Execute arbitrary code as current user

Vulnerability Assessment

Weakness
CWE
ASVS 5.0
V15 - Secure Coding and Architecture Bounds checking, write limits
MITRE ATT&CK

2 techniques across 2 tactics: Execution, Privilege Escalation

The technique list with ATT&CK links and the kill-chain view is part of the Basic plan and up.

Exploitation Conditions

Exploitation requires the victim to open an attacker-crafted malicious file within Adobe Bridge (the UI:R requirement) - it cannot be triggered remotely or without local user action. The vector is local (AV:L), so the attacker must first deliver the malicious file to the target. No authentication is required of the attacker (PR:N), and attack complexity is low (AC:L), meaning once the file is opened no additional special conditions, race windows, or non-default configurations are needed. The primary limiting factors are the mandatory user interaction and the local delivery requirement; affected deployments are Adobe Bridge versions ≤15.1.8 and ≤16.0.7.

Impact

This is a credible but second-tier priority. The CVSS 3.1 base score of 7.8 is driven by HIGH impact to confidentiality, integrity, and availability (C:H/I:H/A:H) enabling arbitrary code execution, but the attack vector is LOCAL (AV:L) and requires user interaction (UI:R) - a victim must open a malicious file. This is NOT a remotely-triggerable, wormable flaw; it is a client-side file-parsing bug typical of desktop creative applications. Exploitation status: no public exploit identified at time of analysis - the CVE is not in CISA KEV and no POC is referenced, so there is no evidence of active exploitation. No EPSS score, KEV entry, or SSVC decision data was provided in the input, so probabilistic exploitation likelihood cannot be quantified; this absence should not be read as either high or low risk. The signals are internally consistent (local vector + user interaction matches a 'open a malicious file' description), so there is no contradiction to flag. Net assessment: patch on a normal cycle, prioritizing workstations where Bridge users routinely open files from untrusted sources (e.g., downloaded assets, email attachments), but this does not warrant emergency out-of-band remediation absent exploitation evidence.

Exploit ScenarioDerived

An attacker crafts a malicious image or asset file and delivers it to a victim via email, a shared drive, or a compromised download (e.g., a stock-asset site). When the victim opens or previews the file in Adobe Bridge, the malformed data triggers an out-of-bounds write that corrupts memory and executes attacker-controlled code with the victim's privileges. No public exploit code has been identified, and successful exploitation depends entirely on convincing the user to open the file.

This Week Schedule remediation this week. Why: HIGH severity (CVSS 7.0-8.9).
No patch listed yet 0.2% exploitation probability (EPSS)

Get an e-mail when this CVE is exploited, patched or re-scored. Free account.

Alert me

AnalysisAIv1 – Oct 13, 2026

Out-of-bounds write in Adobe Bridge (versions up to and including 15.1.8 and 16.0.7) can let an attacker execute arbitrary code in the context of the current user when a crafted file is opened. The attack is local and requires the victim to open a malicious file (UI:R), so delivery of the file to the target and a user action are both prerequisites; no authentication is required of the attacker and complexity is low once the file is opened. There is no public exploit identified at time of analysis and the vulnerability is not in CISA KEV; the vendor advisory (APSB26-167) is the authoritative fix reference. Given the mandatory user interaction and local delivery requirement, this is a credible but second-tier priority rather than an urgent remotely exploitable issue.

RemediationAI

Apply the fix identified in Adobe's security bulletin APSB26-167 (https://www.adobe.com/trust/security/products/bridge/apsb26-167.html), which is the authoritative source for the patched Adobe Bridge versions; an exact fixed build number is not provided in the available intelligence, so verify the released version against the bulletin before closing out rather than assuming a version. Where immediate patching is not possible, reduce exposure with the following compensating controls, each with trade-offs: (1) instruct users not to open untrusted or unsolicited Bridge-compatible files, understanding this is a behavioral control with limited reliability; (2) restrict the file types Bridge is permitted to browse or preview via application preferences, accepting reduced functionality for legitimate asset workflows; (3) strip or block untrusted attachments and downloads at the email and web gateway and enforce Mark-of-the-Web/attachment policies, which lowers delivery success but is bypassable via user circumvention; (4) run Bridge under a low-privilege, non-administrative account, which caps impact but does not prevent the memory corruption itself; (5) apply application allowlisting and EDR memory-corruption detections on Bridge processes as detection rather than prevention, accepting potential false positives and tuning effort; and (6) if Bridge is not operationally required on a given endpoint, uninstall it to remove the attack surface entirely. Note that this vulnerability is not listed in CISA KEV and no public exploit code has been identified, so remediation should be scheduled through normal patch cycles rather than treated as an emergency response.

Affected VersionsENISA

Adobe Bridge 0 ≤15.1.8
Adobe Bridge 0 ≤16.0.7

Affected Packages

euvd adobe_bridge no fix

Source: OSV (Open Source Vulnerabilities)

Affects your stack

Affects 1 package in euvd

Checking this CVE against your own stacks and servers is part of the Basic plan and up.

Technical ContextAI · show details

The root cause is a CWE-787 out-of-bounds write in Adobe Bridge, Adobe's digital asset management and file-browsing application, which parses a wide range of image, vector, and media file formats as well as embedded metadata and XMP sidecar data. An out-of-bounds write occurs when the application computes a buffer size or index incorrectly while handling attacker-controlled file content and then writes past the end of the allocated buffer; in a memory-unsafe native codebase this typically corrupts adjacent heap or stack structures and, if the attacker can shape the surrounding memory, leads to controlled execution flow and arbitrary code execution in the context of the user running Bridge. The CVSS 3.1 vector (AV:L/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H) confirms the exploitation profile: the attack vector is local because the malicious file must be delivered to and opened on the target, no privileges are required (PR:N), complexity is low with no race or non-default configuration dependencies (AC:L), but a user must actively open the file (UI:R). Scope is unchanged, so code execution is confined to the Bridge process and the invoking user's permissions, which limits blast radius on properly configured endpoints but still yields full confidentiality, integrity, and availability impact for the user context.

Know when the next one hits your stack

  • Watch products and get an email when something new is published
  • Check this CVE against your own stack and servers
  • Exploit and PoC references, threat intelligence from 22 sources

No credit card · 7-day full trial

Severity by source

Vendor (adobe) PRIMARY 7.8 HIGH
AV:L/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H
vuln.today AI 7.8 HIGH

AV:L and UI:R because exploitation requires a local user to open a malicious file; PR:N as no attacker privileges are needed; C/I/A:H for arbitrary code execution as the current user.

3.1 AV:L/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H
4.0 AV:L/AC:L/AT:N/PR:N/UI:A/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N

Primary rating from Vendor (adobe).

CVSS VectorVendor: adobe

Attack Vector
Local
Attack Complexity
Low
Privileges Required
None
User Interaction
Required
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

DescriptionCVE.org

Bridge is affected by an out-of-bounds write vulnerability that could result in arbitrary code execution in the context of the current user. Exploitation of this issue requires user interaction in that a victim must open a malicious file.

Executive ViewAI

Why It Matters

Adobe Bridge, a widely deployed asset-management tool used by creative, marketing, and design teams, contains a high-severity memory-corruption flaw that can allow a crafted file to run attacker-controlled code with the privileges of the user who opens it. Because exploitation requires an employee to open a malicious file delivered to their workstation, the practical exposure is concentrated among staff who routinely open files from external sources, though a successful compromise could lead to data theft, credential capture, and onward movement from an otherwise trusted creative workstation. Leadership should treat this as a targeted, user-driven risk that warrants prompt inventory, containment, and monitoring rather than an emergency remote-exploit response.

Business Impact: Medium
Compensating Controls

No vendor-released patch identified at time of analysis. Interim mitigations: block or quarantine untrusted creative asset file types at email and web gateways; instruct users not to open files from unverified external sources; disable automatic previewing and thumbnail rendering of externally sourced files where feasible; ensure EDR is deployed and alerting on all hosts running Adobe Bridge at or below 15.1.8 or 16.0.7; remove standing local administrator rights from creative workstations; segment and monitor those endpoints for anomalous process spawning or outbound connections; and continue tracking vendor advisory APSB26-167 for the authoritative fix.

Threat Intelligence Overview

EPSS Score
0.2%
Top 96% exploitable
Prevalence
Medium
widely-used Adobe Creative Cloud asset manager, common but not universal
Data Quality
5 sources
Confidence: Medium

How this decision was reached

The engine reads each signal below and applies a fixed list of rules from top to bottom. The first rule that matches sets the recommended action – like a statement, every line is shown.

SignalValue
Severity HIGH
CISA KEV No
Public POC No
EPSS 0.2%
Patch available No
Active threat No
Deciding rule
HIGH severity (CVSS 7.0-8.9)
What every action level means
Emergency Immediate action required. Criteria: CRITICAL + in CISA KEV (actively exploited) without patch, OR CRITICAL + EPSS > 30% without patch, OR CRITICAL + active threat signals without patch.
Act Now Prioritize within 24-48h. Criteria: in KEV with patch available, OR CRITICAL + public POC, OR HIGH + EPSS > 10%, OR CRITICAL + active threat, OR any CRITICAL severity.
This Week Schedule remediation this week. Criteria: HIGH severity (CVSS 7.0-8.9). Patch within normal change window.
This Month Plan within 30 days. Criteria: MEDIUM severity (CVSS 4.0-6.9), lower exploitation probability. Include in regular patch cycle.
Monitor Track and reassess. Criteria: LOW severity (CVSS 0.1-3.9), minimal exploitation risk. No immediate action needed.

SSVC AssessmentENISA

SSVC Decision
Defer
Exploitation
None
System Exposure· derived
Small
Automatable
No
Human Impact
Medium
Technical Impact
Total

Priority Score

39
Low Medium High Critical
KEV: 0
EPSS: 0
CVSS: +39
PoC: 0
Weaponized: 0
Threat intel: 0
Gov advisory: 0

Attack Technique

A buffer overflow occurs when a program writes more data to a memory buffer than it was allocated to hold, causing the excess data to spill into adjacent memory regions.

Memory corruption occurs when a program writes data beyond the boundaries of allocated memory regions or accesses memory in unintended ways, violating the integrity of the process's address space.

Remote Code Execution represents the critical moment when an attacker successfully runs arbitrary code on a target system without physical access.

This site uses cookies essential for authentication and security. No tracking or analytics cookies are used. Privacy Policy