CVE-2026-27294
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 · uneditedAdobe 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.
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 confidenceAdobe Framemaker versions 2022.8 and earlier contain an out-of-bounds read vulnerability in the file parsing logic. When parsing a specially crafted malicious file, the software reads past the end of an allocated memory structure, which can be leveraged by an attacker to achieve code execution in the context of the current user.
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< 2022.9CVSS 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 checksWork through these to decide whether this CVE applies to you.
-
Detect Adobe Framemaker installationSearch for Adobe Framemaker in installed programs via Windows Registry (HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall\) or check Program Files for Framemaker folderAffected if Adobe Framemaker is found on the system
-
Identify installed Framemaker versionRun 'frank -version' from the Framemaker installation directory, or right-click the Framemaker executable and view Properties > Details for the Product VersionAffected if Version returned is 2022.8 or earlier (any version below 2022.9)
-
Verify file parsing is accessibleConfirm the Framemaker application can open document files (.fm, .mif, .xml) - the vulnerability triggers during parsing of specially crafted filesAffected if Framemaker is installed and can be used to open document files
User is affected if Adobe Framemaker version 2022.8 or earlier is installed and can be used to open document files, since the out-of-bounds read vulnerability exists in the file parsing logic for these versions.
Generated from the published advisory. Verify against your own configuration.
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 · scoped2022.9
Users should avoid opening untrusted or unsolicited files in Adobe Framemaker. Organizations should update to a patched version of Adobe Framemaker beyond 2022.8 when available, and consider implementing file type restrictions or sandboxing for the application.
Adobe Framemaker 2022.9 or later
- 1. Save any open work in Adobe Framemaker and close the application
- 2. Open Adobe Creative Cloud desktop application or navigate to the Adobe Framemaker download page at helpx.adobe.com
- 3. Check for available updates to Adobe Framemaker
- 4. If an update to version 2022.9 or later is available, download and install it
- 5. Alternatively, download the standalone installer for Framemaker 2022.9 or later from Adobe's official website
- 6. Run the installer and follow the on-screen prompts to complete the upgrade
- 7. After installation, launch Framemaker and verify the version number matches 2022.9 or later
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation1.0 h
- Implementation1.0 h
- Testing1.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,200.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-27294 — 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 sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2026-27294 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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