# veraPDF has potential XSLT injection vulnerability when using policy files Advisory record · `GHSA-qxqf-2mfx-x8jw` - **Identifiers:** `GHSA-qxqf-2mfx-x8jw` · `CVE-2024-28109` - **State:** Confirmed - **Severity:** CVSS 8.1 High - **Critical:** No - **Weakness (CWE):** [CWE-91](https://cwe.mitre.org/data/definitions/91.html) - **Tags:** [Other injection](https://agentprime.io/advisories/tag/injection.md) - **Published:** 20 May 2024 - **Updated:** 14 May 2026 - **Reviewed by a person:** No Published by the GitHub Advisory Database at 20 May 2024, 14:57 UTC. agentprime has not analysed this yet, so whether it affects any app is not known. ## Affected packages - `org.verapdf:core` (Maven): affected `<1.24.2`; fixed in `1.24.2` - `org.verapdf:core-jakarta` (Maven): affected `<1.24.2`; fixed in `1.24.2` - `org.verapdf:core-arlington` (Maven): affected `<1.25.127`; fixed in `1.25.127` - `org.verapdf:verapdf-library-arlington` (Maven): affected `<1.25.127`; fixed in `1.25.127` - `org.verapdf:verapdf-library` (Maven): affected `<1.24.2`; fixed in `1.24.2` - `org.verapdf:verapdf-library-jakarta` (Maven): affected `<1.24.2`; fixed in `1.24.2` - `org.verapdf:library-arlington` (Maven): affected `<1.25.127`; fixed in `1.25.127` - `org.verapdf:library` (Maven): affected `<1.24.2`; fixed in `1.24.2` - `org.verapdf:library-jakarta` (Maven): affected `<1.24.2`; fixed in `1.24.2` ## Machine-written summary Summary written by Claude Haiku from the source advisory. Not reviewed by a person. > veraPDF's core, library and related Maven packages (org.verapdf) before 1.24.2, and the arlington variants before 1.25.127, are affected by a potential XSLT injection issue when executing policy checks with custom Schematron files, which may theoretically lead to remote code execution. The source does not describe the exact attacker preconditions. Upgrade to 1.24.2 or 1.25.127 for the affected packages. Standard validation and policy checks are not affected; if you use custom policy files, load only ones 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 - 8.1 High, CVSS 3.1: `CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:N`, from CNA (GitHub_M) - **CISA KEV:** Not listed. - **EPSS:** 0.010, the 64th percentile, on 14 Nov 2026: FIRST’s estimate of the chance of exploitation in the next 30 days. ## Timeline - 31 Oct 2026, 14:20 UTC: First seen by agentprime - 31 Oct 2026, 14:20 UTC: [Confirmed by OSV](https://osv.dev/vulnerability/GHSA-qxqf-2mfx-x8jw) ## Sources - [GitHub Advisory Database: GHSA-qxqf-2mfx-x8jw](https://github.com/advisories/GHSA-qxqf-2mfx-x8jw) - [OSV: GHSA-qxqf-2mfx-x8jw](https://osv.dev/vulnerability/GHSA-qxqf-2mfx-x8jw) - - - - - - - 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. ## Check whether this affects you A Match means an installed version is in the affected range above. Most don’t affect the app; agentprime hasn’t analysed this one yet. - With the agentprime MCP server (), ask your agent to check the project: `check_lockfile` sends a lockfile, `check_packages` a list of installed packages, and both return the Matches and the upgrades that clear them. `get_advisory` returns this record. Setup: - In a browser: reads your lockfile in the browser, never uploading it. - Whether it touches your code, with file and line: the Claude Code plugin, - As JSON: , or `POST https://api.agentprime.io/v1/match` with your packages () --- The web page: . Everything for agents: .