CVE-2026-110088: Premiere code execution in file handling

Summary

Premiere Pro has a buffer overflow flaw that lets an attacker run arbitrary code with the privileges of the current user. Exploitation is local and requires no login, but a victim must open a malicious file.

Read the original description

Premiere Pro is affected by a Buffer Overflow vulnerability that could result in arbitrary code execution in the context of the current user. An attacker could exploit this vulnerability to execute arbitrary code. Exploitation of this issue requires user interaction in that a victim must open a malicious file.

Who should check

Teams running Adobe Premiere 26.5.2 and earlier, or 25.6.6 and earlier, on Windows or macOS

Read the source excerpt

“25.6.6 and earlier”

adobe.com

cve.now Index

18Pcve.now Index 18 of 100 · methodology v3 · provisional

Exploitation?/40Unknown. No CISA SSVC exploitation rating yet
Exposure5/25Specific setups only
Reach?/20Unknown. No tracked technology or package matched
Severity7.8/10CVSS 7.8
No patch5/5No patch listed yet

What would change the score

Would score about 68 if added to CISA KEV
Would score about 63 if CISA's SSVC rates exploitation active
Would score about 28 if CISA's SSVC rates it automatable

How the score works · Rankings

What to do

Check whether your setup matches what the bug needs.
Adobe Premiere 26.5.2 and earlier, or 25.6.6 and earlier Windows and macOS platforms
Workaround: The checked facts list no workaround or mitigation. No fix is recorded in the facts, so there is no documented step to take while waiting for one.

Check your systems with an agent

Paste this into a coding or ops agent. It checks your systems read-only and reports a table per asset.

Check whether my systems are affected by CVE-2026-110088 (Premiere Pro | Buffer Overflow (CWE-120)), using the cve.now data below.

Rules: work read-only. Do not run exploit code, proof-of-concept scripts or scanners that send attack payloads, and do not change any configuration, package, image or deployment. Report findings only.

What cve.now has for CVE-2026-110088 (entry last updated 2026-11-10):
Affected:
- Adobe Premiere: through 26.5.2
- Adobe Premiere: through 25.6.6
Fixed versions: none listed yet.
Conditions (all must be true for the bug to be hit):
- Adobe Premiere 26.5.2 and earlier, or 25.6.6 and earlier (source: https://www.adobe.com/trust/security/products/premiere/apsb26-101.html)
- Windows and macOS platforms (source: https://www.adobe.com/trust/security/products/premiere/apsb26-101.html)
Setup: unknown whether the bug needs a non-default feature or setting. Check the advisory.
Attacker needs: local access, no login, a user action.
CISA KEV: CVE-2026-110088 is not listed as of cve.now's last read.
This KEV status is for CVE-2026-110088 only. If you also check another CVE, look up its own KEV status; never assume it from this one.

How to check:
- Installed software: check what is actually running, not what a repo declares. Read the version from each host, container image and Kubernetes node (the binary's version output, the OS package database, image layers), and check whether the conditions above hold there. Distribution packages may carry a backported fix under an older version number; confirm against the distribution's own advisory.

Verify against the linked advisories before concluding, and cite the date you read each one:
- https://www.adobe.com/trust/security/products/premiere/apsb26-101.html
Do not conclude an asset is unaffected unless you checked it and the evidence covers both its version and the conditions above. If you could not check something, mark it unknown and say what is missing.

Entry: https://cve.now/CVE-2026-110088
For follow-up questions, use the cve.now MCP server at https://mcp.cve.now/mcp (no authentication), for example get_vulnerability with id CVE-2026-110088.

Timeline

Nov 10, 2026, 8:25 PM UTCCVE published
Nov 10, 2026, 9:22 PM UTCFirst seen by cve.now

Affected versions

Adobe Premiere
through 26.5.2
Adobe Premiere
through 25.6.6

Evidence 3

Vendor advisory · 1

Establishes: Affected and fixed versions.

Advisory
adobe.com · trust/security/products/premiere/apsb26-101.html

CVE record · 2

Establishes: The identifier and description.

Record
CVE List · CVE-2026-110088
Record
NVD · CVE-2026-110088

Corrections

None so far.

Something wrong on this page? Report an error. Every fix is listed here.

Questions about CVE-2026-110088

Is CVE-2026-110088 being exploited?

It is not in CISA's Known Exploited Vulnerabilities catalog, and CISA's SSVC assessment does not mark exploitation as active. That does not mean it has not been attacked: vendors and researchers can report attacks before CISA lists them. No public exploit code is tracked.Source: cve.now feed data

What does this mean?

A buffer overflow happens when a program writes more data into a fixed-size area of memory than it can hold. The extra data can overwrite nearby memory, and this bug could result in arbitrary code execution in the context of the current user.Source: adobe.com

Which versions are affected by CVE-2026-110088?

Premiere: through 26.5.2. Premiere: through 25.6.6.Source: cve.now feed data

Am I affected, and how do I check?

The listed affected versions are Adobe Premiere 26.5.2 and earlier, and Adobe Premiere 25.6.6 and earlier, on Windows and macOS. Compare the installed Premiere version against these ranges.Source: adobe.com

How do I fix CVE-2026-110088?

The checked facts do not name a fixed version or an upgrade target. Check Adobe's advisory for a fixed release before deciding what to install.Source: adobe.com

What if there's no patch?

The checked facts list no workaround or mitigation. No fix is recorded in the facts, so there is no documented step to take while waiting for one.Source: adobe.com

Premiere Pro | Buffer Overflow (CWE-120)