# CVE-2021-40795: Adobe Premiere Pro 3GP File Parsing Out-Of-Bounds Read Remote Code Execution Vulnerability

> An out-of-bounds read in Adobe Premiere Pro allows remote code execution if a user opens a malicious 3GP file.

- **Severity:** High 7.8 (`CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Local or same network only
- **Victim action needed:** A user has to click or open something
- **Fix available:** No
- **Published:** 7 Sep 2023
- **Updated:** 27 Feb 2025
- **Also known as:** GHSA-w26v-9pmr-2p6c

## What is CVE-2021-40795?

CVE-2021-40795 is a high-severity memory corruption vulnerability in Adobe Premiere Pro, published on 7 Sep 2023. It can only be exploited from the same machine or local network, and only if a user opens a file or follows a link.

### Official description

Adobe Premiere Pro versions 22.0 (and earlier) and 15.4.2 (and earlier) are affected by an out-of-bounds read vulnerability which could result in a read past the end of an allocated memory structure. An attacker could leverage this vulnerability to execute code in the context of the current user. Exploitation of this issue requires user interaction in that a victim must open a malicious file.

Weakness: CWE-125 (Out-of-bounds Read)

## Which versions are affected by CVE-2021-40795?

It affects 1 product.


Products: Adobe Premiere Pro.

## How do I fix CVE-2021-40795?

No fix has been published for CVE-2021-40795 yet. Limit exposure of the affected software until one is available.

## Is CVE-2021-40795 being exploited?

There is no known exploitation of CVE-2021-40795 in the wild and no public exploit code.

## Other vulnerabilities in Adobe Premiere Pro

- [CVE-2026-48269](https://insights.sbomify.com/CVE-2026-48269/): Premiere Pro | Heap-based Buffer Overflow (CWE-122) (high 7.8)
- [CVE-2026-48270](https://insights.sbomify.com/CVE-2026-48270/): Premiere Pro | Out-of-bounds Write (CWE-787) (high 7.8)
- [CVE-2026-48369](https://insights.sbomify.com/CVE-2026-48369/): Premiere Pro | Out-of-bounds Write (CWE-787) (high 7.8)
- [CVE-2026-34636](https://insights.sbomify.com/CVE-2026-34636/): Premiere Pro | Out-of-bounds Write (CWE-787) (high 7.8)
- [CVE-2026-34637](https://insights.sbomify.com/CVE-2026-34637/): Premiere Pro | Out-of-bounds Write (CWE-787) (high 7.8)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2021-40795 and fix it if it is affected.

What it is: CVE-2021-40795 is a high-severity memory corruption vulnerability in Adobe Premiere Pro, published on 7 Sep 2023. It can only be exploited from the same machine or local network, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of CVE-2021-40795 in the wild and no public exploit code.

Affected product: Adobe Premiere Pro. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2021-40795/ (Markdown: https://insights.sbomify.com/CVE-2021-40795/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2021-40795
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2021-40795
- OSV: https://osv.dev/vulnerability/CVE-2021-40795

---
From sbomify Insights: https://insights.sbomify.com/CVE-2021-40795/
Summaries are generated and may contain mistakes; the official description above is the record.
