dbcve.org
Media EncoderApplication · Adobe

CVE-2026-34639

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
Media Encoder 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 confidence

Adobe Media Encoder contains an out-of-bounds write vulnerability that allows arbitrary code execution when a victim opens a malicious file. The vulnerability exists in versions 26.0.2, 25.6.4 and earlier, and executes code in the context of the current user.

MitigationUpdate Adobe Media Encoder to the latest patched version. Avoid opening untrusted or suspicious media files from unknown 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
Media EncoderApplication
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. Verify Adobe Media Encoder is installed
    Open Windows Control Panel > Programs and Features, or macOS Applications folder, and look for Adobe Media Encoder. On Windows, you can also check: HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall\Adobe Media Encoder in the Registry Editor.
    Affected if Adobe Media Encoder is not found in the system, the vulnerability does not apply.
  2. Locate the installed version number
    In Windows: Right-click Adobe Media Encoder in Programs and Features and select Properties > Details to view the version. On macOS: Right-click Adobe Media Encoder in Applications > Get Info > Version. You can also launch the application and go to Help > About Adobe Media Encoder.
    Affected if The version cannot be determined, treat as potentially vulnerable.
  3. Compare installed version against vulnerable ranges
    The vulnerable version ranges are: 25.6.4 and earlier, OR any version from 26.0 up to 26.0.2 (including 26.0, 26.0.1, 26.0.2). Compare your installed version number to these ranges.
    Affected if Installed version is 25.6.4 or lower, OR is 26.0, 26.0.1, or 26.0.2.
  4. Confirm the version is patched
    The patched (non-vulnerable) versions are 25.6.5 or higher in the 25.x branch, OR 26.2 or higher in the 26.x branch. Verify your version falls outside the vulnerable ranges.
    Affected if Installed version is 25.6.5 or higher in the 25.x line, OR 26.2 or higher in the 26.x line, then the environment is NOT affected by this CVE.

The environment is affected if Adobe Media Encoder is installed with version 25.6.4 or earlier, or any version from 26.0 through 26.0.2.

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 Adobe Media Encoder to the latest patched version. Avoid opening untrusted or suspicious media files from unknown sources.

Recommended fix High confidence

Media Encoder 25.6.5 (for 25.x branch) or Media Encoder 26.2 (for 26.x branch)

  1. Navigate to the Adobe Creative Cloud desktop application or visit helpx.adobe.com to download the latest version of Adobe Media Encoder
  2. If using Media Encoder 25.x branch, upgrade to version 25.6.5 or later
  3. If using Media Encoder 26.x branch, upgrade to version 26.2 or later
  4. After upgrading, verify the version by opening Media Encoder and checking Help > About Adobe Media Encoder
  5. Ensure end users are advised not to open untrusted or malicious media files

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

Fix this in Media Encoder Scoped from the published advisory
  • Consultation2.0 h
  • Implementation1.0 h
  • Testing3.0 h
  • Review / QA1.0 h
7.0 hours of engineering $1,210
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,936.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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