Skip to main content
VulnerabilityPublished Updated

CVE-2025-54242: Adobe Premiere Pro · Use After Free

Affects Adobe Premiere ProSource CVE Database V5

0

Not known to be exploited · CVSS 7.8 High.

Data as of 26 Oct 2026, 12:55 UTC

CVSS 3.1 base score
7.8High
How severe the flaw is on the 0–10 CVSS scale.
EPSS
0.2% chance of exploitation in 30 days – higher than 10% 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 9 Sep 2025

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponised: 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 26 Oct 2026.

What to do

Affected software

ProductAffectedFixed in
Adobe Premiere ProAffected
  • =0
Fixed in–

AI-suggested

Until an official patch is released, organizations should implement several specific mitigations: 1) Enforce strict file handling policies by restricting the opening of files from untrusted or unknown sources within Adobe Premiere Pro. 2) Educate users about the risks of opening unsolicited or suspicious project files and encourage verification of file origins. 3) Utilize application sandboxing or containerization technologies to limit the impact of potential exploitation by isolating Premiere Pro processes. 4) Employ endpoint detection and response (EDR) solutions to monitor for anomalous behaviors related to file access and code execution within Premiere Pro. 5) Regularly back up critical project files and maintain offline copies to mitigate data loss from potential attacks. 6) Monitor Adobe's security advisories closely for patch releases and apply updates promptly once available. 7) Consider limiting user privileges where possible to reduce the impact of code execution under user context. These targeted actions go beyond generic advice by focusing on controlling file sources, user awareness, and containment strategies specific to this vulnerability.

Description

Premiere Pro versions 25.3, 24.6.5 and earlier are affected by a Use After Free 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, and scope is unchanged.

References

Community reviews

Loading reviews…