Categories
CVE-2026-54082 medium CVSS 6.5

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

Summary

Vulnerability in org.verapdf:validation-model (CVE-2026-54082). 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.

veraPDF validation model is an implementation of the veraPDF validation model. From 1.25.73 until 1.30.2 and 1.31.71, veraPDF-validation contains an XML External Entity vulnerability in PDFAValidator.validate(...) and GFPDAcroForm.getdynamicRender(), where default DocumentBuilderFactory parsing of rich-text annotation or form-field values and XFA configurations in untrusted PDFs can allow local file disclosure and outbound network requests. This issue is fixed in versions 1.30.2 and 1.31.71.

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-54082 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. CVSS score: 6.5/10.
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-54082" on the vendor's site.

CVE-2026-54082 (org.verapdf:validation-model) — CWE-611 / CVSS v3 6.5
Attack vector: remote (network-reachable) / unauthenticated / no user interaction
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 without authentication.

📍 Affected scope

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

🔥 Severity

Severity: Medium (CVSS 6.5/10). 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