LiveActive security incident?Get immediate response
CVE Record

CVE-2021-40770: Adobe Prelude M4A File Parsing Memory Corruption Arbitrary Code Execution

Adobe Prelude version 10.1 (and earlier) is affected by a memory corruption vulnerability due to insecure handling of a malicious M4A file, potentially resulting in arbitrary code execution in the context of the current user. User interaction is required in that the victim must open a specially crafted file to exploit this vulnerability.

HighCVSS 7.8Not KEV-listedUpdated
Glexia's TakeAutomated analysishigh

Security readout for executives and security teams

Plain-English summary

Adobe Prelude 10.1 and earlier can be compromised if a user opens a malicious M4A audio file. Successful exploitation could let attacker-supplied code run with that user’s permissions, affecting confidentiality, integrity, and availability. The provided sources do not support claims of active exploitation.

Executive priority

Treat this as a targeted workstation risk rather than a broad internet-facing emergency. Prioritize creative, marketing, and media teams that use Adobe Prelude and handle external media. Remediation should be scheduled promptly where affected versions remain in use.

Technical view

CVE-2021-40770 is a memory corruption issue in Adobe Prelude’s M4A file handling, mapped to CWE-788. CVSS 3.1 is 7.8: local attack vector, low complexity, no privileges required, and user interaction required. Impact is arbitrary code execution in the current user context.

Likely exposure

Exposure is likely limited to endpoints or workstations running Adobe Prelude 10.1 or earlier, especially users who receive or process external audio or media files. Systems without Adobe Prelude are not indicated as affected by the provided sources.

Exploitation context

The attacker must convince a victim to open a specially crafted M4A file in Adobe Prelude. The source bundle lists no KEV status and provides no cited evidence of active exploitation or public weaponization.

Researcher notes

Key constraints are user interaction and current-user code execution. Validation should focus on asset inventory, version confirmation, file-handling workflows, and whether official Adobe guidance has been applied. Evidence is incomplete for exploit prevalence, patch details, and any product beyond Adobe Prelude.

Mitigation direction

  • Inventory Adobe Prelude installations and identify versions 10.1 or earlier.
  • Review Adobe APSB21-96 for the vendor’s current remediation guidance.
  • Apply Adobe-provided updates or mitigations referenced by official guidance.
  • Limit opening externally supplied M4A files on affected workstations.
  • Remove Adobe Prelude where it is no longer operationally required.

Validation and detection

  • Confirm whether Adobe Prelude is installed on media-production endpoints.
  • Record installed Prelude versions and compare them with the affected range.
  • Verify remediation status against Adobe APSB21-96, not informal version assumptions.
  • Review email, download, and EDR telemetry for suspicious M4A handling on affected hosts.
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-788: 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-40770 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-40770Attack 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
AdobePreludeunspecified, unspecifiedListed
Weakness

CWE details

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

CWE-788 · source CWE mapping

Access of Memory Location After End of Buffer

Access of Memory Location After End of Buffer represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.