GHSA-3JH7-WM29-Q568
Vulnerability from github – Published: 2026-07-29 15:11 – Updated: 2026-07-29 15:11Summary
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 requires only that the target validate an attacker-supplied PDF. A single markup annotation with a crafted /RC string is sufficient.
Proposed Patch
Harden the DocumentBuilderFactory in validation-model/src/main/java/org/verapdf/gf/model/tools/DictionaryKeysHelper.java per the OWASP XXE Prevention Cheat Sheet to disallow DOCTYPE outright.
{
"affected": [
{
"database_specific": {
"last_known_affected_version_range": "\u003c= 1.30.1"
},
"package": {
"ecosystem": "Maven",
"name": "org.verapdf:validation-model"
},
"ranges": [
{
"events": [
{
"introduced": "1.25.73"
},
{
"fixed": "1.30.2"
}
],
"type": "ECOSYSTEM"
}
]
},
{
"database_specific": {
"last_known_affected_version_range": "\u003c= 1.31.70"
},
"package": {
"ecosystem": "Maven",
"name": "org.verapdf:validation-model"
},
"ranges": [
{
"events": [
{
"introduced": "1.31.1"
},
{
"fixed": "1.31.71"
}
],
"type": "ECOSYSTEM"
}
]
},
{
"database_specific": {
"last_known_affected_version_range": "\u003c= 1.30.1"
},
"package": {
"ecosystem": "Maven",
"name": "org.verapdf:validation-model-jakarta"
},
"ranges": [
{
"events": [
{
"introduced": "1.25.73"
},
{
"fixed": "1.30.2"
}
],
"type": "ECOSYSTEM"
}
]
},
{
"database_specific": {
"last_known_affected_version_range": "\u003c= 1.31.70"
},
"package": {
"ecosystem": "Maven",
"name": "org.verapdf:validation-model-jakarta"
},
"ranges": [
{
"events": [
{
"introduced": "1.31.1"
},
{
"fixed": "1.31.71"
}
],
"type": "ECOSYSTEM"
}
]
}
],
"aliases": [
"CVE-2026-54078"
],
"database_specific": {
"cwe_ids": [
"CWE-611"
],
"github_reviewed": true,
"github_reviewed_at": "2026-07-29T15:11:43Z",
"nvd_published_at": null,
"severity": "HIGH"
},
"details": "## Summary \n \n**Description**\nAn 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. \n \n## Details \nThe 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. \n \nThe vulnerability stems from two combined issues: \n- 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 `\u003c!DOCTYPE \u2026 SYSTEM \"\u2026\"\u003e` and `\u003c!ENTITY \u2026 SYSTEM \"\u2026\"\u003e` declarations. \n- 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. \n \n## Impact \n \nThis impacts all current releases of the veraPDF validation-model module. \n \nSuccessful exploitation requires only that the target validate an attacker-supplied PDF. A single markup annotation with a crafted /RC string is sufficient. \n \n## Proposed Patch \n \nHarden the `DocumentBuilderFactory` in `validation-model/src/main/java/org/verapdf/gf/model/tools/DictionaryKeysHelper.java` per the OWASP XXE Prevention Cheat Sheet to disallow DOCTYPE outright.",
"id": "GHSA-3jh7-wm29-q568",
"modified": "2026-07-29T15:11:43Z",
"published": "2026-07-29T15:11:43Z",
"references": [
{
"type": "WEB",
"url": "https://github.com/veraPDF/veraPDF-validation/security/advisories/GHSA-3jh7-wm29-q568"
},
{
"type": "PACKAGE",
"url": "https://github.com/veraPDF/veraPDF-validation"
}
],
"schema_version": "1.4.0",
"severity": [
{
"score": "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",
"type": "CVSS_V4"
}
],
"summary": "veraPDF Validation XXE via Rich Text"
}
Sightings
| Author | Source | Type | Date | Other |
|---|
Nomenclature
- Seen: The vulnerability was mentioned, discussed, or observed by the user.
- Confirmed: The vulnerability has been validated from an analyst's perspective.
- Published Proof of Concept: A public proof of concept is available for this vulnerability.
- Exploited: The vulnerability was observed as exploited by the user who reported the sighting.
- Patched: The vulnerability was observed as successfully patched by the user who reported the sighting.
- Not exploited: The vulnerability was not observed as exploited by the user who reported the sighting.
- Not confirmed: The user expressed doubt about the validity of the vulnerability.
- Not patched: The vulnerability was not observed as successfully patched by the user who reported the sighting.