CVE-2021-40787: Adobe Premiere Elements M4A file memory corruption vulnerability could lead to arbitrary code execution
Telemetry drift only. No threshold crossed and no authority ruling changed.
CVE record, CISA KEV and EPSS as of 2026-10-18.
CVEs like this one computed, by meaning
What to do now held facts and links
- Upgrade to premiere elements 2021.4 or later upper bounds of the CVE record's affected ranges
- Record your decision, dated and frozen with today's evidence: patch by a date · mitigated by a compensating control · deferred · accepted the risk · not affected
- Check your version against the ranges this record publishes.
What it is stated by the CNA
Adobe Premiere Elements 20210809.daily.2242976 (and earlier) is affected by a memory corruption vulnerability due to insecure handling of a malicious file, potentially resulting in arbitrary code execution in the context of the current user. User interaction is required to exploit this vulnerability.
- weakness
- CWE-788 Access of Memory Location After End of Buffer (CWE-788)
- affected
- Adobe Premiere Elements
- published ranges
- adobe premiere elements < 2021.4
- first unaffected version, by branch
- premiere elements 2021.4
- severity
- 7.8 CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H
- assigned by
- adobe
- published
- 2022-03-16
check us helpx.adobe.com
Exploit code held, dated
- exploit code
- None held in the PoC-in-GitHub feed. A public repository changes this brief.
What moved held, dated
| date | EPSS | event |
|---|---|---|
| 17 Mar 2022 | 0.01036 | |
| 23 Mar 2022 | 0.01223 | |
| 7 Mar 2023 | 0.0009 | scoring model v2023.03.01 |
| 8 Mar 2023 | 0.0009 | |
| 17 Mar 2025 | 0.00732 | scoring model v2025.03.14 |
| 29 Nov 2025 | 0.00881 | |
| 15 Jun 2026 | 0.0155 | scoring model v2026.06.15 |
| 15 Jul 2026 | 0.01588 | |
| 5 Aug 2026 | 0.0165 |
27 observations held. A step marked with a scoring model moved because the measurement was replaced, not because the vulnerability changed.
Outside the record researched, cited
This section reads the record's references and adds cited findings from outside it. It needs an account. Everything above is held facts and is complete without it.
What would change this brief held, dated
- CISA KEV
- Not listed in the catalogue we hold. A listing changes this brief.
- exploit probability
- 0.02 on 2026-08-05 (FIRST's EPSS, a probability and not evidence of exploitation). Next band line: 10% (0.10). Crossing a line changes this brief.
- fix
- Held: premiere elements 2021.4. A newer fix from the CNA or OSV changes this brief.
How to check this
Every value above is held with two dates: when it was true upstream (as_of) and when we recorded it (tx_from). Re-derive the exploit probability as it stood on any date:
SELECT value, source, source_version, as_of, tx_from
FROM volatile_valid_as_of('CVE-2021-40787', '2026-10-30T23:59:59.999999Z', now());