Apache FOP: unsafe deserialization in hyphenation loading (CVE-2026-71395)

An affected Apache FOP deployment can deserialize unsafe data when loading hyphenation resources. Upgrade the renderer to remove the unsafe input path in deployments that load untrusted resources.

Public CVE record · Vendor or publisher advisory · Source and API bundle

cve.now entry. Product: Apache XML Graphics FOP (org.apache.xmlgraphics:fop-core) (lab: gabriel-fop-app).

Eden terminates the HTTP connection to the affected product, evaluates a declarative policy and — in tier 2 — a separately compiled native Rust module under signed module authority, before any byte reaches the application. It does not patch the affected component; the vendor's fixed release remains the durable repair.

Status: Remediated (tier 1 + tier 2), live-proven 2026-11-11T17:09:14Z on the installed eden-product-release:1.103.0 lab container.

The vulnerability

FOP's hyphenation-pattern loader deserializes a caller-supplied serialized object, so a crafted FO document reaches ObjectInputStream-equivalent gadget territory. The fixture (make_fop, port 18317) reproduces the delivery shape: a render upload carrying the Java serialization magic marker (aced0005) records a deserialization mark.

The Eden patch

Tier 1 — declarative policy (blunt, fail-closed): deny every request under /fop, ordinary FO rendering included — false positives measured below.

Tier 2 — native Rust module gabriel_fop_v1 (surgical): refuses upload bodies carrying the Java serialization magic marker; ordinary FO documents pass unchanged.

Implement the remediation

The commands are operator examples for the recorded scope. Compare fixture routes and software selectors with the intended deployment before use. See deployment prerequisites.

1. Prepare the target. Verify the loaded product and version against the advisory. Use a compatible Eden HTTP interlay and an authenticated operator with Configure permission. Open the deployment example and API instructions. The bundle identifies module gabriel_fop_v1 version 1.0.0 and the SDK revision in patch.toml. Run the policy extraction from the adapter directory.
2. Apply the declarative policy. Scope the policy to /fop and descendants (all methods, deny). Set INTERLAY to the target interlay UUID in the authenticated Eden CLI. Run an authenticated GET /api/v1/interlays/{interlay} with X-Eden-Verbose: true. Save its complete current settings object as current-settings.json and retain the prior remediation declaration for recovery. Set IDEMPOTENCY_KEY to a fresh key for this intended mutation.

jq -e '.tier1' deployment.json > remediation.json
jq -e --slurpfile policy remediation.json \
  '.remediation = $policy[0] | {settings: .}' current-settings.json \
  > interlay-update.json
eden api request PATCH "/api/v1/interlays/$INTERLAY" \
  --header "Idempotency-Key:$IDEMPOTENCY_KEY" \
  --body-file interlay-update.json --content-type application/json --confirm

3. Verify the serving policy. Read back the interlay.

eden api request GET "/api/v1/interlays/$INTERLAY" \
  --header 'X-Eden-Verbose:true'

Check that remediation_status.state is ready and both desired and effective SHA-256 values match the intended declaration. Replay the benign and marked requests in the recorded comparison on an isolated target. Check the recorded response and backend outcome for each probe. Use the request and expected-status table in the linked API example alongside the observed comparison. 4. Restore the previous policy. Coordinate the change with any other operator updating this interlay. Read current settings again and merge the saved remediation field into them. If the prior settings had no remediation field, omit it in the replacement. Send the same PATCH with a fresh idempotency key, then read back the intended state. Repeat the verification probes. Keep the affected route isolated if restoring the prior settings reopens exposure.

Native module gabriel_fop_v1

1. Prepare the archive. Use the version 1.0.0 bundle for source, target, and build profile. Configure independent host approval for the installed Eden release. Use the authenticated principals required by the native authority contract. Set PATCH_ARCHIVE to the exact schema-2 package and PACKAGE_SHA256 to its expected archive digest. Verify and import it using the same target interlay.

printf '%s  %s\n' "$PACKAGE_SHA256" "$PATCH_ARCHIVE" | sha256sum --check &&
  eden api request PUT "/api/v1/interlays/$INTERLAY/patch-packages/$PACKAGE_SHA256" \
    --body-file "$PATCH_ARCHIVE" \
    --content-type application/vnd.eden.patch-package.v2+tar --confirm

2. Approve and activate. Enroll the publisher key, attest host software inventory, and inspect the configuration returned by import. Obtain independent host approval. Sign the typed statement with the matching SDK. Send the admit action followed by activate for the prepared operation. Use the applicable typed payload for each action in authority-action.json.

eden api request POST "/api/v1/interlays/$INTERLAY/native-authority" \
  --body-file authority-action.json --content-type application/json --confirm

3. Verify the operation. Read the receipt through the same endpoint. Confirm serving_now and the full expected shard acknowledgment. Repeat the report’s benign and marked probes and check the backend observations.
4. Revoke or restore. Send revoke with the exact operation UUID. Mandatory protection can refuse traffic until a compatible operation is approved and activated. Verify the restored receipt and repeat the probes.

Vendor update. Use the advisory to identify the supported update or workaround for the installed release. The advisory data used here supplies no fixed version. Confirm the running version and verify the affected feature after the change.

Measured comparison (fixtures10, run 2026-11-11)

Performance trace (Eden telemetry, live 2026-11-11)

Measured with Eden's built-in request telemetry (gateway.request.baseline spans, read back through /api/v1/analytics/telemetry?signal=traces), not client wall-clock. Latency Eden introduces per remediation arm for this case:

Eden-added latency for the tier-2 remediation: benign requests complete in 360 µs mean (p50 342 µs, p95 476 µs) in-product, module evaluation included. Honest scope: lab fixtures on one host, fresh connection per measured request, warm requests only; module reactivated shards 2/2 with a fresh signed statement per measurement; spans carry the full authority lineage (module SHA-256, operation, publication). Not the EDEN-3640 performance qualification contract.

Tested against: eden-product-release:1.103.0-single (image sha256:809293e1f0b525ac…, build target eden_service_single, tooling revision 81a0724a…). Raw data: module2/telemetry-ab/fop-telemetry.json and module2/tier1-ab/fop-tier1.json.

Authority lifecycle and negatives

Import 201, activation: explicit_required; publisher enroll_key, host inventory + approve, reader inspect refused 403; tampered-statement admit 400; invalid-signature admit 403; admit prepared (not serving), activate → receipt serving_now, applied shards 2/2. Revoke → the identical attack gets 503 (fail-closed); re-approve + re-activate → 403 again. All recorded in the evidence JSON.

Honest scope

The fixture reproduces the serialized-marker delivery shape, not the full FOP hyphenation API. Bypass variants (gadget encodings, alternate loaders, compressed streams) are not bypass-tested; the rule is a lab-grade partial. First live attempt hit the trailing-slash policy rejection (E04FF) and a native-conditions exact-path mismatch; both fixed, case re-run clean. Module binary SHA-256 3db8222e…, source modules/gabriel_fop_v1.rs.

Cost record

Run window 17:09:14Z → 17:09:25Z (per-CVE ledger, marginal session cost).

Evidence appendix

• Fixture: gabriel-2026-11-11/fixtures10.py (make_fop, port 18317)
• Evidence: gabriel-2026-11-11/module2/evidence/fop-module.json
• Module source: docs/case-studies/modules/gabriel_fop_v1.rs