Home › Intelligence › Brief
VULNERABILITY BRIEF🟠 High Vulnerability

Improper XML External Entity (XXE) in OSGeo GeoServer (CVE‑2025‑58360) Risks Map Service Integrity

OSGeo GeoServer’s WMS GetMap endpoint allows crafted XML that can trigger external entity processing, exposing file reads and potential SSRF. The flaw highlights gaps in input‑validation controls that auditors scrutinize for compliance readiness.

LiveThreat™ Intelligence · 📅 October 07, 2026· 📰 nvd.nist.gov
🟠
Severity
High
VU
Type
Vulnerability
🎯
Confidence
High
🏢
Affected
1 sector(s)
✅
Actions
4 recommended
📰
Source
nvd.nist.gov

Improper XML External Entity (XXE) in OSGeo GeoServer (CVE‑2025‑58360) Risks Map Service Integrity

What It Is – OSGeo GeoServer’s /geoserver/wms GetMap operation accepts XML input without proper restriction of external entity references, creating an XML External Entity (XXE) flaw. An attacker can embed malicious entities in the XML request to read arbitrary files or trigger SSRF‑style behavior.

Exploitability – Publicly disclosed; no known active exploit chain, but the vulnerability is trivial to weaponize with a crafted XML payload. CVSS v3.1 base score is 7.5 (High).

Affected Products – OSGeo GeoServer (all supported versions prior to the vendor‑issued fix).

Why It Matters for Trust & Control Assurance

  • Input‑validation controls must be demonstrably enforced; an XXE gap signals missing safeguards that auditors will flag under multiple frameworks.
  • Continuous evidence of secure configuration (e.g., disabled external entity processing) supports a defensible audit trail and shows due‑diligence to customers.
  • Remediation evidence can be ingested into a Trust Center, giving enterprises a single source of truth for compliance reporting.

Recommended Actions

  • Apply the OSGeo‑provided patch or upgrade to the first version that disables external entity processing for the WMS endpoint.
  • Verify that XML parsers are configured with disallow-doctype-decl or equivalent hardening flags.
  • Update your configuration‑management policies to require documented XML‑parsing controls and logging of parsing errors.
  • Capture remediation artifacts (patch version, configuration snapshots) for inclusion in your control‑evidence repository.

Source: CISA KEV – CVE‑2025‑58360

📰 Original Source
https://nvd.nist.gov/vuln/detail/CVE-2025-58360 ↗

This LiveThreat Intelligence Brief is an independent analysis. Read the original reporting at the link above.

From the Verisq platform · Trust Operations

Every gap like this maps to a control you can evidence.

The Verisq AI Trust Operations platform maps incidents to your control framework and collects the evidence continuously — so your Trust Center shows proof, not promises, when a buyer or auditor asks.

Explore the Verisq AI Trust Operations platform →