Skip to content

← Public intelligence

Maven package

org.verapdf:validation-model

Open actionable advisories and recorded vendor fixes. This public package view has no inventory attached and cannot establish whether your deployment is affected. A vendor fix never resolves your finding; verify your installed version and the source guidance.

Open advisories

3 actionable advisories, newest first. Withdrawn advisories and news are excluded. Coverage is partial.

  1. Medium, CVSS 6.5MavenAmendedPublished

    veraPDF-validatio: Use of Default DocumentBuilderFactory leads to XXE When Processing Untrusted PDFs

    CVE-2026-54082 · GHSA-cg9x-g3gm-h5h6

    Affected
    • Maven org.verapdf:validation-model >= 1.17.35, <= 1.30.1; >= 1.31.1, <= 1.31.70
    Fixed in
    1.30.21.31.71· Vendor fix available
    Issue
    veraPDF-validation has an XML External Entity (XXE) vulnerability in two PDF parsing paths (validate and GFPDAcroForm.getdynamicRender()). A malicious/crafted PDF supplied to a veraPDF consumer can lead to the expansion of external entities while parsing rich-text annotation/form-field values or XFA configurations, allowing local file disclosure and potentially outbound network requests depending on the runtime (host) environment. Details Consumers that utilise either the PDFAValidator.validate(...) or GFPDAcroForm(acroForm).getdynamicRender() APIs to process untrusted PDFs are vulnerable to XXE exploits. Both vulnerable paths share the same root cause: the underlying source binds a default DocumentBuilderFactory and immediately calls newDocumentBuilder() which does not disable parsing of DTDs, external entities, XInclude, or external resource access directives in XML schemas. This is an XXE vulnerability affecting applications that use veraPDF's affected APIs to parse or…

    Recommended action: Upgrade to 1.31.71 or 1.30.2 by release line, then redeploy and verify.A vendor fix does not resolve your finding until you verify it in your own systems.

    Sources:osv.dev (1)github.com (2)Source checked Evidence →
  2. High, CVSS 8.7MavenAmendedPublished

    veraPDF Validation XXE via Rich Text

    CVE-2026-54078 · GHSA-3jh7-wm29-q568

    Affected
    • Maven org.verapdf:validation-model >= 1.25.73, <= 1.30.1; >= 1.31.1, <= 1.31.70
    Fixed in
    1.30.21.31.71· Vendor fix available
    Issue
    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 FEATURESECUREPROCESSING, and no secure EntityResolver. The default JAXP/Xerces parser…

    Recommended action: Upgrade to 1.31.71 or 1.30.2 by release line, then redeploy and verify.A vendor fix does not resolve your finding until you verify it in your own systems.

    Sources:osv.dev (1)github.com (2)Source checked Evidence →
  3. High, CVSS 8.7MavenAmendedPublished

    veraPDF Validation XXE via XFA

    CVE-2026-54079 · GHSA-36mm-w85j-3q2j

    Affected
    • Maven org.verapdf:validation-model >= 1.17.35, <= 1.30.1; >= 1.31.1, <= 1.31.70
    Fixed in
    1.30.21.31.71· Vendor fix available
    Issue
    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 XFA stream. This affects all current versions of veraPDF-validation. Details The vulnerability resides in veraPDF-validation validation-model/src/main/java/org/verapdf/gf/model/impl/pd/GFPDAcroForm.java within the getdynamicRender() method. This method retrieves the /XFA entry from the PDF's /AcroForm dictionary, decodes the embedded XML stream, and parses it to extract the <dynamicRender element value. The vulnerability stems from the use of a default-configured DocumentBuilderFactory to parse fully attacker-controlled XML: - The factory is created via DocumentBuilderFactory.newInstance() with no security features enabled. disallow-doctype-decl, external-general-entities, external-parameter-entities, and FEATURESECUREPROCESSING are…

    Recommended action: Upgrade to 1.31.71 or 1.30.2 by release line, then redeploy and verify.A vendor fix does not resolve your finding until you verify it in your own systems.

    Sources:osv.dev (1)github.com (2)Source checked Evidence →