Media EncoderApplication · Adobe

CVE-2024-49551

HIGH · 7.8 CVSS v3.1 Published 2024-12-10
Fix available
A fix is available. Upgrade to 24.6.3 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 25.0, 24.6.3 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 user opens a specially crafted malicious file. The vulnerability affects versions 25.0, 24.6.3 and earlier, and executes code in the context of the current user.

MitigationUpdate Adobe Media Encoder to the latest patched version. Additionally, educate users to avoid opening files from untrusted sources, as exploitation requires user interaction.

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:< 24.6.3= 25.0

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 Adobe Media Encoder or check the installed programs list in Windows Control Panel > Programs and Features, or on macOS in Applications folder
    Affected if Adobe Media Encoder is present on the system
  2. Determine the installed version number
    In Adobe Media Encoder, go to Help > About Adobe Media Encoder. Alternatively, check the version in the Windows registry at HKLM\SOFTWARE\Adobe\MediaEncoder or on macOS in /Applications/Adobe Media Encoder
    Affected if Version displayed is 25.0 or 24.6.3 or earlier
  3. Compare version against affected ranges
    If version shows 25.0, this is affected. If version shows 24.x, check if it is 24.6.3 or lower. Versions greater than 24.6.3 (such as 24.7, 24.8, etc.) are NOT affected
    Affected if Installed version is exactly 25.0 OR is 24.6.3 or any version lower than 24.6.3
  4. Confirm user interaction requirement
    Note that exploitation requires a user to open a specially crafted malicious file. Check if users routinely open media files from untrusted or unknown sources
    Affected if Users in the environment open files from untrusted sources, making them potential targets

A user is affected if Adobe Media Encoder version 25.0 or version 24.6.3 or earlier is installed AND users may open 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 24.6.3 or later
Fixed in 24.6.3
Interim mitigation

Update Adobe Media Encoder to the latest patched version. Additionally, educate users to avoid opening files from untrusted sources, as exploitation requires user interaction.

Recommended fix High confidence

Adobe Media Encoder 24.6.4 or later (or the 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 at adobe.com
  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 Media Encoder)
Caveat Standard upgrade; ensure system meets minimum requirements for the new version

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

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2024-49551 — 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 sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2024-49551 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