dbcve.org
FramemakerApplication · Adobe

CVE-2025-47126

HIGH · 7.8 CVSS v3.1 Published 2025-07-08
Fix available
A fix is available. Upgrade to 2020.9 / 2022.7 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 2020.8, 2022.6 and earlier are affected by an out-of-bounds write 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 confidence

Adobe Framemaker versions 2020.8, 2022.6 and earlier contain an out-of-bounds write vulnerability. An attacker can exploit this by crafting a malicious file that, when opened by a victim, triggers the vulnerability and executes arbitrary code in the context of the current user's privileges.

MitigationUpdate Adobe Framemaker to the latest patched version. Additionally, educate users to avoid opening files from untrusted sources, as exploitation requires user interaction.

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:< 2020.9>= 2022, < 2022.7

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. Verify Adobe Framemaker is installed
    On Windows, check Registry key HKEY_LOCAL_MACHINE\SOFTWARE\Adobe\FrameMaker or HKEY_LOCAL_MACHINE\SOFTWARE\WOW6432Node\Adobe\FrameMaker for the InstallDir value. On macOS, check /Applications/Adobe FrameMaker for the application bundle.
    Affected if No FrameMaker entry exists in Registry or no application bundle is found - the system is not affected.
  2. Identify the installed Framemaker version
    On Windows, read the Version value from the Registry key at HKEY_LOCAL_MACHINE\SOFTWARE\Adobe\FrameMaker. On macOS, right-click Adobe FrameMaker.app, select Get Info, and read the Version field under General.
    Affected if Unable to determine version - further manual investigation required.
  3. Compare version against affected ranges
    If the installed version begins with 20.x, check if it is less than 20.0.9 (for example, 20.0.8 or earlier). If it begins with 22.x, check if it is less than 22.0.7 (for example, 22.0.6, 22.0.5, 22.0, or 22.x versions below 22.0.7).
    Affected if Version is 20.0.8 or earlier, OR version is 22.0.6 or earlier - the installed version is within the affected range.
  4. Confirm vulnerability trigger condition
    This vulnerability is triggered when a user opens a specially crafted malicious file in Adobe Framemaker. Verify if the application is configured to open files from untrusted or external sources.
    Affected if Users routinely open .fm or .framemaker files from untrusted sources without validation - exploitation is possible if the file is malicious.

The system is affected if Adobe Framemaker is installed with version 20.0.8 or earlier, or version 22.0.6 or earlier, and users may open untrusted files.

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 2020.9 / 2022.7 or later
Fixed in 2020.92022.7
Interim mitigation

Update Adobe Framemaker to the latest patched version. Additionally, educate users to avoid opening files from untrusted sources, as exploitation requires user interaction.

Recommended fix Moderate confidence

Framemaker 2020.9 (for 2020.x branch) or Framemaker 2022.7 (for 2022.x branch)

  1. 1. Determine the currently installed Adobe Framemaker version by opening Framemaker and navigating to Help > About Adobe Framemaker
  2. 2. If the installed version is 2020.8 or earlier (2020.x branch), upgrade to Framemaker 2020.9 or later
  3. 3. If the installed version is 2022.0 through 2022.6 (2022.x branch), upgrade to Framemaker 2022.7 or later
  4. 4. Download the appropriate fixed version from the official Adobe website or your organization's software distribution center
  5. 5. Run the installer with administrator privileges
  6. 6. After installation, restart Framemaker and verify the version in Help > About Adobe Framemaker shows the updated release
Caveat Security patch update; minimal risk of breaking changes expected

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

Fix this in Framemaker Scoped from the published advisory
  • Consultation2.0 h
  • Implementation2.0 h
  • Testing3.0 h
  • Review / QA1.0 h
8.0 hours of engineering $1,390
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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

Get it on GitHub Scan in the browser

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-2025-47126 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