CVE-2026-27292
Use After Free in Adobe FrameMaker Allows Arbitrary Code Execution
Publication date: 2026-04-14
Last updated on: 2026-04-15
Assigner: Adobe Systems Incorporated
Description
Description
CVSS Scores
EPSS Scores
| Probability: | |
| Percentile: |
Meta Information
Affected Vendors & Products
| Vendor | Product | Version / Range |
|---|---|---|
| adobe | framemaker | to 2022.9 (exc) |
Helpful Resources
Exploitability
| CWE ID | Description |
|---|---|
| CWE-416 | The product reuses or references memory after it has been freed. At some point afterward, the memory may be allocated again and saved in another pointer, while the original pointer references a location somewhere within the new allocation. Any operations using the original pointer are no longer valid because the memory "belongs" to the code that operates on the new pointer. |
Attack-Flow Graph
AI Powered Q&A
Can you explain this vulnerability to me?
This vulnerability is a Use After Free issue in Adobe Framemaker versions 2022.8 and earlier. It occurs when the software improperly handles memory, allowing an attacker to execute arbitrary code within the context of the current user. To exploit this vulnerability, an attacker must trick a user into opening a malicious file.
How can this vulnerability impact me? :
If exploited, this vulnerability can allow an attacker to execute arbitrary code with the same privileges as the current user. This could lead to unauthorized actions such as installing programs, viewing, changing, or deleting data, or creating new accounts with full user rights. However, exploitation requires user interaction by opening a malicious file.
What immediate steps should I take to mitigate this vulnerability?
To mitigate this vulnerability, ensure that users do not open malicious files in Adobe Framemaker versions 2022.8 and earlier.
Consider updating Adobe Framemaker to a version later than 2022.8 once a patch is available.
Educate users about the risks of opening files from untrusted sources to reduce the chance of exploitation.
How does this vulnerability affect compliance with common standards and regulations (like GDPR, HIPAA)?:
This vulnerability allows arbitrary code execution in the context of the current user after opening a malicious file, which could lead to unauthorized access or data compromise.
Such unauthorized access or data compromise could potentially impact compliance with standards and regulations like GDPR or HIPAA, which require protection of sensitive data and user privacy.
However, specific impacts on compliance depend on the environment and data involved, and no explicit information about compliance effects is provided in the available data.