dbcve.org
Premiere ProApplication · Adobe

CVE-2026-34638

HIGH · 7.8 CVSS v3.1 Published 2026-05-12
Fix available
A fix is available. Upgrade to 25.6.5 / 26.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 26.0.2, 25.6.4 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.

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

Adobe Premiere Pro contains a Use After Free vulnerability where memory is accessed after being freed, enabling arbitrary code execution when a user opens a malicious file. The vulnerability affects versions 26.0.2, 25.6.4 and earlier.

MitigationUpdate Premiere Pro to the latest patched version beyond 26.0.2/25.6.4 and exercise caution when 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:< 25.6.5>= 26.0, < 26.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. Find installed Premiere Pro version on Windows
    Open Premiere Pro, go to Help > About Adobe Premiere Pro, or open Windows Settings > Apps > Apps & Features and locate Adobe Premiere Pro to see the installed version number
    Affected if Version shown is 25.6.4 or earlier, OR version is 26.0.0 through 26.1.x (any 26.0.x or 26.1.x release)
  2. Find installed Premiere Pro version on macOS
    Open Premiere Pro, go to Premiere Pro > About Adobe Premiere Pro, or open Finder > Applications and right-click Premiere Pro to Get Info showing the version
    Affected if Version shown is 25.6.4 or earlier, OR version is 26.0.0 through 26.1.x (any 26.0.x or 26.1.x release)
  3. Confirm vulnerable version range
    Compare your installed version number to the affected ranges: versions 25.x below 25.6.5, and versions 26.0.x below 26.2
    Affected if Your installed version falls into either < 25.6.5 (for 25.x branch) OR >= 26.0 and < 26.2 (for 26.x branch)
  4. Determine exposure to malicious files
    Premiere Pro must be able to open project files or media files for this vulnerability to be triggered. Check if the application is configured to open files from untrusted or unknown sources
    Affected if The vulnerable version is installed AND the application has permission to open project or media files (which is the default behavior for Premiere Pro)

You are affected if your installed Adobe Premiere Pro version is 25.6.4 or earlier, or any 26.0.x/26.1.x version below 26.2, and you use the software to open project or media 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 25.6.5 / 26.2 or later
Fixed in 25.6.526.2
Interim mitigation

Update Premiere Pro to the latest patched version beyond 26.0.2/25.6.4 and exercise caution when opening files from untrusted sources.

Recommended fix High confidence

Premiere Pro 25.6.5 or later for 25.x branch; Premiere Pro 26.2 or later for 26.x branch

  1. 1. Open Adobe Premiere Pro
  2. 2. Go to Help > Check for Updates
  3. 3. If updates are available, download and install the latest version
  4. 4. Alternatively, manually download Premiere Pro version 25.6.5 or later (25.x branch) or version 26.2 or later (26.x branch) from the official Adobe website

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

Fix this in Premiere Pro Scoped from the published advisory
  • Consultation2.0 h
  • Implementation2.0 h
  • Testing3.0 h
  • Review / QA2.0 h
9.0 hours of engineering $1,570
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-34638 — 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-2026-34638 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