dbcve.org
Media EncoderApplication · Adobe

CVE-2019-8246

CRITICAL · 9.8 CVSS v3.1 Published 2019-11-14
Fix available
A fix is available. Upgrade to after 13.1 or later.
See remediation →
100/100
Remediation priority · Urgent
Remotely reachable No privileges Zero-click

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
Adobe Media Encoder versions 13.1 and earlier have an out-of-bounds write vulnerability. Successful exploitation could lead to arbitrary code execution .

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 versions 13.1 and earlier contain an out-of-bounds write vulnerability where the software writes data beyond the intended memory buffer boundaries. Successful exploitation allows attackers to execute arbitrary code in the context of the current user.

MitigationUpdate Adobe Media Encoder to a version newer than 13.1. Apply vendor-released security patches and ensure endpoint protection is active.

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:<= 13.1

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
Network
Complexity
Low
Privileges
None
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/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
    Check for Adobe Media Encoder in the system program list. On Windows, open Control Panel > Programs and Features, or run 'Get-WmiObject -Class Win32_Product' in PowerShell to list installed software.
    Affected if Adobe Media Encoder appears in the installed programs list
  2. Locate the Adobe Media Encoder executable
    Search for 'Adobe Media Encoder.exe' in common installation directories: C:\Program Files\Adobe\Adobe Media Encoder\ or C:\Program Files (x86)\Adobe\Adobe Media Encoder\
    Affected if The executable file exists at these paths
  3. Determine the installed version
    Right-click the Adobe Media Encoder.exe file, select Properties, then view the Details tab to see the File Version. Alternatively, right-click the application in Programs and Features and select 'Change' to view version information.
    Affected if The displayed version number is 13.1 or earlier (such as 13.0, 12.x, etc.)
  4. Cross-check version via registry
    On Windows, open the Registry Editor and navigate to HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall\ looking for an Adobe Media Encoder entry, or check HKLM\SOFTWARE\Adobe\MediaEncoder\ for a Version value.
    Affected if The registry key shows a version value of 13.1 or lower

The system is affected if Adobe Media Encoder is installed with any version numbered 13.1 or lower, since the out-of-bounds write vulnerability exists in these versions and can allow arbitrary code execution.

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 13.1
Interim mitigation

Update Adobe Media Encoder to a version newer than 13.1. Apply vendor-released security patches and ensure endpoint protection is active.

Recommended fix Moderate confidence

Adobe Media Encoder 13.1.1 or later (or latest available version)

  1. 1. Close Adobe Media Encoder if it is currently running
  2. 2. Download the latest version of Adobe Media Encoder from the official Adobe website or Creative Cloud desktop application
  3. 3. Run the installer and follow the on-screen prompts to complete the installation
  4. 4. After installation, verify the version number in the application (Help > About Adobe Media Encoder)
  5. 5. Ensure the installed version is greater than 13.1
Caveat Standard upgrade considerations apply - review release notes for new features or changes to workflow

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
  • Implementation2.0 h
  • Testing1.0 h
  • Review / QA1.0 h
6.0 hours of engineering $1,090
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,744.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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