# GeoServer has improper ENTITY_RESOLUTION_ALLOWLIST URI validation in XML Processing (SSRF) Advisory record · `GHSA-mc43-4fqr-c965` - **Identifiers:** `GHSA-mc43-4fqr-c965` · `CVE-2024-34711` - **State:** Confirmed - **Severity:** CVSS 9.3 Critical - **Critical:** Yes: CVSS 9+ - **Weakness (CWE):** [CWE-20](https://cwe.mitre.org/data/definitions/20.html) · [CWE-200](https://cwe.mitre.org/data/definitions/200.html) · [CWE-611](https://cwe.mitre.org/data/definitions/611.html) · [CWE-918](https://cwe.mitre.org/data/definitions/918.html) - **Tags:** [Information disclosure](https://agentprime.io/advisories/tag/info-disclosure.md) · [XML external entities (XXE)](https://agentprime.io/advisories/tag/xxe.md) · [Server-side request forgery (SSRF)](https://agentprime.io/advisories/tag/ssrf.md) · [CWE-20](https://agentprime.io/advisories/tag/cwe-20.md) - **Published:** 10 Jun 2025 - **Updated:** 10 Jun 2025 - **Reviewed by a person:** No Published by the GitHub Advisory Database at 10 Jun 2025, 14:13 UTC. agentprime has not analysed this yet, so whether it affects any app is not known. ## Critical Critical, because: - CVSS score 9.3: 9.0 or more. How we decide what’s critical: ## Affected packages - `org.geoserver.web:gs-web-app` (Maven): affected `<2.25.0`; fixed in `2.25.0` - `org.geoserver.main:gs-main` (Maven): affected `<2.25.0`; fixed in `2.25.0` ## Machine-written summary Summary written by Claude Haiku from the source advisory. Not reviewed by a person. > GeoServer (org.geoserver.web:gs-web-app and org.geoserver.main:gs-main) before 2.25.0 has improper URI validation in its XML external entity filtering. An unauthenticated attacker can exploit this XXE flaw to make server-side requests to arbitrary HTTP servers, scan internal networks, and read limited .xsd files. Upgrade to 2.25.0 or later, which uses an allowlist by default; the source also notes that the ENTITY_RESOLUTION_ALLOWLIST system property can add schema locations. Written 7 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 - 9.3 Critical, CVSS 3.1: `CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:H/I:L/A:N`, from CNA (GitHub_M) - **CISA KEV:** Not listed. - **EPSS:** 0.0031, the 24th percentile, on 8 Nov 2026: FIRST’s estimate of the chance of exploitation in the next 30 days. ## Timeline - 31 Oct 2026, 15:11 UTC: First seen by agentprime - 31 Oct 2026, 15:11 UTC: [Confirmed by OSV](https://osv.dev/vulnerability/GHSA-mc43-4fqr-c965) ## Sources - [GitHub Advisory Database: GHSA-mc43-4fqr-c965](https://github.com/advisories/GHSA-mc43-4fqr-c965) - [OSV: GHSA-mc43-4fqr-c965](https://osv.dev/vulnerability/GHSA-mc43-4fqr-c965) - - - - 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: .