Adobe Framemaker versions 2022.8 and earlier are affected by an Untrusted Search Path vulnerability that might allow attackers to execute arbitrary code in the context of the current user. If the application uses a search path to locate critical resources such as programs, then an attacker could modify that search path to point to a malicious program, which the targeted application would then execute. Exploitation of this issue does not require user interaction.
Security readout for executives and security teams
Plain-English summary
Adobe FrameMaker 2022.8 and earlier can be induced to run a malicious program instead of a trusted resource because it may search an attacker-influenced location. Successful exploitation could compromise the current user’s data and system access. The supplied evidence contains conflicting user-interaction claims, so exploitation prerequisites require confirmation.
Executive priority
Treat this as a high-priority endpoint remediation issue, especially where FrameMaker users access sensitive information or possess elevated rights. There is no supplied evidence of active exploitation, but potential code execution and high impact justify prompt inventory and vendor-guided remediation rather than emergency incident declarations.
Technical view
CVE-2026-27290 is a CWE-426 untrusted search path flaw with CVSS 3.1 score 8.6. An attacker may redirect FrameMaker’s resource lookup toward a malicious program, causing code execution as the current user. The vector indicates local access, low complexity, no privileges, user interaction, changed scope, and high confidentiality, integrity, and availability impact.
Likely exposure
Exposure is limited to systems running Adobe FrameMaker 2022.8 or earlier. Impact depends on the permissions of the user running FrameMaker. The supplied sources do not establish how commonly vulnerable search-path conditions occur or whether particular operating systems or configurations are more exposed.
Exploitation context
The bundle marks this CVE as absent from KEV and provides no evidence of active exploitation. It says exploitation requires no user interaction, while the CVSS vector specifies UI:R. Treat the exact interaction requirement as unresolved until Adobe’s advisory clarifies it. Local attack-vector requirements reduce remote reach but not post-exploitation impact.
Researcher notes
The principal evidence gap is the contradiction between the narrative’s no-interaction statement and CVSS UI:R. The normalized affected entry is also less explicit than the description, which identifies 2022.8 and earlier. Researchers should preserve these distinctions and avoid asserting remote exploitation, active exploitation, a confirmed fixed version, or exact triggering conditions without additional Adobe evidence.
Mitigation direction
Inventory Adobe FrameMaker installations and identify versions 2022.8 or earlier.
Review Adobe advisory APSB26-36 for the approved fixed release or mitigation.
Apply Adobe’s prescribed remediation according to organizational change controls.
Prioritize systems where FrameMaker users hold elevated or sensitive access.
Validation and detection
Record the installed FrameMaker version on every identified endpoint.
Confirm remediated versions against Adobe advisory APSB26-36.
Verify no FrameMaker 2022.8-or-earlier installations remain in managed inventory.
Monitor Adobe and CVE records for clarified prerequisites or exploitation evidence.
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-426: 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-426 · source CWE mapping
Untrusted Search Path
Untrusted Search Path represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.