Categories
CVE-2026-54078

XXE (XML External Entity) in org.verapdf:validation-model (CVE-2026-54078)

Summary

Vulnerability in org.verapdf:validation-model (CVE-2026-54078). Risk of unauthorized operations or information disclosure. Exploitable via DocumentBuilderFactory. Mitigation: upgrade to 1.31.71 or later.

Original description

The description as published by the source.

Summary

Description
An XML External Entity Injection (CWE-611) vulnerability in veraPDF allows a remote attacker to read arbitrary files on the server file system and perform Server-Side Request Forgery by submitting a crafted PDF containing a malicious rich-text (/RC or /RV) entry. This affects all current versions of veraPDF-validation.

Details

The vulnerability resides in veraPDF-validation validation-model/src/main/java/org/verapdf/gf/model/tools/DictionaryKeysHelper.java within the getRichTextStringOrStreamEntryStringRepresentation() method. This helper extracts the XHTML rich-text body from a PDF dictionary string or stream and parses it with a DOM parser to return the concatenated text content.

The vulnerability stems from two combined issues:

  • The DocumentBuilderFactory is instantiated with default settings , no disallow-doctype-decl, no disabling of external general/parameter entities, no FEATURE_SECURE_PROCESSING, and no secure EntityResolver. The default JAXP/Xerces parser will therefore resolve <!DOCTYPE … SYSTEM "…"> and <!ENTITY … SYSTEM "…"> declarations.
  • After parsing, getAllNodeText() recursively concatenates every text node in the document and returns it as the model property value. This means the expanded contents of any external entity are reflected directly back into the validation report.

Impact

This impacts all current releases of the veraPDF validation-model module.

Successful exploitation r…

Source: GitHub Security Advisories (Global) NVD GitHub Advisory

Auto-generated summary

Assembled by SecPulse from the source data (CVSS, CWE, affected versions) using templates — no AI involved. Check the original description and references below for exact details.

A vulnerability tracked as CVE-2026-54078 has been found in org.verapdf:validation-model.
Attackers can target a specific entry point like DocumentBuilderFactory over the network to misuse the product.
Risk of unauthorized operations or information disclosure.
What to do: upgrade org.verapdf:validation-model to 1.31.71 or later.
If unsure, ask your IT team or search "org.verapdf:validation-model CVE-2026-54078" on the vendor's site.

CVE-2026-54078 (org.verapdf:validation-model) — CWE-611
Attack surface: DocumentBuilderFactory
Patched: 1.31.71 — apply immediately
Plan: 1) Audit SBOM/dependencies, 2) Stage→prod upgrade, 3) Add WAF/proxy monitoring on affected endpoints, 4) Hunt IOCs in logs.
Refs: see the GHSA / vendor advisory / patched release linked on this page.

❓ What is the problem

A vulnerability (CWE-611) exists in org.verapdf:validation-model. Attackers reach the vulnerable code path via DocumentBuilderFactory.

📍 Affected scope

Check the vendor advisory for the affected versions of org.verapdf:validation-model. Attack surface: DocumentBuilderFactory.

🔥 Severity

Severity: ?. Risk of unauthorized operations or information disclosure.

🔧 How to fix

Update to 1.31.71.

🛡️ Workaround

Until the patch is applied: disable the affected feature, apply WAF rules, or restrict access via network ACLs.

🔍 Detection

Search webserver/proxy logs for unusual request patterns matching this CVE's known IOCs. Audit SBOM/dependencies to find affected services.

Response actions

Concrete steps and command examples for SOC/SRE teams to execute in order

  1. 1
    Identify exposure identify
    Audit SBOM/dependencies for affected components.

    資産台帳・SBOM・依存マニフェストで org.verapdf:validation-model を使っているサービスとバージョンを洗い出す。

  2. 2
    Apply patch patch
    Upgrade org.verapdf:validation-model to 1.31.71

    ステージング環境で 1.31.71 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスを含めること。

  3. 3
    Post-deployment verification verify
    Confirm patched version is live in production

    パッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番ではアクセスログ・WAF でアラート再発が無いか継続監視。

Affected packages

maven org.verapdf:validation-model
[{"type":"ECOSYSTEM","events":[{"introduced":"1.31.1"},{"fixed":"1.31.71"}]}]
maven org.verapdf:validation-model-jakarta
[{"type":"ECOSYSTEM","events":[{"introduced":"1.31.1"},{"fixed":"1.31.71"}]}]

References

We use cookies for analytics and ad measurement. This setting applies to all Game co., Ltd. sites. Details