What is the CVSS score of CVE-2026-27295?

CVE-2026-27295 has a CVSS 3.1 base score of 7.8 (High). CVSS vector: CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H. EPSS exploitation probability: 0.0%.

Which versions of Framemaker are affected by CVE-2026-27295?

Adobe FrameMaker 2022.8 and earlier contain an out-of-bounds write vulnerability that allows arbitrary code execution when users open malicious files, posing a significant risk to organizations where…

How to fix or mitigate CVE-2026-27295?

Within 24 hours: Issue security alert to all FrameMaker 2022.8 and earlier users warning against opening files from untrusted sources; implement email filtering rules to block suspicious attachments with FrameMaker-associated file types (.fm, .book). Within 7 days: Inventory all FrameMaker installations and versions across the organization; restrict FrameMaker use to a limited group of trusted administrators where possible, or disable it on high-risk endpoints. Within 30 days: Monitor Adobe security advisories for patch availability; prepare and test upgrade path to FrameMaker 2023.0 or later (or latest available version once patched); execute patch deployment upon vendor release.

Framemaker CVE-2026-27295

EUVD-2026-22786 HIGH

Out-of-bounds Write (CWE-787)

2026-04-14 psirt@adobe.com

GHSA-573h-4gmm-4r9w

RCE Buffer Overflow Memory Corruption Adobe Framemaker

7.8

CVSS 3.1 · Vendor: adobe

Severity by source

Vendor (adobe) PRIMARY

7.8 HIGH

AV:L/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H

Primary rating from Vendor (adobe) · only source for this CVE.

CVSS VectorVendor: adobe

Attack Vector

Local

Attack Complexity

Low

Privileges Required

None

User Interaction

Required

Scope

Unchanged

Confidentiality

High

Integrity

High

Availability

High

Lifecycle Timeline

Analysis Generated

Apr 15, 2026 - 01:10 vuln.today

EUVD ID Assigned

Apr 14, 2026 - 23:22 euvd

EUVD-2026-22786

Analysis Generated

Apr 14, 2026 - 23:22 vuln.today

CVE Published

Apr 14, 2026 - 23:16 nvd

HIGH 7.8

DescriptionCVE.org

Adobe Framemaker versions 2022.8 and earlier are 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.

AnalysisAI

Out-of-bounds write in Adobe FrameMaker 2022.8 and earlier enables arbitrary code execution when users open specially crafted malicious files. The vulnerability achieves full confidentiality, integrity, and availability impact (CVSS 7.8 HIGH) but requires local access and user interaction, limiting immediate risk. No public exploit identified at time of analysis, and exploitation requires social engineering to deliver the malicious file to victims.

Technical ContextAI

This vulnerability stems from CWE-787 (Out-of-Bounds Write), a memory corruption class where the application writes data beyond allocated buffer boundaries. Adobe FrameMaker, a desktop publishing and document processing application used for technical documentation, fails to properly validate input when parsing specially formatted files. The out-of-bounds write occurs during file processing operations, allowing attackers to overwrite adjacent memory regions. When successfully exploited, this memory corruption enables hijacking of program execution flow, resulting in arbitrary code execution with the privileges of the current user. The local attack vector (AV:L) indicates the malicious file must be delivered and opened on the victim's system, typically through email attachments, file shares, or social engineering channels.

RemediationAI

Adobe has released security updates addressing this vulnerability in Adobe Security Bulletin APSB26-36. Users should immediately update to the patched version specified in the vendor advisory at https://helpx.adobe.com/security/products/framemaker/apsb26-36.html. Organizations should deploy updates through existing software distribution mechanisms and verify successful installation across all FrameMaker deployments. As interim mitigation until patching is complete, implement strict controls on opening FrameMaker files from untrusted sources, enforce email attachment filtering policies to block suspicious file types, and educate users on the risks of opening unsolicited documents. Disable FrameMaker file associations in environments where the application is installed but not actively required.