Is CVE-2026-104341 exploited in the wild?

No. Junglewise Threat Intelligence has no report of CVE-2026-104341 being exploited in the wild.

How severe is CVE-2026-104341?

High severity, with a CVSS score of 7.8, published 13 October 2026.

Which products and versions are affected?

Adobe FrameMaker 2022 17.0.9.866 and earlier; Adobe FrameMaker 2026 18.0.0.206 and earlier.

Is there a fix for CVE-2026-104341?

Yes: fixed in FrameMaker 2026 18.0.1.312; FrameMaker 2022 17.0.10.928. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.

How is CVE-2026-104341 attacked?

It is attacked with local access, in a web application.

Am I affected by CVE-2026-104341?

Check whether you run Adobe FrameMaker 2022 or Adobe FrameMaker 2026 at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

CVE-2026-104341: Adobe FrameMaker out-of-bounds write vulnerability

CVE-2026-104341 · Severity: high · CVSS 7.8 · Published 2026-10-13

Adobe FrameMaker, a document authoring and publishing tool used by technical professionals, contains an out-of-bounds write vulnerability that allows arbitrary code execution when a user opens a malicious file. An attacker can exploit this to gain full control of the victim's system with the current user's privileges. The vulnerability requires user interaction but poses a significant risk to organizations using FrameMaker for technical documentation.

Technologies: Adobe FrameMaker 2022, Adobe FrameMaker 2026. Vendors: Adobe.

Quick answers

Is CVE-2026-104341 exploited in the wild?: No. Junglewise Threat Intelligence has no report of CVE-2026-104341 being exploited in the wild.
How severe is CVE-2026-104341?: High severity, with a CVSS score of 7.8, published 13 October 2026.
Which products and versions are affected?: Adobe FrameMaker 2022 17.0.9.866 and earlier; Adobe FrameMaker 2026 18.0.0.206 and earlier.
Is there a fix for CVE-2026-104341?: Yes: fixed in FrameMaker 2026 18.0.1.312; FrameMaker 2022 17.0.10.928. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
How is CVE-2026-104341 attacked?: It is attacked with local access, in a web application.
Am I affected by CVE-2026-104341?: Check whether you run Adobe FrameMaker 2022 or Adobe FrameMaker 2026 at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

How to fix

Fixed in: FrameMaker 2026 18.0.1.312; FrameMaker 2022 17.0.10.928

Technical details

The vulnerability is an out-of-bounds write (CWE-787) in FrameMaker's file parsing logic that allows an attacker to write data beyond allocated buffer boundaries, leading to arbitrary code execution. Exploitation requires local file interaction and user action to open a crafted malicious document; no network vector exists. Adobe has released patched versions 18.0.1.312 for FrameMaker 2026 and 17.0.10.928 for FrameMaker 2022.

Affected products

Adobe FrameMaker 2026 18.0.0.206 and earlier
Adobe FrameMaker 2022 17.0.9.866 and earlier

Timeline

2026-10-13: disclosed

References

https://www.adobe.com/trust/security/products/framemaker/apsb26-172.html

This page as Markdown. Free to reuse under CC BY 4.0 with a link back.