veraPDF CLI has potential XXE (XML External Entity Injection) vulnerability

Exploitation

No confirmed exploitation recorded. Patch Next marks exploitation only from CISA KEV.

CVSS 4.0

2.3 · CVSS:4.0/AV:N/AC:L/AT:P/PR:N/UI:P/VC:L/VI:L/VA:N/SC:N/SI:N/SA:N · score source

EPSS

• CVE-2024-52800: 1.11% estimated exploitation activity in the next 30 days; percentile 65.92 (FIRST EPSS, 2026-11-03). This is a model estimate, not proof of exploitation or customer exposure.

As published by the source; long descriptions are shortened.

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 trust. References Original issue: #1488

Published by the source

2 Dec 2024, 17:15 UTC

Last modified by the source

14 May 2026, 20:44 UTC

Source last checked

26 Oct 2026, 16:45 UTC

1. Revision 1 · created · 26 Oct 2026

   Published from ghsa record GHSA-4cx5-89vm-833x

Preview the exact text before you copy it. Commands are read-only suggestions; review them before running anything.

# Patch Next advisory brief: CVE-2024-52800

Advisory: veraPDF CLI has potential XXE (XML External Entity Injection) vulnerability
IDs: CVE-2024-52800, GHSA-4cx5-89vm-833x
Record: https://patchnext.com/advisories/cve-2024-52800 (revision 1, source checked 26 Oct 2026, 16:45 UTC)
Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected.
Severity: Low (CVSS 2.3)
Exploitation: no confirmed exploitation recorded. Patch Next confirms exploitation only from CISA KEV.
Vendor response: Vendor fix available; fixed versions by package: org.verapdf:verapdf-library-jakarta 1.26.2; org.verapdf:verapdf-library 1.26.2; org.verapdf:core 1.26.2; org.verapdf:core-arlington 1.26.2; org.verapdf:library 1.26.2; org.verapdf:core-jakarta 1.26.2; org.verapdf:verapdf-library-arlington 1.26.2; org.verapdf:library-jakarta 1.26.2; org.verapdf:library-arlington 1.26.2. A vendor fix does not mean a deployment is fixed.

## Affected components
- Maven org.verapdf:verapdf-library-jakarta: affected <= 1.26.1; fixed in 1.26.2
- Maven org.verapdf:verapdf-library: affected <= 1.26.1; fixed in 1.26.2
- Maven org.verapdf:core: affected <= 1.26.1; fixed in 1.26.2
- Maven org.verapdf:core-arlington: affected <= 1.26.1; fixed in 1.26.2
- Maven org.verapdf:library: affected <= 1.26.1; fixed in 1.26.2
- Maven org.verapdf:core-jakarta: affected <= 1.26.1; fixed in 1.26.2
- Maven org.verapdf:verapdf-library-arlington: affected <= 1.26.1; fixed in 1.26.2
- Maven org.verapdf:library-jakarta: affected <= 1.26.1; fixed in 1.26.2
- Maven org.verapdf:library-arlington: affected <= 1.26.1; fixed in 1.26.2

## Suggested inspection (read-only)
- Maven org.verapdf:verapdf-library-jakarta: check the installed version with your package manager.
- Maven org.verapdf:verapdf-library: check the installed version with your package manager.
- Maven org.verapdf:core: check the installed version with your package manager.
- Maven org.verapdf:core-arlington: check the installed version with your package manager.
- Maven org.verapdf:library: check the installed version with your package manager.
- Maven org.verapdf:core-jakarta: check the installed version with your package manager.
- Maven org.verapdf:verapdf-library-arlington: check the installed version with your package manager.
- Maven org.verapdf:library-jakarta: check the installed version with your package manager.
- Maven org.verapdf:library-arlington: 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:verapdf-library-jakarta, org.verapdf:verapdf-library, org.verapdf:core, org.verapdf:core-arlington, org.verapdf:library, org.verapdf:core-jakarta, org.verapdf:verapdf-library-arlington, org.verapdf:library-jakarta, org.verapdf:library-arlington.
- 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://github.com/advisories/GHSA-4cx5-89vm-833x (GitHub-reviewed advisory GHSA-4cx5-89vm-833x lists affected ranges: Maven org.verapdf:core >=0 =0 =0 =0 =0 =0 =0 =0 =0 <=1.26.1)

Commands are suggestions: review each one before running it.