GHSA-qxqf-2mfx-x8jw veraPDF has potential XSLT injection vulnerability when using policy files

• Maven org.verapdf:core: < 1.24.2 → fixed in 1.24.2 • Maven org.verapdf:core-jakarta: < 1.24.2 → fixed in 1.24.2 • Maven org.verapdf:core-arlington: < 1.25.127 → fixed in 1.25.127 • Maven org.verapdf:verapdf-library-arlington: < 1.25.127 → fixed in 1.25.127 • Maven org.verapdf:verapdf-library: < 1.24.2 → fixed in 1.24.2 • Maven org.verapdf:verapdf-library-jakarta: < 1.24.2 → fixed in 1.24.2 • Maven org.verapdf:library-arlington: < 1.25.127 → fixed in 1.25.127 • Maven org.verapdf:library: < 1.24.2 → fixed in 1.24.2 • Maven org.verapdf:library-jakarta: < 1.24.2 → fixed in 1.24.2

Impact Executing policy checks using custom schematron files invokes an XSL transformation that may theoretically lead to a remote code execution (RCE) vulnerability. Patches This has been patched and users should upgrade to veraPDF v1.24.2 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: