veraPDF Validation XXE via Rich Text
CVE-2026-54078GHSA-3jh7-wm29-q568
What to do
Vendor fix available. Upgrade each affected package to the fixed version on its release line (org.verapdf:validation-model 1.31.71, 1.30.2; org.verapdf:validation-model-jakarta 1.31.71, 1.30.2), redeploy, then verify what is actually installed.
This page has no inventory attached, so it cannot say whether you are affected. A vendor fix is not proof that your deployment is fixed.
Affected packages
Maven org.verapdf:validation-model
- Affected
- >= 1.25.73, <= 1.30.1>= 1.31.1, <= 1.31.70
- Fixed in
- 1.30.2, 1.31.71
Maven org.verapdf:validation-model-jakarta
- Affected
- >= 1.25.73, <= 1.30.1>= 1.31.1, <= 1.31.70
- Fixed in
- 1.30.2, 1.31.71
Sources
- Open Source Vulnerabilities (OSV.dev), including the GitHub Advisory Database
OSV record GHSA-3jh7-wm29-q568 lists affected ranges: Maven org.verapdf:validation-model >=1.25.73 =1.31.1 =1.25.73 =1.31.1 <1.31.71 (fixed)
VerifiedObserved Structured OSV record; GitHub-reviewed advisory.
- GitHub Advisory Database and maintainer security advisories on GitHub
GitHub-reviewed advisory GHSA-3jh7-wm29-q568 lists affected ranges: Maven org.verapdf:validation-model >=1.25.73 =1.31.1 =1.25.73 =1.31.1 <=1.31.70
VerifiedObserved Structured GitHub Advisory Database record (type=reviewed) from the GitHub REST API.
Severity and exploitation
- Exploitation
- No confirmed exploitation recorded. Patch Next marks exploitation only from CISA KEV.
- CVSS 4.0
- 8.7 · CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:N/VA:N/SC:N/SI:N/SA:N · score source
- EPSS
- CVE-2026-54078: 0.56% estimated exploitation activity in the next 30 days; percentile 46.34 (FIRST EPSS, 2026-11-03). This is a model estimate, not proof of exploitation or customer exposure.
Source description
As published by the source; long descriptions are shortened.
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 FEATURESECUREPROCESSING, and no secure EntityResolver. The default JAXP/Xerces parser…
Dates and revisions
- Published by the source
- Last modified by the source
- Source last checked
- Revision 3 · amended ·
Amended from ghsa record GHSA-3jh7-wm29-q568
- Revision 2 · amended ·
Reviewed OSV alias/range/CVSS4 correction; package source scopes and original publication preserved. No customer finding resolved.
- Revision 1 · created ·
Published from osv record GHSA-3jh7-wm29-q568
Agent brief
Preview the exact text before you copy it. Commands are read-only suggestions; review them before running anything.
# Patch Next advisory brief: CVE-2026-54078 Advisory: veraPDF Validation XXE via Rich Text IDs: CVE-2026-54078, GHSA-3jh7-wm29-q568 Record: https://patchnext.com/advisories/cve-2026-54078 (revision 3, source checked 26 Oct 2026, 16:54 UTC) Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected. Severity: High (CVSS 8.7) Exploitation: no confirmed exploitation recorded. Patch Next confirms exploitation only from CISA KEV. Vendor response: Vendor fix available; fixed versions by package: org.verapdf:validation-model 1.31.71, 1.30.2; org.verapdf:validation-model-jakarta 1.31.71, 1.30.2. A vendor fix does not mean a deployment is fixed. ## Affected components - Maven org.verapdf:validation-model: affected >= 1.25.73, <= 1.30.1; >= 1.31.1, <= 1.31.70; fixed in 1.30.2, 1.31.71 - Maven org.verapdf:validation-model-jakarta: affected >= 1.25.73, <= 1.30.1; >= 1.31.1, <= 1.31.70; fixed in 1.30.2, 1.31.71 ## Suggested inspection (read-only) - Maven org.verapdf:validation-model: check the installed version with your package manager. - Maven org.verapdf:validation-model-jakarta: check the installed version with your package manager. ## Supported action Upgrade each affected component to a fixed version on its release line. For a transitive dependency, upgrade the parent package or add an override or constraint, then regenerate the lockfile. Redeploy every environment that ran an affected version. ## Required regression checks - Run the test suite and a production build. - Exercise the features that depend on org.verapdf:validation-model, org.verapdf:validation-model-jakarta. - Repeat the inspection and confirm that only fixed versions remain installed. ## Rollback considerations - Keep the previous lockfile and deployment artifact. Rolling back reinstates the vulnerable version, so apply any documented mitigation while you fix forward. ## Unresolved questions - Which deployments run an affected version? - Exploitation status can change. Check again before lowering the priority. - Mark the work resolved only after the fixed version is verified in production. ## Sources - Verified: https://osv.dev/vulnerability/GHSA-3jh7-wm29-q568 (OSV record GHSA-3jh7-wm29-q568 lists affected ranges: Maven org.verapdf:validation-model >=1.25.73 =1.31.1 =1.25.73 =1.31.1 <1.31.71 (fixed)) - Verified: https://github.com/advisories/GHSA-3jh7-wm29-q568 (GitHub-reviewed advisory GHSA-3jh7-wm29-q568 lists affected ranges: Maven org.verapdf:validation-model >=1.25.73 =1.31.1 =1.25.73 =1.31.1 <=1.31.70) Commands are suggestions: review each one before running it.
Loading voting…