Skip to main content
Mallory
← Back to News
internet-facing-service-vulnerabilitywidely-deployed-product-advisoryopen-source-dependency-vulnerabilitydetection-content-update

XXE Flaws in GeoServer WFS and Apache CXF Expose Servers to SSRF and Data Leakage

Vulnerability Disclosure · 3 sources · Updated 5mo ago · First seen Apr 7, 2026

XXE Flaws in GeoServer WFS and Apache CXF Expose Servers to SSRF and Data Leakage

GeoServer and Apache CXF disclosed separate XML External Entity vulnerabilities that could let attackers abuse unsafe XML parsing to access sensitive resources. In GeoServer, CVE-2025-30220 affects the Web Feature Service (WFS) through the GeoTools library, where in-memory XSD schema processing does not enforce GeoServer’s ENTITY_RESOLUTION_ALLOWLIST restriction. The flaw can enable information disclosure and server-side request forgery (SSRF) via malicious XML containing external entities or DTDs, with affected GeoServer versions including 2.27.0, 2.26.0 through 2.26.2, and versions up to 2.25.6.

Apache also disclosed CVE-2026-44618, an important-severity XXE flaw in the WS-Transfer functionality of Apache CXF caused by an insecure XML parser configuration. Affected versions include org.apache.cxf:cxf-rt-ws-transfer 4.2.0 before 4.2.1, 4.0.0 before 4.1.6, and all 3.6.x releases before 3.6.11. Vendors urged organizations to upgrade to fixed releases immediately; where GeoServer patching is delayed, defenders were advised to restrict access to WFS endpoints and monitor for suspicious XML requests and outbound activity consistent with SSRF attempts.

Do you run this?See affected versions and whether adversaries are exploiting it.
Check your exposure
Event timeline

How this story unfolded

Events from the most recent confirmed update back to the earliest known activity.

3 events · Jun 10, 2025 – May 22, 2026
  1. May 22, 20266mo ago

    Apache discloses CVE-2026-44618 in CXF WS-Transfer

    Apache disclosed CVE-2026-44618, an important-severity XXE vulnerability in Apache CXF's WS-Transfer functionality caused by insecure XML parser configuration. Affected versions include 4.2.0 before 4.2.1, 4.0.0 before 4.1.6, and all 3.6.x versions before 3.6.11, with upgrades recommended to the fixed releases.

  2. Jun 19, 20251y ago

    Kudelski details affected GeoServer versions and mitigation guidance

    Kudelski Security published technical analysis of CVE-2025-30220, identifying affected GeoServer versions including 2.27.0, 2.26.0 through 2.26.2, and versions up to 2.25.6. It advised immediate upgrades, restricting access to WFS endpoints if patching is delayed, and monitoring for suspicious XML and SSRF-related activity.

  3. Jun 10, 20251y ago

    GeoServer publishes advisory for CVE-2025-30220 XXE flaw

    GeoServer disclosed CVE-2025-30220, a high-severity XML External Entity vulnerability in its Web Feature Service caused by GeoTools schema processing bypassing the ENTITY_RESOLUTION_ALLOWLIST restriction. The issue can enable information disclosure and SSRF via malicious XML payloads using external entities or DTDs.

Linked entities

Related entities

Vulnerabilities, threat actors, malware, products, organizations, and breaches Mallory has linked to this story.

Open in app →
Do you run this?See whether adversaries are exploiting this yet, and where the affected versions run in your environment.
Check Your Exposure
Mallory platform

See the full picture, correlated to your attack surface.

This page covers what’s public. Mallory adds the parts that aren’t: which of your assets are affected, which threat actors are using it right now, and what to deploy next.

Exposure mappingMap indicators from this story to your assets and identify affected systems in minutes.
Threat actor evidenceEvery observed campaign, victim, and pivot linked to actors named in this story.
Associated malwareMalware, exploits, and IOCs connected to the activity described here.
Detection signaturesYARA, Sigma, and Snort rules deployed to your SIEM as soon as they’re published.
Scheduled alertsGet matching new stories delivered to your team as they break, not the next morning.
AI threadsAsk questions about this story and take action on the answers.