LiveActive security incident?Get immediate response
CVE Record

CVE-2021-35999: Adobe Prelude Memory Corruption Remote Code Execution Vulnerability

Adobe Prelude version 10.0 (and earlier) is affected by a memory corruption vulnerability when parsing a specially crafted file. 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 file.

HighCVSS 7.8Not KEV-listedUpdated
Glexia's TakeAutomated analysishigh

Security readout for executives and security teams

Plain-English summary

Adobe Prelude 10.0 and earlier can be compromised if a user opens a maliciously crafted file. Successful exploitation could run attacker-controlled code with that user's privileges, risking data theft, tampering, or disruption on affected workstations.

Executive priority

Treat as high priority for creative or media teams using Adobe Prelude. The business risk depends on installed footprint and exposure to untrusted files, not internet-facing reachability.

Technical view

CVE-2021-35999 is a CWE-788 memory corruption issue in Adobe Prelude file parsing. CVSS 3.1 is 7.8 with local attack vector, low complexity, no privileges required, and user interaction required. Impact is high for confidentiality, integrity, and availability.

Likely exposure

Exposure is limited to systems with Adobe Prelude 10.0 or earlier installed, particularly users who open files from external or untrusted sources. This is not described as a remotely reachable network service issue.

Exploitation context

An unauthenticated attacker must persuade a victim to open a malicious file. The source bundle does not show CISA KEV listing or other cited evidence of active exploitation.

Researcher notes

Key evidence supports memory corruption during crafted file parsing, arbitrary code execution as the current user, and required user interaction. The bundle does not include exploit details, patch version details, or active exploitation evidence.

Mitigation direction

  • Review Adobe APSB21-58 for the vendor-provided remediation.
  • Update or remove Adobe Prelude 10.0 and earlier where affected.
  • Limit opening Prelude files from untrusted or unexpected sources.
  • Use least-privilege user accounts on creative workstations.
  • Prioritize controls for users handling external media files.

Validation and detection

  • Inventory endpoints for Adobe Prelude installations and versions.
  • Identify systems running Adobe Prelude 10.0 or earlier.
  • Confirm Adobe APSB21-58 remediation status for affected hosts.
  • Review security telemetry for suspicious activity after file opens.
  • Validate user workflows for untrusted file handling.
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-35999 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-35999Attack 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.