User-context code execution via out-of-bounds write
Published Apr 8, 2025 · Updated Feb 26, 2026
Out-of-bounds write in Adobe Media Encoder 25.1 and earlier and 24.6.4 and earlier allows local users to execute code via a malicious file. Adobe identifies the write as occurring during malicious-file processing but does not disclose the affected parser, file format, function, or bounds-checking failure. Exploitation requires a user to open the file, after which attacker-controlled code runs with that user's privileges.
Summary
What happened
Out-of-bounds write in Adobe Media Encoder 25.1 and earlier and 24.6.4 and earlier allows local users to execute code via a malicious file. Adobe identifies the write as occurring during malicious-file processing but does not disclose the affected parser, file format, function, or bounds-checking failure. Exploitation requires a user to open the file, after which attacker-controlled code runs with that user's privileges.
The record
- CVE
- CVE-2025-27194
- Published
- Apr 8, 2025
- Updated
- Feb 26, 2026
- Vendor
- Adobe
- Product
- Adobe Media Encoder
- Classifications
- CWE-787, T1204.002
- Attack vector
- local
- Privileges
- unauthenticated
Timeline
How it unfolded
- Apr 8, 2025CVE publishedPublication date reported by the CVE source.
- Feb 26, 2026Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=0 <=24.6.4
What conditions does exploitation require?
What is affected?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo