Quick answers
- Is CVE-2026-103857 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-103857 being exploited in the wild.
- How severe is CVE-2026-103857?
- Medium severity, with a CVSS score of 5.5, 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-103857?
- 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-103857 attacked?
- It is attacked with local access.
- Am I affected by CVE-2026-103857?
- 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
CVE-2026-103857 is an out-of-bounds read (CWE-125) in Adobe FrameMaker that allows memory exposure. The vulnerability requires user interaction—a victim must open a malicious file—and is reachable via local attack vectors. Exploitation results in confidentiality breach with no code execution.
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