ADOBE MEDIA ENCODER · CVE-2026-113541 · Other
FIX → 27.0 · 26.5.3 ✓ verified
Adobe Media Encoder has an out-of-bounds write flaw that lets a crafted file write past a memory buffer. An attacker who gets a victim to open that file can run code as the current user.
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 on Windows or macOS at 26.5.2 or earlier, or 25.6.6 or earlier. The flaw is an out-of-bounds write triggered when a user opens a crafted file, giving code execution as that user. Video/creative teams and shared render machines that open files from outside sources matter most; machines without Media Encoder can skip it.
Not affected if no-untrusted-media-files
Who cares adobe-media-encoder, creative-cloud, macos, user-interaction, windows
26.5.2 and earlier, and 25.6.6 and earlier26.5.3 or 27.0Media 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
Update Adobe Media Encoder to 27.0, or to 26.5.3 on the 26.x line (25.6.6 and earlier is affected; move to 26.5.3 or 27.0), via Creative Cloud app / Download Center