How severe is GHSA-3jh7-wm29-q568?

No CVSS score has been assigned to GHSA-3jh7-wm29-q568 yet. Review the advisory details and affected package list to assess your exposure.

Which packages are affected by GHSA-3jh7-wm29-q568?

GHSA-3jh7-wm29-q568 affects the following packages: org.verapdf:validation-model (Maven), org.verapdf:validation-model (Maven), org.verapdf:validation-model-jakarta (Maven), org.verapdf:validation-model-jakarta (Maven). Ecosystems affected: Maven.

How do I fix GHSA-3jh7-wm29-q568?

Update org.verapdf:validation-model to 1.30.2 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-3jh7-wm29-q568 is resolved across your whole dependency graph.

How do I detect GHSA-3jh7-wm29-q568 in my Maven dependencies?

Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for org.verapdf:validation-model. O3's reachability analysis confirms whether the vulnerable code path is actually invoked in your application, so you act on real exposure instead of every transitive match.

How do I mitigate GHSA-3jh7-wm29-q568 if there is no patch (or I can't update yet)?

If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.

How does O3 Security protect against GHSA-3jh7-wm29-q568?

O3 pinpoints whether GHSA-3jh7-wm29-q568 is reachable in your code and exactly where to fix it, then blocks exploitation in production at runtime until the patched version is deployed.

Is GHSA-3jh7-wm29-q568 actively exploited in the wild?

No public exploit code has been indexed for GHSA-3jh7-wm29-q568 yet. This does not mean the vulnerability cannot be exploited — absence of public exploits does not imply safety. Apply the recommended fix and use O3 Security to monitor your exposure.

What type of vulnerability is GHSA-3jh7-wm29-q568?

GHSA-3jh7-wm29-q568 is classified as XML External Entity (XXE) (CWE-611). This weakness type describe the underlying flaw category, which helps determine the potential impact and the right class of mitigation.

When was GHSA-3jh7-wm29-q568 published, and has it been updated?

GHSA-3jh7-wm29-q568 was published on July 29, 2026 and was last updated on July 29, 2026. Advisory data evolves as severity scores, affected ranges, and exploit intelligence are revised — always check the latest version of the advisory before acting.

☕ Maven

GHSA-3jh7-wm29-q568

GHSA-3jh7-wm29-q568 is a XML External Entity (XXE) vulnerability in org.verapdf:validation-model. O3 Security confirms whether GHSA-3jh7-wm29-q568 is actually reachable in your code before you act, and blocks exploitation at runtime until you patch.

veraPDF Validation XXE via Rich Text

Also known asCVE-2026-54078

Published

Jul 29, 2026

Updated

Jul 29, 2026

Affected

4 pkgs

Patched

4 / 4

Exploits

None indexed

Blast Radius

4 pkgs affected

☕org.verapdf:validation-model☕org.verapdf:validation-model☕org.verapdf:validation-model-jakarta☕org.verapdf:validation-model-jakarta

Real-time download stats are indexed for npm and PyPI packages. This vulnerability affects Maven packages — download data is not available via public APIs for these ecosystems.

Description

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 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 Packages

4 total 4 fixed

Ecosystem	Package	Vulnerable range	Fix
☕Maven	`org.verapdf:validation-model`	≥ 1.25.73&&< 1.30.2	1.30.2
☕Maven	`org.verapdf:validation-model`	≥ 1.31.1&&< 1.31.71	1.31.71
☕Maven	`org.verapdf:validation-model-jakarta`	≥ 1.25.73&&< 1.30.2	1.30.2
☕Maven	`org.verapdf:validation-model-jakarta`	≥ 1.31.1&&< 1.31.71	1.31.71

Detection & mitigation playbook

Open-source dependency

Detect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for org.verapdf:validation-model. O3's reachability analysis confirms whether the vulnerable code path is actually invoked in your application, so you act on real exposure instead of every transitive match.
Fix
Update org.verapdf:validation-model to 1.30.2 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-3jh7-wm29-q568 is resolved across your whole dependency graph.
Workarounds
If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.
How O3 protects you
O3 pinpoints whether GHSA-3jh7-wm29-q568 is reachable in your code and exactly where to fix it, then blocks exploitation in production at runtime until the patched version is deployed.

Tailored to GHSA-3jh7-wm29-q568. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.

Frequently Asked Questions

## 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

O3 Security · Impact-Aware SCA

Is GHSA-3jh7-wm29-q568 in your dependencies?

O3 detects GHSA-3jh7-wm29-q568 across Maven dependencies and uses function-level reachability to confirm whether the vulnerable code path is actually reachable — not just present. No false positives.

Scan my dependencies How O3 SCA works