dbcve.org
Media EncoderApplication · Adobe

CVE-2026-47979

MEDIUM · 5.5 CVSS v3.1 Published 2026-07-14
Fix available
A fix is available. Upgrade to after 26.2.2 or later.
See remediation →
58/100
Remediation priority · Elevated
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 read vulnerability that could lead to disclosure of sensitive memory. An attacker could leverage this vulnerability to disclose sensitive information. 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 · moderate confidence

Media Encoder contains an out-of-bounds read vulnerability that allows disclosure of sensitive memory contents when a user opens a malicious file. This type of vulnerability occurs when the software reads memory beyond allocated buffer boundaries, potentially exposing sensitive data in the process memory.

MitigationUpdate Media Encoder to the latest patched version provided by the vendor. Users should avoid opening files from untrusted or unknown sources to mitigate exploitation.

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
None
Availability
None

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

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 installation
    Locate the Media Encoder application on the system through the installed programs list or program files directory
    Affected if Media Encoder is present on the system
  2. Identify the installed version number
    Access the version information through the application's About dialog, Help menu, or application properties in the system
    Affected if Version number cannot be determined
  3. Compare version against affected ranges
    If version is 25.x, check if it is 25.6.5 or lower. If version is 26.x, check if it is 26.2.2 or lower. Versions 25.6.6 and above, or 26.2.3 and above, are NOT in the affected range
    Affected if Version is 25.6.5 or lower, OR version is between 26.0 and 26.2.2 inclusive

Your environment is affected if Adobe Media Encoder is installed and the version falls within 25.6.5 or lower, or within 26.0 to 26.2.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.

From vendor data
Upgrade available Upgrade to a release after 26.2.2
Interim mitigation

Update Media Encoder to the latest patched version provided by the vendor. Users should avoid opening files from untrusted or unknown sources to mitigate exploitation.

Fix this in Media Encoder Scoped from the published advisory
  • Consultation1.0 h
  • Implementation1.0 h
  • Testing2.0 h
  • Review / QA1.0 h
5.0 hours of engineering $860
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,376.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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