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

CVE-2026-27298 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-27298?

Adobe FrameMaker 2022.8 and earlier contains a type confusion vulnerability enabling arbitrary code execution when users open maliciously crafted documents, compromising confidentiality, integrity,…

How to fix or mitigate CVE-2026-27298?

Within 24 hours: Identify all FrameMaker 2022.8 and earlier installations via asset inventory and communicate security advisory to affected users prohibiting opening documents from untrusted sources. Within 7 days: Restrict FrameMaker file handling through endpoint controls (e.g., disable automatic file opening, require manual user confirmation); implement network monitoring for suspicious FrameMaker process behavior. Within 30 days: Upgrade to FrameMaker 2023.x or later (current patched version) or prepare alternative document workflow using validated third-party tools; validate upgrade compatibility with existing document repositories before full deployment.

Framemaker CVE-2026-27298

EUVD-2026-22792 HIGH

Access of Resource Using Incompatible Type (Type Confusion) (CWE-843)

2026-04-14 psirt@adobe.com

RCE 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:11 vuln.today

EUVD ID Assigned

Apr 14, 2026 - 23:22 euvd

EUVD-2026-22792

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 Access of Resource Using Incompatible Type ('Type Confusion') 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

Arbitrary code execution in Adobe FrameMaker 2022.8 and earlier allows local attackers to execute code with current user privileges via maliciously crafted files. The type confusion vulnerability (CWE-843) requires user interaction to open a weaponized document. CVSS 7.8 (High) reflects significant impact (full confidentiality, integrity, availability compromise) once exploitation succeeds. No public exploit identified at time of analysis, though the local attack vector and user interaction requirement reduce immediate remote exploitation risk.

Technical ContextAI

This vulnerability stems from a type confusion error (CWE-843), a memory corruption class where the application accesses a resource using an incompatible type pointer or reference. In FrameMaker's document parsing engine, improper type validation allows attackers to craft files that cause the application to misinterpret object types in memory. When FrameMaker processes the malicious file, this type confusion can corrupt memory structures, enabling control of execution flow. Type confusion vulnerabilities are common in complex document processors handling multiple file formats (MIF, BOOK, XML) and often occur during deserialization or object instantiation. Adobe FrameMaker is a desktop publishing application for technical documentation, making it a target for social engineering attacks in enterprise environments where users regularly exchange document files.

RemediationAI

Apply the vendor-released patch detailed in Adobe Security Bulletin APSB26-36 available at https://helpx.adobe.com/security/products/framemaker/apsb26-36.html. Adobe typically releases fixed versions through their Creative Cloud update mechanism or direct downloads for enterprise licensees. Upgrade to the patched version specified in APSB26-36 immediately for systems in high-risk environments. As a temporary mitigation until patching, restrict opening FrameMaker files to trusted sources only, implement email attachment filtering to block unexpected .fm, .book, and .mif files, and consider application sandboxing or virtualization to limit code execution impact. Educate users on social engineering risks associated with unsolicited technical documents. For enterprise deployments, prioritize patching systems used by engineers, technical writers, and documentation teams who regularly receive external files.