{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2021-46816 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2021-46816 yet. Limit exposure of the affected software until one is available.","what":"CVE-2021-46816 is a high-severity memory corruption vulnerability in Adobe Premiere, published on 13 Jun 2022. It can only be exploited from the same machine or local network, and only if a user opens a file or follows a link."},"fix_prompt":"Check this codebase for CVE-2021-46816 and fix it if it is affected.\n\nWhat it is: CVE-2021-46816 is a high-severity memory corruption vulnerability in Adobe Premiere, published on 13 Jun 2022. It can only be exploited from the same machine or local network, and only if a user opens a file or follows a link.\nExploitation: There is no known exploitation of CVE-2021-46816 in the wild and no public exploit code.\n\nAffected product: Adobe Premiere. No package-level version data is available, so check the vendor advisory linked from the reference page.\n\nTask:\n1. 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.\n2. 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.\n3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.\n4. Run the tests and summarise what changed and why.\n5. If nothing in the project is affected, say so and change nothing.\n\nReference: https://insights.sbomify.com/CVE-2021-46816/ (Markdown: https://insights.sbomify.com/CVE-2021-46816/index.md)","id":"CVE-2021-46816","markdown":"https://insights.sbomify.com/CVE-2021-46816/index.md","name":"CVE-2021-46816","record":{"aliases":["GHSA-839r-958m-2c8x"],"analysis":{"component_type":"desktop_application","fix_type":"patch","impacts":["code_execution"],"network_reachable":"adjacent_or_local","non_default_config":false,"product_category":"Video editing software","requires_auth":"none","summary":"An attacker can achieve arbitrary code execution by tricking a user into opening a malicious M4A file in Adobe Premiere Pro.","user_interaction":"required","vuln_class":"memory_corruption"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"adobe","cpe":[{"product":"premiere_pro","vendor":"adobe"}],"cvss":{"score":7.8,"severity":"high","source":"cna","vector":"CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H","version":"3.1"},"cwes":[{"id":"CWE-787","name":"Out-of-bounds Write"}],"description":"Adobe Premiere Pro version 15.4 (and earlier) are affected by a memory corruption vulnerability. 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 M4A file.","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"none_known"},"has_fix":null,"headline":"Adobe Premiere Pro M4A file memory corruption vulnerability could lead to remote code execution","id":"CVE-2021-46816","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"memory_corruption","year":"2021"},"n_packages":0,"n_references":1,"next":{"headline":"Adobe Media Encoder M4A file memory corruption vulnerability could lead to remote code execution","id":"CVE-2021-46817"},"packages":[],"prev":{"headline":"Memory corruption in EMUI","id":"CVE-2021-46814"},"products":["Premiere"],"published":"2022-06-13","related":[{"cvss_score":7.8,"headline":"Premiere Pro | Heap-based Buffer Overflow (CWE-122)","id":"CVE-2026-48269","kev_date_added":null,"published":"2026-07-14"},{"cvss_score":7.8,"headline":"Premiere Pro | Out-of-bounds Write (CWE-787)","id":"CVE-2026-48270","kev_date_added":null,"published":"2026-07-14"},{"cvss_score":7.8,"headline":"Premiere Pro | Out-of-bounds Write (CWE-787)","id":"CVE-2026-48369","kev_date_added":null,"published":"2026-07-14"},{"cvss_score":7.8,"headline":"Premiere Pro | Out-of-bounds Write (CWE-787)","id":"CVE-2026-34636","kev_date_added":null,"published":"2026-05-12"},{"cvss_score":7.8,"headline":"Premiere Pro | Out-of-bounds Write (CWE-787)","id":"CVE-2026-34637","kev_date_added":null,"published":"2026-05-12"},{"cvss_score":7.8,"headline":"Premiere Pro | Use After Free (CWE-416)","id":"CVE-2026-34638","kev_date_added":null,"published":"2026-05-12"},{"cvss_score":7.8,"headline":"Premiere Pro | Out-of-bounds Read (CWE-125)","id":"CVE-2026-27269","kev_date_added":null,"published":"2026-03-10"}],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"class":"attribution","licence":"US public information, NVD API terms","name":"NVD"},{"class":"attribution","licence":"CWE Terms of Use","name":"CWE (MITRE)"},{"class":"attribution","licence":"FIRST CVSS licence","name":"CVSS (FIRST)"}],"ssvc":{"automatable":"no","exploitation":"none","technical_impact":"total"},"state":"PUBLISHED","updated":"2025-04-23","vendors":["Adobe"]},"summary":"An attacker can achieve arbitrary code execution by tricking a user into opening a malicious M4A file in Adobe Premiere Pro.","url":"https://insights.sbomify.com/CVE-2021-46816/"}