LiveActive security incident?Get immediate response
CVE Record

CVE-2021-42738: Adobe Prelude MXF 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 MXF 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 when a user opens a malicious MXF media file. Successful exploitation could run code with that user’s permissions, making creative workstations and media-ingest workflows the main concern. The source bundle does not show active exploitation.

Executive priority

Treat this as a targeted workstation risk, not an internet-exposed server emergency. Prioritize teams that ingest third-party media files and ensure affected Prelude installations follow Adobe guidance.

Technical view

CVE-2021-42738 is a CWE-788 memory corruption flaw in Adobe Prelude’s MXF file parsing. The CVSS 3.1 score is 7.8: local attack vector, low complexity, no privileges, user interaction required, and high confidentiality, integrity, and availability impact.

Likely exposure

Exposure is most likely on endpoints running Adobe Prelude 10.1 or earlier, especially systems that open MXF files from clients, partners, archives, or shared media storage.

Exploitation context

Exploitation requires a victim to open a specially crafted MXF file. The provided KEV status is false, and no cited source in the bundle confirms exploitation in the wild.

Researcher notes

The bundle supports arbitrary code execution in the current user context through malicious MXF parsing. It does not include exploit proof, fixed-version details, or telemetry confirming active exploitation, so avoid claiming more than the CVE and Adobe advisory establish.

Mitigation direction

  • Inventory Adobe Prelude installations and identify versions 10.1 or earlier.
  • Check Adobe APSB21-96 for the supported fixed version or vendor-directed action.
  • Restrict opening MXF files from untrusted or unexpected sources.
  • Use least-privilege user accounts on media workstations.
  • Prioritize controls around email, file-sharing, and media-ingest paths.

Validation and detection

  • Confirm installed Adobe Prelude versions on creative and media-handling endpoints.
  • Review whether users handle external MXF files in normal workflows.
  • Check endpoint telemetry for suspicious Prelude crashes or child processes.
  • Verify Adobe guidance has been applied where affected versions exist.
  • Document any systems that cannot be updated and compensating controls used.
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-42738 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-42738Attack 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.