FramemakerApplication · Adobe

CVE-2026-27293

HIGH · 7.8 CVSS v3.1 Published 2026-04-14
Fix available
A fix is available. Upgrade to 2022.9 or later.
See remediation →
81/100
Remediation priority · High
No privileges

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
Adobe Framemaker versions 2022.8 and earlier are affected by a Heap-based Buffer Overflow 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.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

Adobe Framemaker versions 2022.8 and earlier contain a heap-based buffer overflow vulnerability that can be triggered when a user opens a specially crafted malicious file, leading to arbitrary code execution in the context of the current user's privileges.

MitigationUpgrade Adobe Framemaker to a version newer than 2022.8. Until patched, avoid opening untrusted or unexpected Framemaker documents (.fm, .book, .mif files).

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
FramemakerApplication
Affected:< 2022.9

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Local
Complexity
Low
Privileges
None
User interaction
Required
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

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

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Check installed Adobe Framemaker version
    Open Adobe Framemaker, then go to Help > About Adobe Framemaker to view the exact version number displayed in the dialog box
    Affected if The displayed version is 2022.8 or earlier, or any version less than 2022.9
  2. Verify version via system installed programs
    On Windows, open Control Panel > Programs and Features (or Settings > Apps > Apps & features), locate Adobe Framemaker in the installed programs list, and note the version column entry
    Affected if The listed version is earlier than 2022.9 (for example, 2022.8, 2022.7, 2022.6, etc.)
  3. Confirm vulnerability requires file opening
    Recall or audit recent file opens of .framemaker, .fm, or related document files from untrusted or unknown sources, as this CVE triggers only when a specially crafted malicious file is opened
    Affected if A suspicious or untrusted .framemaker/.fm file was recently opened on the system

You are affected if Adobe Framemaker version is earlier than 2022.9 (i.e., 2022.8 or earlier), and a malicious crafted file was or could be opened.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Upgrade available Upgrade to 2022.9 or later
Fixed in 2022.9
Interim mitigation

Upgrade Adobe Framemaker to a version newer than 2022.8. Until patched, avoid opening untrusted or unexpected Framemaker documents (.fm, .book, .mif files).

Recommended fix High confidence

Adobe Framemaker 2022.9 or later

  1. Verify current Adobe Framemaker version by navigating to Help > About Adobe Framemaker
  2. Close any running instances of Adobe Framemaker
  3. Download Adobe Framemaker 2022.9 or later from the official Adobe website (helpx.adobe.com) or through the Creative Cloud desktop application
  4. Run the installer with administrative privileges
  5. Follow the on-screen installation prompts to complete the upgrade
  6. Restart the system if prompted
  7. Verify the upgrade was successful by checking Help > About Adobe Framemaker shows version 2022.9 or later
  8. Ensure users are warned not to open untrusted files, as exploitation requires user interaction (opening a malicious file)
Caveat Standard upgrade considerations apply - backup important documents before upgrading; some legacy document formats or plugins may require revalidation

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Framemaker Scoped from the published advisory
  • Consultation2.0 h
  • Implementation1.0 h
  • Testing1.0 h
  • Review / QA1.0 h
5.0 hours of engineering $910
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,456.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-27293 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2026-27293 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data