CVE-2026-27297
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 Integer Underflow (Wrap or Wraparound) 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 · moderate confidenceAdobe Framemaker versions 2022.8 and earlier contain an integer underflow (wrap or wraparound) vulnerability that can be triggered when parsing a specially crafted malicious file. Successful exploitation allows arbitrary code execution in the context of the current user without requiring elevated privileges.
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.
-
Check installed Adobe Framemaker versionOpen Adobe Framemaker, then go to Help > About Adobe Framemaker to display the version number. Alternatively, check the Windows Programs and Features list or macOS Applications folder for the installed version.Affected if The displayed version is 2022.8 or earlier, meaning it is below 2022.9 and falls within the affected range.
-
Verify Framemaker can open document filesConfirm that Adobe Framemaker is capable of opening .fm or other document files, as the vulnerability is triggered during file parsing.Affected if Framemaker is installed and functional to open files, which is the default state.
-
Identify user privilege contextNote the Windows or macOS account used to run Adobe Framemaker. The vulnerability executes code in the context of the current user's privileges.Affected if The user runs Framemaker with elevated or standard user privileges, as the vulnerability impacts whatever user context is active when the malicious file is opened.
A user is affected if Adobe Framemaker version 2022.8 or earlier (below 2022.9) is installed and the application is used to open files, since the integer underflow triggers during malicious file parsing.
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
Update Adobe Framemaker to a patched version beyond 2022.8. Users should avoid opening files from untrusted sources until the patch is applied.
Adobe Framemaker 2022.9 or later
- 1. Open Adobe Framemaker and navigate to Help > About Adobe Framemaker to confirm the current version
- 2. If version is 2022.8 or earlier, download Adobe Framemaker 2022.9 or later from the official Adobe website (helpx.adobe.com)
- 3. Close all Adobe applications before running the installer
- 4. Run the installer with administrator privileges and follow the on-screen prompts
- 5. After installation completes, relaunch Framemaker and verify the version shows 2022.9 or later via Help > About Adobe Framemaker
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation1.0 h
- Implementation2.0 h
- Testing2.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,664.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-27297 — 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-27297 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