Advisory record · GHSA-4cx5-89vm-833x

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

CVSS 2.3 LowEPSS 0.011 · 66th percentile

Published by the GitHub Advisory Database at 2 Dec 2024, 17:15 UTC. agentprime has not analysed this yet, so whether it affects any app is not known.

PackageEcosystemAffectedFixed in
org.verapdf:coreMaven<1.26.21.26.2
org.verapdf:core-jakartaMaven<1.26.21.26.2
org.verapdf:core-arlingtonMaven<1.26.21.26.2
org.verapdf:verapdf-libraryMaven<1.26.21.26.2
org.verapdf:verapdf-library-jakartaMaven<1.26.21.26.2
org.verapdf:verapdf-library-arlingtonMaven<1.26.21.26.2
org.verapdf:libraryMaven<1.26.21.26.2
org.verapdf:library-jakartaMaven<1.26.21.26.2
org.verapdf:library-arlingtonMaven<1.26.21.26.2
Identifiers
GHSA-4cx5-89vm-833x · CVE-2024-52800
Weakness (CWE)
CWE-611
Published
2 Dec 2024
Updated
14 May 2026

Machine-written summary

Summary written by Claude Haiku from the source advisory. Not reviewed by a person.

veraPDF CLI and the org.verapdf Maven packages (core, library and related artifacts) before 1.26.2 are affected. Running policy checks with custom Schematron files can invoke an XSL transformation that may theoretically lead to remote code execution. The source gives few details on who can trigger it, and no fixed version is listed; the source says a patch is in progress. Standard validation is not affected, and users should only load custom policy files from trusted sources.

Written 3 Nov 2026.

Not analysed yet

We haven’t published our analysis of this Advisory yet. Once a person has reviewed it, this page will say what’s vulnerable, what has to be true for your app to be affected, and how to check.

Severity and exploitation

ScoreRatingCVSSVectorSource
2.3 Low 4.0 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 CNA (GitHub_M)
  • CISA KEV Not listed.
  • EPSS 0.011, the 66th percentile, on 9 Nov 2026: FIRST’s estimate of the chance of exploitation in the next 30 days.

Timeline

  1. 31 Oct 2026, 14:20 UTC First seen by agentprime
  2. 31 Oct 2026, 14:20 UTC Confirmed by OSV

Sources

Facts on this page come from the GitHub Advisory Database (CC-BY 4.0), OSV and the other sources listed, as published. We don’t reproduce full advisory descriptions, which can contain exploit code.