dbcve.org
Premiere ProApplication · Adobe

CVE-2025-27196

HIGH · 7.8 CVSS v3.1 Published 2025-04-08
Fix available
A fix is available. Upgrade to 24.6.5 / 25.2 or later.
See remediation →
81/100
Remediation priority · High
No privileges

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
Premiere Pro versions 25.1, 24.6.4 and earlier are affected by a Heap-based Buffer Overflow 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.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

Heap-based buffer overflow in Adobe Premiere Pro that triggers when a victim opens a specially crafted malicious file, potentially allowing arbitrary code execution in the context of the current user.

MitigationUpdate Premiere Pro to version 25.2 or later (or the latest patched version for 24.x); avoid opening files from untrusted sources.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
Premiere ProApplication
Affected:< 24.6.5>= 25.0, < 25.2

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Local
Complexity
Low
Privileges
None
User interaction
Required
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Locate Adobe Premiere Pro installation directory
    Check typical install paths: Windows typically uses 'C:\Program Files\Adobe\Adobe Premiere Pro' or 'C:\Program Files (x86)\Adobe\Adobe Premiere Pro'. On macOS, check '/Applications/Adobe Premiere Pro' or versioned subfolders like 'Adobe Premiere Pro 2024'.
    Affected if Adobe Premiere Pro is installed on the system
  2. Retrieve the installed Premiere Pro version
    On Windows: Right-click the Adobe Premiere Pro executable in the installation folder, select Properties, then view the Details tab for Product Version. Alternatively, open Registry Editor and navigate to HKLM\SOFTWARE\Adobe\Premiere Pro\[VersionKey] to find the InstallVersion value. On macOS: Right-click the application in Finder, select Get Info, and read the Version field.
    Affected if A version number is returned from the software
  3. Compare installed version against affected ranges
    Determine if the installed version falls into: 1) Any 24.x version earlier than 24.6.5, OR 2) Any 25.x version from 25.0 up to but not including 25.2. For example, versions like 24.5.0, 24.6.0, 25.0, 25.1 are all in the affected range.
    Affected if The installed version is < 24.6.5 OR (>= 25.0 AND < 25.2)
  4. Verify the file parsing component is reachable
    Confirm that the user can open project files, media files, or other loadable content through Premiere Pro. The vulnerability triggers specifically when opening a specially crafted malicious file - ensure the application is used for its intended file-opening functionality.
    Affected if Premiere Pro is functional and capable of opening project or media files

If Adobe Premiere Pro is installed and the version matches the affected ranges (< 24.6.5 or >= 25.0 to < 25.2), the environment is vulnerable to heap-based buffer overflow when opening specially crafted malicious files.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Upgrade available Upgrade to 24.6.5 / 25.2 or later
Fixed in 24.6.525.2
Interim mitigation

Update Premiere Pro to version 25.2 or later (or the latest patched version for 24.x); avoid opening files from untrusted sources.

Recommended fix High confidence

Premiere Pro 24.6.5 or later; Premiere Pro 25.2 or later

  1. Open Adobe Creative Cloud desktop application
  2. Navigate to the Apps tab
  3. Find Adobe Premiere Pro in the available updates
  4. Click Update to install the latest version
  5. Alternatively, download the fixed version directly from helpx.adobe.com
Caveat Adobe patch updates typically include bug fixes and security improvements with minimal risk

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Premiere Pro Scoped from the published advisory
  • Consultation1.0 h
  • Implementation2.0 h
  • Testing1.0 h
  • Review / QA1.0 h
5.0 hours of engineering $890
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,424.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2025-27196 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2025-27196 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data