What is the CVSS score of EUVD-2026-22784?

EUVD-2026-22784 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 EUVD-2026-22784?

Adobe FrameMaker 2022.8 and earlier contains an out-of-bounds read vulnerability that allows attackers to execute arbitrary code when users open malicious files, potentially compromising document…

How to fix or mitigate EUVD-2026-22784?

Within 24 hours: Inventory all FrameMaker deployments and versions across the organization; notify users not to open files from untrusted sources and to report suspicious documents. Within 7 days: Review Adobe security bulletin APSB26-36 for interim guidance; evaluate whether document review processes can be restricted to trusted internal sources only. Within 30 days: Upgrade all FrameMaker installations to the latest patched version when Adobe releases a fix; monitor Adobe security advisories for patch availability.

Framemaker EUVD-2026-22784

| CVE-2026-27294 HIGH

Out-of-bounds Read (CWE-125)

2026-04-14 psirt@adobe.com

Buffer Overflow Information Disclosure 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-22784

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 read vulnerability when parsing a crafted file, which could result in a read past the end of an allocated memory structure. An attacker could leverage this vulnerability to execute code 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 read in Adobe FrameMaker 2022.8 and earlier enables arbitrary code execution when users open malicious crafted files. Exploitation requires local access and user interaction (CVSS 7.8, AV:L/UI:R), allowing attackers to execute code with current user privileges and achieve high confidentiality, integrity, and availability impact. EPSS data not available; no confirmed active exploitation (CISA KEV) or public exploit code identified at time of analysis. Adobe has released security bulletin APSB26-36 addressing this vulnerability.

Technical ContextAI

This vulnerability stems from improper bounds checking during file parsing operations in Adobe FrameMaker, a document processor for technical documentation and publishing. The CWE-125 classification indicates a classic out-of-bounds read flaw where the application reads data past the end of an allocated buffer when processing specially crafted input files. While categorized as an out-of-bounds read (typically associated with information disclosure), Adobe's advisory confirms this can be weaponized for code execution-likely through techniques such as leveraging the disclosed memory contents to bypass ASLR, chain with other vulnerabilities, or trigger further memory corruption. The vulnerability affects Adobe FrameMaker versions 2022.8 and all prior releases, indicating a potentially long-standing code defect in the file parsing engine that handles proprietary or complex document formats.

RemediationAI

Organizations should immediately apply the security updates detailed in Adobe Security Bulletin APSB26-36 available at https://helpx.adobe.com/security/products/framemaker/apsb26-36.html. The vendor advisory specifies patched versions that address CVE-2026-27294 along with installation procedures for enterprise deployments. Until patches can be deployed, implement defense-in-depth controls including restricting FrameMaker file-opening privileges to trusted document sources only, enabling application-level sandboxing or virtualization where supported, deploying endpoint detection and response solutions configured to monitor FrameMaker process behavior for anomalies, and conducting user security awareness training emphasizing the risks of opening unsolicited FrameMaker documents from unknown senders. For high-security environments, consider temporarily restricting FrameMaker usage to air-gapped systems or disabling the application until patches are verified and deployed.