Skip to main content
Menu
CVEs

CVE

Apache XML Graphics FOP: CWE-502 unsafe deserialization in hyphenation loading

CVE-2026-71395EUVD-2026-123531GHSA-538H-76QV-3VQW

Exploited
No known exploitation
Fix
See vendor advisory
Who is exposed
Not reported
Published
Last modified
Reference
Last checked
15/100 · provisional
None on Exploit-DB, Metasploit or GitHub

Summary

Apache XML Graphics FOP, a Java library for turning XSL-FO documents into output such as PDF, contains an unsafe deserialization flaw in how it loads hyphenation data. The facts do not state how an attacker reaches the flaw or what they gain from it, so no remote or local access path is described here.

Written by anthropic/claude-haiku-5.5 from the sources below. Verify against them.

Read the original description

unsafe deserialization in hyphenation loading vulnerability in Apache XML Graphics FOP.

This issue affects Apache XML Graphics FOP: through 2.11.

Users are recommended to upgrade to version 2.12, which fixes the issue.

cve.now Index

15Pcve.now Index 15 of 100 · methodology v3 · provisional
  • Exploitation?/40Unknown. No CISA SSVC exploitation rating yet
  • Exposure?/25Unknown. No advisory context yet
  • Reach10/20Affects Maven packages
  • Severity?/10Unknown. No CVSS score or vendor rating
  • No patch5/5No fixed version listed; see vendor advisory

What would change the score

  • Would score about 70 if added to CISA KEV
  • Would score about 65 if CISA's SSVC rates exploitation active
  • Would score about 37 if advisories confirm default setups are exposed

Check your systems with an agent

Paste this into a coding or ops agent. It checks your systems read-only and reports a table per asset.

Check whether my systems are affected by CVE-2026-71395 (Apache XML Graphics FOP: CWE-502 unsafe deserialization in hyphenation loading), using the cve.now data below.

Rules: work read-only. Do not run exploit code, proof-of-concept scripts or scanners that send attack payloads, and do not change any configuration, package, image or deployment. Report findings only.

What cve.now has for CVE-2026-71395 (entry last updated 2026-11-11):
Affected:
- Maven package org.apache.xmlgraphics:fop-core: through 2.11.0
Fixed versions: none listed yet.
Setup: unknown whether the bug needs a non-default feature or setting. Check the advisory.
CISA KEV: CVE-2026-71395 is not listed as of cve.now's last read.
This KEV status is for CVE-2026-71395 only. If you also check another CVE, look up its own KEV status; never assume it from this one.

How to check:
- Packages (Maven): find every lockfile in each project and run the stack.check operation of the cve.now MCP server (execute) on each one. Compare the resolved versions, not the ranges a manifest declares, with the affected versions above. Include transitive dependencies.

Verify against the linked advisories before concluding, and cite the date you read each one:
- https://lists.apache.org/thread.html/nsb89to1r0vzdh3t4w7x10q4z3xk5jqf
- https://issues.apache.org/jira/browse/FOP-3332
- http://www.openwall.com/lists/oss-security/2026/11/11/19
Do not conclude an asset is unaffected unless you checked it and the evidence covers both its version and the conditions above. If you could not check something, mark it unknown and say what is missing.

Report a table with one row per asset and these columns: Asset | Version or build | Status (affected, fixed, not applicable, unknown) | Compensating controls | Exposure (internet-facing, internal, none) | Evidence | Next action.

Entry: https://cve.now/CVE-2026-71395
For follow-up questions, use the cve.now MCP server at https://mcp.cve.now/mcp (no authentication), for example execute with name cve.get and arguments {"id": "CVE-2026-71395"}.

Timeline

  1. CVE published
  2. First seen by cve.now
  3. Record last updated

Affected versions

Evidence 5

Vendor advisory · 1

Establishes: Affected and fixed versions.

  1. Advisory

CVE record · 2

Establishes: The identifier and description.

  1. Record
  2. Record

Write-ups · 2

Establishes: Technical detail and context.

  1. Report
  2. Link

Corrections

None so far.

Something wrong on this page? Report an error. Every fix is listed here.

Questions about CVE-2026-71395

Is CVE-2026-71395 being exploited?

It is not in CISA's Known Exploited Vulnerabilities catalog, and CISA's SSVC assessment does not mark exploitation as active. That does not mean it has not been attacked: vendors and researchers can report attacks before CISA lists them. No public exploit code is tracked.Source: cve.now feed data

Which versions are affected by CVE-2026-71395?

org.apache.xmlgraphics:fop-core (Maven): through 2.11.0.Source: cve.now feed data