dbcve.org
Media EncoderApplication · Adobe

CVE-2026-47976

HIGH · 7.8 CVSS v3.1 Published 2026-07-14
Fix available
A fix is available. Upgrade to after 26.2.2 or later.
See remediation →
81/100
Remediation priority · High
No privileges 5 weeks old

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 is 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 processing a specially crafted malicious file. The vulnerability stems from improper bounds checking during media file parsing, allowing a crafted file to write beyond allocated memory boundaries.

MitigationAvoid opening untrusted or unexpected media files in Media Encoder until the vendor releases and applies the security patch.

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.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. Confirm Adobe Media Encoder is installed
    Check for Adobe Media Encoder in the system. On Windows, look in Program Files/Adobe folder or check Programs and Features. On macOS, check /Applications folder for Adobe Media Encoder.
    Affected if Adobe Media Encoder is not installed on the system.
  2. Identify installed version number
    Open Adobe Media Encoder and navigate to Help > About Adobe Media Encoder. Alternatively, on Windows right-click the application in Programs and Features and select Properties to view the version. On macOS, right-click the app in Applications and select Get Info.
    Affected if Unable to determine the installed version.
  3. Compare version against affected ranges
    Compare your installed version to the vulnerable ranges: version 25.6.5 or lower, OR version 26.0 through 26.2.2.
    Affected if Installed version falls within <= 25.6.5 or >= 26.0 through <= 26.2.2.
  4. Assess file processing exposure
    Determine if the system processes media files from external or untrusted sources. Review workflow to see if Media Encoder is used to encode files received from email, web downloads, or external vendors.
    Affected if Media Encoder processes files from untrusted or unknown sources.

System is affected if Adobe Media Encoder is installed with a vulnerable version AND the application is used to process media files from untrusted sources.

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 a release after 26.2.2
Interim mitigation

Avoid opening untrusted or unexpected media files in Media Encoder until the vendor releases and applies the security patch.

Recommended fix Moderate confidence

Media Encoder 25.6.6 or later (25.x branch); 26.2.3 or later (26.x branch)

  1. Open Adobe Creative Cloud desktop application or navigate to adobe.com/products/media-encoder
  2. Check for available updates for Adobe Media Encoder
  3. Download and install the latest version of Adobe Media Encoder
  4. Alternatively, open Media Encoder and go to Help > Check for Updates
  5. Verify the installed version is 25.6.6 or later for 25.x branch, or 26.2.3 or later for 26.x branch
  6. Restart the application after updating

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

Fix this in Media Encoder Scoped from the published advisory
  • Consultation3.0 h
  • Implementation6.0 h
  • Testing6.0 h
  • Review / QA3.0 h
18.0 hours of engineering $3,120
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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