Quick answers
- Is CVE-2026-126627 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-126627 being exploited in the wild.
- How severe is CVE-2026-126627?
- Informational severity, published 11 November 2026.
- Which products and versions are affected?
- Apache XML Graphics FOP through 2.11.
- Is there a fix for CVE-2026-126627?
- Yes: fixed in 2.12. Until then: Restrict file system access to the system directory where FOP processes documents and stores temporary files to only authorized users. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
- How is CVE-2026-126627 attacked?
- It is attacked with local access, in a software library.
- Am I affected by CVE-2026-126627?
- Check whether you run Apache XML Graphics FOP 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: 2.12
Restrict file system access to the system directory where FOP processes documents and stores temporary files to only authorized users.
Technical details
FOP creates temporary files during document processing with overly permissive file permissions that allow any local user to read them. The vulnerability is a classic temporary file permission issue (CWE-377/CWE-379) affecting the temporary file creation mechanism. An attacker with local access to the system can exploit this through standard file system access to read temporary files before they are cleaned up.
Affected products
- Apache XML Graphics FOP through 2.11
Timeline
- 2026-11-11: disclosed