Current-user code execution via out-of-bounds write
Published Jul 8, 2025 · Updated Feb 26, 2026
Out-of-bounds write in Adobe FrameMaker 2020.8 and 2022.6 and earlier allows context-dependent attackers to execute code via a malicious file. Adobe identifies neither the affected parser nor the file format; public material states only that processing attacker-controlled file data writes outside an allocated boundary. A victim must open the file, after which successful exploitation runs code with the victim's current-user privileges.
Summary
What happened
Out-of-bounds write in Adobe FrameMaker 2020.8 and 2022.6 and earlier allows context-dependent attackers to execute code via a malicious file. Adobe identifies neither the affected parser nor the file format; public material states only that processing attacker-controlled file data writes outside an allocated boundary. A victim must open the file, after which successful exploitation runs code with the victim's current-user privileges.
The record
- CVE
- CVE-2025-47124
- Published
- Jul 8, 2025
- Updated
- Feb 26, 2026
- Vendor
- Adobe
- Product
- Adobe FrameMaker
- Classifications
- CWE-787, T1204.002, T1203
- Attack vector
- local
- Privileges
- unauthenticated
Timeline
How it unfolded
- Jul 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 <=2022.6
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.
Weakness, pattern, technique
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