Media EncoderApplication · Adobe

CVE-2021-36070

HIGH · 7.8 CVSS v3.1 Published 2021-09-01
Fix available
A fix is available. Upgrade to after 15.4 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
Adobe Media Encoder version 15.1 (and earlier) is affected by an improper memory access vulnerability when parsing a crafted .SVG file. An attacker could leverage this vulnerability to execute code 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 versions 15.1 and earlier contain an improper memory access vulnerability when parsing crafted SVG files. Successful exploitation allows arbitrary code execution in the context of the current user, requiring the victim to open a malicious SVG file.

MitigationUpdate Adobe Media Encoder to a version newer than 15.1. Until patched, instruct users not to open untrusted SVG 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:<= 15.4

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 installation
    Check Windows Programs and Features or macOS Applications folder for Adobe Media Encoder, or query the Windows registry at HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall for entries containing 'Adobe Media Encoder'
    Affected if Adobe Media Encoder is installed on the system
  2. Retrieve the installed version number
    Open Adobe Media Encoder and navigate to Help > About Adobe Media Encoder, or read the version from the Windows registry key HKEY_LOCAL_MACHINE\SOFTWARE\Adobe\Adobe Media Encoder\InstallVersion, or examine the file properties of the executable at C:\Program Files\Adobe\Adobe Media Encoder\15\Adobe Media Encoder.exe (path varies by version)
    Affected if The version displayed is 15.1 or earlier, or any version up to and including 15.4
  3. Assess SVG file import capability
    Attempt to import an SVG file through the application's media browser or File > Import menu to confirm the SVG parsing functionality is accessible
    Affected if The application allows importing SVG files as project assets or media sources

The environment is affected if Adobe Media Encoder version 15.4 or earlier is installed and users can import SVG files into the application.

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

Update Adobe Media Encoder to a version newer than 15.1. Until patched, instruct users not to open untrusted SVG files from unknown sources.

Recommended fix High confidence

Adobe Media Encoder 15.4.1 or later

  1. Open Adobe Creative Cloud desktop application or visit adobe.com/downloads
  2. Navigate to Adobe Media Encoder in your installed applications
  3. Check current version by going to Help > About Adobe Media Encoder
  4. Download and install Adobe Media Encoder version 15.4.1 or later
  5. Restart the application after installation
  6. Verify the installed version matches the fixed release

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
  • Implementation4.0 h
  • Testing2.0 h
  • Review / QA1.0 h
10.0 hours of engineering $1,800
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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