CVE-2026-27299
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 Improper Input Validation vulnerability that could lead to arbitrary file system read. An attacker could leverage this vulnerability to access sensitive files or data on the system. 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 improper input validation vulnerability that allows arbitrary file system read. Exploitation requires user interaction—a victim must open a malicious file, enabling attackers to access sensitive files or data on the system.
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
- Changed
- Confidentiality
- High
- Integrity
- None
- Availability
- None
CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:C/C:H/I:N/A:N
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.
-
Verify Adobe Framemaker is installedCheck for Framemaker installation on the system. On Windows, look in Program Files/Adobe or check registry key HKLM\SOFTWARE\Adobe\FrameMaker. On macOS, check /Applications for FrameMaker.app.Affected if Adobe Framemaker is not installed on the system
-
Determine installed Framemaker versionOpen Framemaker and go to Help > About Adobe Framemaker, or check the Windows registry at HKLM\SOFTWARE\Adobe\FrameMaker\Version, or inspect the executable file properties of framemaker.exe.Affected if Cannot determine the version number
-
Compare version to affected rangeCompare the installed version number against the affected versions: any version 2022.8 or earlier is affected. The fixed version is 2022.9.Affected if Installed version is 2022.8 or earlier (any version before 2022.9)
-
Confirm file parsing is in useThis vulnerability triggers when opening a malicious file, which is a core function of Framemaker as a document authoring tool. If Framemaker can open and parse files, the feature is enabled.Affected if Framemaker is installed and capable of opening document files
The system is affected if Adobe Framemaker is installed with version 2022.8 or earlier, since the vulnerability allows arbitrary file read through 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 version newer than 2022.8 when the vendor releases a patch, and avoid opening untrusted or unexpected files.
Adobe Framemaker 2022.9 or later
- Upgrade Adobe Framemaker to version 2022.9 or later
- After upgrading, verify the version by navigating to Help > About Adobe Framemaker to confirm the installation
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation3.0 h
- Implementation2.0 h
- Testing4.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,072.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-27299 — 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-27299 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