# Apache Ivy External Entity Reference vulnerability Advisory record · `GHSA-2jc4-r94c-rp7h` - **Identifiers:** `GHSA-2jc4-r94c-rp7h` · `CVE-2022-46751` - **State:** Confirmed - **Severity:** CVSS 8.2 High - **Critical:** No - **Weakness (CWE):** [CWE-91](https://cwe.mitre.org/data/definitions/91.html) · [CWE-611](https://cwe.mitre.org/data/definitions/611.html) - **Tags:** [Other injection](https://agentprime.io/advisories/tag/injection.md) · [XML external entities (XXE)](https://agentprime.io/advisories/tag/xxe.md) - **Published:** 21 Aug 2023 - **Updated:** 10 Sept 2026 - **Reviewed by a person:** No Published by the GitHub Advisory Database at 21 Aug 2023, 09:30 UTC. agentprime has not analysed this yet, so whether it affects any app is not known. ## Affected packages - `org.apache.ivy:ivy` (Maven): affected `<2.5.2`; fixed in `2.5.2` ## Machine-written summary Summary written by Claude Haiku from the source advisory. Not reviewed by a person. > Apache Ivy versions before 2.5.2 are affected. When Ivy parses XML files, including its own configuration, Ivy files, or Maven POMs, it downloads external document type definitions and expands entity references in them, which is an XML external entity issue. An attacker who can supply such an XML file to Ivy could use this to exfiltrate data, reach resources the machine running Ivy can access, or disrupt Ivy's execution. Upgrade to Ivy 2.5.2 or later. Users unable to upgrade can restrict external DTD processing using Java system properties described in Oracle's JAXP Security Guide. Written 2 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.2 High, CVSS 3.1: `CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:L`, from GitHub Advisory Database - **CISA KEV:** Not listed. - **EPSS:** 0.020, the 80th percentile, on 10 Nov 2026: FIRST’s estimate of the chance of exploitation in the next 30 days. ## Timeline - 21 Aug 2023, 07:15 UTC: [Confirmed by NVD](https://nvd.nist.gov/vuln/detail/CVE-2022-46751) - 31 Oct 2026, 14:18 UTC: First seen by agentprime - 31 Oct 2026, 14:18 UTC: [Confirmed by OSV](https://osv.dev/vulnerability/GHSA-2jc4-r94c-rp7h) ## Sources - [GitHub Advisory Database: GHSA-2jc4-r94c-rp7h](https://github.com/advisories/GHSA-2jc4-r94c-rp7h) - [OSV: GHSA-2jc4-r94c-rp7h](https://osv.dev/vulnerability/GHSA-2jc4-r94c-rp7h) - - - - - - - - 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: .