ADOBE MEDIA ENCODER · CVE-2026-113543 · Other
FIX → 27.0 · 26.5.3 ✓ verified
Adobe Media Encoder has an out-of-bounds write (CWE-787) that a crafted file can trigger, giving code execution as the current user. The victim has to open the malicious file. Adobe fixed it in APSB26-103 and is not aware of exploitation.
first public Nov 10, 2026 · 2 sources
Could this affect your app?
Free first check from your website. Connect your repo for the full answer.
Anyone running Adobe Media Encoder 26.5.2 or earlier, or 25.6.6 or earlier, on Windows or macOS is affected. An attacker needs the user to open a malicious file, so workstations that ingest media from outside (editors, agencies, shared drives) matter most. Systems without Media Encoder installed, or already on 26.5.3 or 27.0, can skip it.
Not affected if file-not-opened, updated-to-26.5.3-or-27.0
Who cares adobe-media-encoder, creative-cloud, desktop, macos, windows
26.5.2 and earlier, and 25.6.6 and earlier, on Windows and macOSMedia Encoder is affected by an out-of-bounds write vulnerability that could result in 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.
This page as .md · .json · CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H
NVD data is provided by NIST and is public domain. Posts quoted belong to their authors.
Check it with your coding agent
It reads this page and tells you if your code is affected.
Are you affected?
Ask from here. InfraStack checks the affected versions against your stack and answers in your inbox.
InfraStack checks the affected versions against your stack and answers in Slack, with the evidence and the fix.
Upgrade to 27.0 · 26.5.3
26.5.2 or earlier) or to 26.5.3 (on the 26.x line); 25.6.6 and earlier is also listed as affected, move to 26.5.3 or 27.0