Quick answers
- Is CVE-2026-110088 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-110088 being exploited in the wild.
- How severe is CVE-2026-110088?
- High severity, with a CVSS score of 7.8, published 10 November 2026.
- Which products and versions are affected?
- Adobe Premiere Pro 26.5.2 and earlier; 25.6.6 and earlier.
- Is there a fix for CVE-2026-110088?
- Yes: fixed in Premiere Pro 27.0, Premiere Pro 26.5.3. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
- How is CVE-2026-110088 attacked?
- It is attacked with local access, in a web application.
- Am I affected by CVE-2026-110088?
- Check whether you run Adobe Premiere Pro at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.
How to fix
- Fixed in: Premiere Pro 27.0, Premiere Pro 26.5.3
Technical details
Multiple memory safety issues (buffer overflows, buffer underflows, and out-of-bounds writes) in Adobe Premiere Pro version 26.5.2 and earlier allow code execution in the context of the current user. Exploitation requires local file system access and user interaction to open a malicious file; the application parses untrusted media data without proper bounds checking. Additional vulnerabilities include path traversal for arbitrary file read, missing authentication for file write operations, and NULL pointer dereference causing denial of service.
Affected products
- Adobe Premiere Pro 26.5.2 and earlier; 25.6.6 and earlier
Timeline
- 2026-11-10: disclosed