CVE-2026-48396 is an incorrect authorization vulnerability in Adobe Bridge that can lead to arbitrary code execution in the context of the current user. The issue affects Adobe Bridge versions 16.0.5 and earlier and 15.1.6 and earlier. Exploitation requires user interaction: a victim must open a malicious file. The vulnerability is classified as scope-changed and is associated with a CVSS v3.1 vector of AV:L/AC:L/PR:N/UI:R/S:C/C:H/I:H/A:H, indicating high impact to confidentiality, integrity, and availability once triggered.
Mallory correlates every CVE against your assets, your vendors, and active adversary campaigns. Know which vulnerabilities matter for you, not just which ones are loud.
What it means. What to do now. Patch path, mitigations, and the assume-compromise checklist.
What an attacker gets, and what they’ve been doing with it.
If you can’t patch tonight, do this now.
Patch, then assume compromise.
No public exploits tracked yet. Mallory keeps watching.
No public exploit code observed for this vulnerability.
Products and vendors Mallory has correlated with this vulnerability. Open in Mallory to drill down to specific CPE configurations and version ranges.
Vendor-confirmed product mapping. Mallory continuously reconciles this list against your asset inventory.
5 sources tracked across advisories, community write-ups, and news. New activity surfaces here as Mallory finds it.
A critical incorrect authorization vulnerability in Adobe Bridge that could allow arbitrary code execution.
A critical incorrect authorization vulnerability in Adobe Bridge that could lead to arbitrary code execution.
An incorrect authorization vulnerability in Adobe Bridge that can lead to arbitrary code execution in the context of the current user if a victim opens a malicious file.
Query your assets running an affected version, and investigate the blast radius.
Every observed campaign linking this CVE to a named adversary.
Malware families riding this exploit, with evidence and IOCs.
YARA, Sigma, Snort, and vendor rules, auto-deployed to your SIEM.
Cross-references every affected SKU, including bundled OEM variants.
Community discussion across Reddit, Mastodon, and other social sources.