Security readout for executives and security teams
Plain-English summary
This is a low-severity information disclosure flaw in Adobe Prelude. An attacker would need to convince a user to open a malicious MP4 file. Successful exploitation could expose memory information from the current user's context, not alter files or take over systems based on the supplied CVSS.
Executive priority
Handle through normal patch and software hygiene cycles unless Prelude is widely used for external media intake.
Technical view
Adobe Prelude 10.0 and earlier are affected by an uninitialized variable vulnerability during specially crafted file parsing. The supplied CVSS 3.1 score is 3.3 with local attack vector, required user interaction, low confidentiality impact, and no integrity or availability impact.
Likely exposure
Exposure is limited to environments where Adobe Prelude 10.0 or earlier is installed and users open untrusted MP4 or media files.
Exploitation context
The bundle does not show KEV listing or active exploitation. Exploitation requires user interaction: a victim must open a malicious file.
Researcher notes
Evidence supports a user-assisted local information disclosure issue only. The source bundle does not provide exploit details, observed exploitation, or a named fixed version.
Mitigation direction
- Inventory endpoints for Adobe Prelude 10.0 or earlier.
- Review Adobe APSB21-58 for vendor update guidance.
- Update or remove affected Prelude installations where possible.
- Limit opening unsolicited or untrusted MP4/media files.
- Use endpoint controls to reduce delivery of suspicious media attachments.
Validation and detection
- Confirm installed Adobe Prelude versions across managed endpoints.
- Check whether Adobe APSB21-58 guidance has been applied.
- Review file-association and workflow exposure for MP4 handling.
- Verify users handling external media receive appropriate cautionary guidance.
Public sources used
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
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-20: 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 lookupCVE-2021-36007 mapping review
Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.
Open ATT&CK lookup- Severity
- Low
- CVSS
- 3.3 (3.1)
- Known Exploited
- No
- Published
Vector: CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:L/I:N/A:N
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.
CVSS vector scores
1 official scoreWe 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.
CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:L/I:N/A:N1.81.4Primary CVE scoreVulnerability scoring details
Base CVSS 3.1 score
3.3LowVector: CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:L/I:N/A:N
Source materials
- CVE List V5 sourceCVE List V5
- https://helpx.adobe.com/security/products/prelude/apsb21-58.htmlCVE reference · x_refsource_MISC
Products and packages named in the record
CWE details
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.
Improper Input Validation
Improper Input Validation represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.