LiveActive security incident?Get immediate response
CVE Record

CVE-2021-46816: Adobe Premiere Pro M4A file memory corruption vulnerability could lead to remote code execution

Adobe Premiere Pro version 15.4 (and earlier) are affected by a memory corruption vulnerability. An unauthenticated attacker could leverage this vulnerability to achieve 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 M4A file.

HighCVSS 7.8Not KEV-listedUpdated
Glexia's TakeAutomated analysishigh

Security readout for executives and security teams

Plain-English summary

CVE-2021-46816 is a high-severity Adobe Premiere Pro flaw where opening a malicious M4A audio file could let an attacker run code as the logged-in user. It needs user interaction, so exposure is mainly users who import or review external media files in affected Premiere Pro versions.

Executive priority

Treat this as a prioritized workstation remediation issue for creative and media teams, especially where external audio or project assets are common. It is high impact, but requires user interaction and has no provided evidence of active exploitation.

Technical view

Adobe Premiere Pro 15.4 and earlier have a memory corruption issue classified as CWE-787. The CVSS 3.1 score is 7.8 with local attack vector and required user interaction. Successful exploitation could affect confidentiality, integrity, and availability in the current user context.

Likely exposure

Organizations are most exposed where Adobe Premiere Pro 15.4 or earlier is installed and users handle untrusted M4A files from clients, vendors, downloads, or shared media libraries.

Exploitation context

The provided sources do not show CISA KEV listing or active exploitation. Exploitation requires a victim to open a malicious M4A file, limiting mass exploitation but leaving targeted media-file delivery plausible.

Researcher notes

Focus validation on version exposure, media-file intake paths, and whether affected users run with elevated privileges. The bundle does not provide exploit telemetry, proof-of-concept status, or a named fixed version, so avoid assumptions beyond Adobe guidance.

Mitigation direction

  • Identify Adobe Premiere Pro 15.4 and earlier installations.
  • Apply Adobe APSB21-67 guidance for affected Premiere Pro systems.
  • Restrict opening unsolicited M4A files on affected workstations.
  • Use least-privilege user accounts for media production systems.
  • Prioritize endpoints handling external client or vendor media.

Validation and detection

  • Inventory Premiere Pro versions across managed endpoints.
  • Confirm affected systems are remediated according to Adobe APSB21-67.
  • Review security controls for handling external M4A files.
  • Check endpoint alerts involving suspicious media files and Premiere Pro.
  • Verify users handling external media received file-safety guidance.
Prepared
Confidence
high
Sources
3

Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.

Potential ATT&CK relevance

Conservative CVE-to-ATT&CK context

These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.

ATT&CK lookup starting points

Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.

cwe · low confidence lookup

CWE-787: Exact CWE lookup

Use the exact CWE identifier as the starting point before reviewing related ATT&CK behavior. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.

Open ATT&CK lookup
description · low confidence lookup

Execution behavior lookup

The CVE wording references code or command execution, so execution technique review may help defensive triage. This is a Glexia inferred lookup path, not an official MITRE, ATT&CK, or CVE Program mapping.

Open ATT&CK lookup
cve · low confidence lookup

CVE-2021-46816 mapping review

Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.

Open ATT&CK lookup
Vulnerability profileCVE Program record
Severity
High
CVSS
7.8 (3.1)
Known Exploited
No
Published

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

Official CVE source material

CNA and ADP enrichment extracted from CVE v5

These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.

1CVSS vectors
0Timeline events
0ADP providers
2Source links

CVSS vector scores

1 official score

We collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.

ScoreVersionSeverityVectorExploitImpactSource
7.8CVSS 3.1HighCVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H1.85.9Primary CVE score

Vulnerability scoring details

Base CVSS 3.1 score

7.8High
CVSS 3.1 vector shape for CVE-2021-46816Attack VectorAttack ComplexityPrivileges RequiredUser InteractionScopeConfidentiality ImpactIntegrity ImpactAvailability Impact

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

Attack Vector
NetworkAdjacentLocalPhysical
Attack Complexity
LowHigh
Privileges Required
NoneLowHigh
User Interaction
NoneRequired
Scope
ChangedUnchanged
Confidentiality Impact
HighLowNone
Integrity Impact
HighLowNone
Availability Impact
HighLowNone

Source materials

Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
AdobePremiereunspecified, unspecifiedListed
Weakness

CWE details

CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.

CWE-787 · source CWE mapping

Out-of-bounds Write

Out-of-bounds Write represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.