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.
Security readout for executives and security teams
Plain-English summary
A malicious document opened in Adobe FrameMaker could corrupt memory and run attacker-controlled code with the victim’s permissions. This could expose or alter data and disrupt the workstation. The supplied description identifies FrameMaker 2022.8 and earlier as affected and requires the user to open a malicious file.
Executive priority
Prioritize remediation for teams that routinely exchange FrameMaker documents externally. Treat affected authoring workstations as high priority because successful exploitation can compromise business data under the user’s access. Broad emergency measures are not supported by the supplied evidence, but prompt vendor-guided updating is warranted.
Technical view
CVE-2026-27295 is a CWE-787 out-of-bounds write in Adobe FrameMaker. It may permit arbitrary code execution as the current user. CVSS 3.1 is 7.8: local attack vector, low complexity, no privileges required, user interaction required, unchanged scope, and high confidentiality, integrity, and availability impact.
Likely exposure
Exposure is concentrated on endpoints running FrameMaker 2022.8 or earlier, particularly where users receive or open FrameMaker files from external or untrusted sources. The supplied structured version metadata is ambiguous, so inventories should be checked against Adobe’s advisory before final scoping.
Exploitation context
Exploitation requires convincing a victim to open a malicious file. The bundle does not identify CVE-2026-27295 as a CISA KEV entry, and no supplied source supports active exploitation. Absence from KEV does not prove that exploitation has never occurred.
Researcher notes
The core vulnerability, impact, interaction requirement, and CVSS data are clear. However, the structured affected entry lists versions “0” and “2022.9” with a default unaffected status, while the description says 2022.8 and earlier. Confirm exact version boundaries and fixed releases in Adobe APSB26-36; the bundle supplies no technical root-cause details or exploit evidence.
Mitigation direction
Identify installations of FrameMaker 2022.8 and earlier.
Review Adobe advisory APSB26-36 for the vendor-approved fixed version.
Apply Adobe’s documented update through normal endpoint-management controls.
Restrict opening unsolicited FrameMaker files until remediation is complete.
Use least-privileged user accounts to limit code-execution impact.
Validation and detection
Inventory FrameMaker versions across managed endpoints.
Confirm installed versions against Adobe advisory APSB26-36.
Verify the vendor-approved update completed successfully on each endpoint.
Review endpoint telemetry for suspicious activity following FrameMaker file opens.
Test controls preventing users from opening untrusted FrameMaker files.
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Potential ATT&CK relevance
Conservative CVE-to-ATT&CK context
These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.
ATT&CK lookup starting points
Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.
cwe · low confidence lookup
CWE-787: Exact CWE lookup
Use the exact CWE identifier as the starting point before reviewing related ATT&CK behavior. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.
The CVE wording references code or command execution, so execution technique review may help defensive triage. This is a Glexia inferred lookup path, not an official MITRE, ATT&CK, or CVE Program mapping.
These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.
1CVSS vectors
3Timeline events
1ADP providers
2Source links
SSVC decision data
CISA-ADPCISA Coordinator
Timestamp
Version
2.0.3
Exploitation: noneAutomatable: noTechnical Impact: total
CVSS vector scores
1 official score
We collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.
CWE-787 · source CWE mapping
Out-of-bounds Write
Out-of-bounds Write represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.