Potential XXE (XML External Entity Injection) vulnerability in veraPDF CLI
veraPDF-library
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| org.verapdf:core Maven |
|
|
| org.verapdf:core-jakarta Maven |
|
|
| org.verapdf:core-arlington Maven |
veraPDF-library
| Product | Affected | Fixed in |
|---|---|---|
| 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 |
|
|
| org.verapdf:library-arlington Maven |
|
|
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.
From the CVE record · GitHub_M
Running custom Schematron policy files through the CLI invokes an XSL transformation that may theoretically allow remote code execution. This requires a custom policy file containing XSLT code; standard validation and policy checks are not affected. The input does not specify authentication or user-interaction requirements.
Engineers using any listed Maven org.verapdf core, verapdf-library, or library package, including jakarta and arlington variants, below 1.26.2 should check their usage of custom policy files.