Skip to main content
VulnerabilityPublished Updated

CVE-2026-27269: Adobe Premiere · Out-of-bounds Read

Affects Adobe PremiereSource CVE Database V5

0
Compare

Not known to be exploited · CVSS 7.8 High.

Data as of 30 Oct 2026, 06:59 UTC

CVSS 3.1 base score
7.8High
How severe the flaw is on the 0–10 CVSS scale.
EPSS
0.1% chance of exploitation in 30 days – higher than 6% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 10 Mar 2026

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponized: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 29 Oct 2026.

What to do

Affected software

ProductAffectedFixed in
AdobePremiereAffected
  • <=25.5
Fixed in–
AdobePremiere ProAffected
  • <=25.5
Fixed in–

AI-suggested

Until an official patch is released, organizations should implement strict controls on file sources, restricting Premiere Pro project files and media imports to trusted origins only. Employ advanced email filtering and user awareness training to reduce the risk of phishing attacks delivering malicious files. Utilize endpoint detection and response (EDR) solutions to monitor for suspicious behaviors related to Adobe Premiere Pro processes. Enforce the principle of least privilege by ensuring users run Premiere Pro with minimal necessary permissions to limit potential damage from exploitation. Regularly back up critical project data to enable recovery in case of compromise. Once Adobe releases a patch, prioritize immediate deployment across all affected systems. Additionally, consider sandboxing or isolating Premiere Pro usage environments to contain potential exploitation.

Description

Premiere Pro versions 25.5 and earlier are affected by an out-of-bounds read vulnerability when parsing a crafted file, which could result in a read past the end of an allocated memory structure. An attacker could leverage this vulnerability to execute code in the context of the current user. Exploitation of this issue requires user interaction in that a victim must open a malicious file.

References

Community reviews

Loading reviews…