LiveActive security incident?Get immediate response
CVE Record

CVE-2021-40771: Adobe Prelude WAV 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 WAV 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

A malicious WAV audio file can corrupt memory in Adobe Prelude 10.1 and earlier. If a user opens the file, an attacker could run code with that user's permissions. This is a workstation-focused risk tied to media-handling workflows, not a remote network service exposure.

Executive priority

Treat as a high-priority endpoint remediation item for media teams. Business urgency is higher where staff routinely receive audio files from outside parties or where compromised user workstations could access sensitive content.

Technical view

CVE-2021-40771 is a CWE-788 memory corruption issue in Adobe Prelude WAV parsing. CVSS 3.0 is 7.8, with local attack vector, low complexity, no privileges required, and required user interaction. Successful exploitation may affect confidentiality, integrity, and availability as the current user.

Likely exposure

Organizations are exposed where Adobe Prelude 10.1 or earlier is installed, especially on systems that open externally supplied audio or project media. Exposure is likely limited to endpoints used for media production or review rather than servers.

Exploitation context

The source bundle does not show CISA KEV listing or any cited evidence of active exploitation. Exploitation requires persuading a user to open a specially crafted WAV file in the affected application.

Researcher notes

Evidence supports arbitrary code execution through malicious file parsing with required user interaction. The provided sources do not include exploit-in-the-wild evidence, weaponized samples, or detailed fixed-version data beyond the Adobe advisory reference.

Mitigation direction

  • Identify endpoints running Adobe Prelude 10.1 or earlier.
  • Review Adobe APSB21-96 and apply the vendor-recommended update or remediation.
  • Restrict users from opening untrusted WAV files in Prelude.
  • Limit Prelude use on systems handling sensitive data.
  • Remove Prelude where it is no longer required.

Validation and detection

  • Confirm installed Adobe Prelude versions across managed endpoints.
  • Verify remediation status against Adobe APSB21-96 guidance.
  • Check whether media teams receive WAV files from external sources.
  • Review endpoint alerts for Prelude crashes after opening media files.
  • Confirm users handling external media have current security awareness guidance.
Prepared
Confidence
medium
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-40771 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.0)
Known Exploited
No
Published

Vector: CVSS:3.0/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.0HighCVSS:3.0/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.0 score

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

Vector: CVSS:3.0/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.