CVE-2026-34637
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 · uneditedPremiere Pro versions 26.0.2, 25.6.4 and earlier are affected by an out-of-bounds write 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 confidencePremiere Pro contains an out-of-bounds write vulnerability that allows arbitrary code execution when a user opens a specially crafted malicious file, running with the privileges of the current user.
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< 25.6.5>= 26.0, < 26.2CVSS 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 checksWork through these to decide whether this CVE applies to you.
-
Check if Adobe Premiere Pro is installedOpen the Creative Cloud desktop app and look for Premiere Pro in the Installed apps section, or open Windows Settings > Apps > Installed apps and search for Premiere ProAffected if Premiere Pro is not listed as installed - the vulnerability does not apply
-
Determine the installed Premiere Pro versionOpen Premiere Pro, go to Help > About Adobe Premiere Pro to see the exact version number (e.g., 25.4.0, 26.1.0)Affected if The version displayed is < 25.6.5 OR >= 26.0 and < 26.2 - the version is vulnerable
-
Verify the file opening behaviorCheck if the application is configured to open files automatically or if users commonly drag-and-drop files into Premiere Pro (review any enterprise file handling policies)Affected if Users routinely open video files in Premiere Pro - the attack surface exists if version is vulnerable
-
Confirm the installed version against affected rangesCompare your installed version number to: 25.6.5 and 26.0-26.1.x. Versions before 25.6.5 and versions 26.0 through 26.1.x are affectedAffected if Your installed version matches the affected ranges listed above
You are affected if Adobe Premiere Pro is installed AND the installed version is either below 25.6.5 or falls between 26.0 and 26.2 (exclusive).
Generated from the published advisory. Verify against your own configuration.
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 · scoped25.6.526.2
Organizations should update Premiere Pro to the latest patched version once available and educate users to avoid opening files from untrusted sources.
Premiere Pro 25.6.5 or later; Premiere Pro 26.2 or later
- 1. Open Adobe Premiere Pro
- 2. Go to Help > Check for Updates to automatically download and install the latest version
- 3. Alternatively, manually download the updated Premiere Pro version from the official Adobe website (helpx.adobe.com)
- 4. Verify the installed version matches or exceeds the fixed release (25.6.5 for 25.x line, 26.2 for 26.x line)
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation4.0 h
- Implementation2.0 h
- Testing2.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,624.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-34637 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2026-34637 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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