How severe is GHSA-4cx5-89vm-833x?

No CVSS score has been assigned to GHSA-4cx5-89vm-833x yet. Review the advisory details and affected package list to assess your exposure.

Which packages are affected by GHSA-4cx5-89vm-833x?

GHSA-4cx5-89vm-833x affects the following packages: org.verapdf:core (Maven), org.verapdf:core-jakarta (Maven), org.verapdf:core-arlington (Maven), org.verapdf:verapdf-library (Maven), org.verapdf:verapdf-library-jakarta (Maven), org.verapdf:verapdf-library-arlington (Maven), org.verapdf:library (Maven), org.verapdf:library-jakarta (Maven), and 1 more. Ecosystems affected: Maven.

How do I fix GHSA-4cx5-89vm-833x?

Update org.verapdf:core to 1.26.2 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-4cx5-89vm-833x is resolved across your whole dependency graph.

How do I detect GHSA-4cx5-89vm-833x in my Maven dependencies?

Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for org.verapdf:core, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.

How do I mitigate GHSA-4cx5-89vm-833x 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.

Is GHSA-4cx5-89vm-833x actively exploited in the wild?

No public exploit code has been indexed for GHSA-4cx5-89vm-833x 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 is the EPSS score for GHSA-4cx5-89vm-833x?

GHSA-4cx5-89vm-833x has an EPSS (Exploit Prediction Scoring System) score of 1.1%, placing it in the 66th percentile of all CVEs. EPSS is maintained by FIRST.org and estimates the probability that a vulnerability will be exploited in the wild within the next 30 days. This score indicates relatively lower exploitation probability, though the CVSS severity should still guide your patching priority.

What type of vulnerability is GHSA-4cx5-89vm-833x?

GHSA-4cx5-89vm-833x 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-4cx5-89vm-833x published, and has it been updated?

GHSA-4cx5-89vm-833x was published on December 2, 2024 and was last updated on May 14, 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

Not in CISA KEV

veraPDF CLI has potential XXE (XML External Entity Injection) vulnerabilityGHSA-4cx5-89vm-833x

GHSA-4cx5-89vm-833x is a XML External Entity (XXE) vulnerability in org.verapdf:core. A fix is available for org.verapdf:core — see the affected versions and patch details below.

Also known asCVE-2024-52800

Published

Dec 2, 2024

Updated

May 14, 2026

Affected

9 pkgs

Patched

9 / 9

Exploits

None indexed

Exploitation data as of Nov 6, 2026 · OSV.dev, NVD, FIRST.org (EPSS)

Exploitation Status

No confirmed exploitation observed yet

CISA’s own triage has not observed active exploitation or public proof-of-concept code for this CVE as of its last assessment.

Exploitation and automatability from CISA’s SSVC triage for GHSA-4cx5-89vm-833x.

EPSS Exploitation Probability

via FIRST.org ↗

1.1%probability of exploitation in next 30 days

Lower Risk0.00%

Lower risk than most CVEs66th percentile — riskier than 66% of all scored CVEsHighest risk

Probability of exploitation in the next 30 days, from FIRST.org EPSS.

Real-World Exposure

9 pkgs affected

☕org.verapdf:core☕org.verapdf:core-jakarta☕org.verapdf:core-arlington☕org.verapdf:verapdf-library☕org.verapdf:verapdf-library-jakarta☕org.verapdf:verapdf-library-arlington☕org.verapdf:library☕org.verapdf:library-jakarta+1 more

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

veraPDF is an open source PDF/A validation library. Executing policy checks using custom schematron files via the CLI invokes an XSL transformation that may theoretically lead to a remote code execution (RCE) vulnerability. This doesn't affect the standard validation and policy checks functionality, veraPDF's common use cases. Most veraPDF users don't insert any custom XSLT code into policy profiles, which are based on Schematron syntax rather than direct XSL transforms. For users who do, only load custom policy files from sources you trust. This issue has not yet been patched. Users are advised to be cautious of XSLT code until a patch is available.

Affected Packages

9 total 9 fixed

Ecosystem	Package	Vulnerable range	Fix
☕Maven	`org.verapdf:core`	all versions	1.26.2`org.verapdf:core:1.26.2`
☕Maven	`org.verapdf:core-jakarta`	all versions	1.26.2`org.verapdf:core-jakarta:1.26.2`
☕Maven	`org.verapdf:core-arlington`	all versions	1.26.2`org.verapdf:core-arlington:1.26.2`
☕Maven	`org.verapdf:verapdf-library`	all versions	1.26.2`org.verapdf:verapdf-library:1.26.2`
☕Maven	`org.verapdf:verapdf-library-jakarta`	all versions	1.26.2`org.verapdf:verapdf-library-jakarta:1.26.2`
☕Maven	`org.verapdf:verapdf-library-arlington`	all versions	1.26.2`org.verapdf:verapdf-library-arlington:1.26.2`

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:core, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update org.verapdf:core to 1.26.2 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-4cx5-89vm-833x 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.

Frequently Asked Questions

### Impact Executing policy checks using custom schematron files via the CLI invokes an XSL transformation that may theoretically lead to a remote code execution (RCE) vulnerability. ### Patches We are currently working on a patch that will be released when ready. ### Workarounds This doesn't affect the standard validation and policy checks functionality, veraPDF's common use cases. Most veraPDF users don't insert any custom XSLT code into policy profiles, which are based on Schematron syntax rather than direct XSL transforms. For users who do, only load custom policy files from sources you

O3 Security · Impact-Aware SCA

Is GHSA-4cx5-89vm-833x in your dependencies?

Find it across Maven, including transitive dependencies.

Scan my dependencies How O3 SCA works