CVE-2026-58501: Zeep SOAP Client forbid_external Bypass Vulnerability

Technical summary

The vulnerability stems from incomplete implementation of the forbid_external security control in Zeep's WSDL and XSD document parser. While the setting is defined in the codebase, validation logic fails to check it when processing xsd:import, xsd:include, wsdl:import directives, and lxml entity or DTD expansion directives. This allows an attacker to include references to attacker-controlled resources in schema documents. When a vulnerable Zeep instance parses such documents—whether directly or transitively through imported schemas—it will resolve and fetch these external references regardless of the forbid_external configuration. The underlying cause is CWE-918 (Server-Side Request Forgery), where the application makes network requests on behalf of the user without proper authorization or validation controls.

Business impact

Organizations using Zeep to consume untrusted or third-party SOAP services face potential data exfiltration and reconnaissance risks. If an attacker can influence WSDL or XSD content consumed by an application—either by compromising a SOAP service provider, performing man-in-the-middle interception, or submitting malicious schema references—Zeep will fetch attacker-chosen URLs from the server running the application. This can be exploited for information disclosure (reading server responses, testing internal network connectivity, probing internal services), credential harvesting, or as a pivot point for further exploitation. The impact is elevated if the Zeep client runs on a server with access to sensitive internal resources or if it processes schemas from multiple external sources.

Affected systems

Python applications using Zeep library versions 4.0.0 through 4.3.2 are affected. This includes any deployment where Zeep is integrated to consume SOAP web services. Systems are at risk only if they parse WSDL or XSD documents from sources an attacker can influence or intercept. Applications that consume only trusted, internally-controlled SOAP services and never parse external schema documents have lower immediate risk, but configurations should still be verified. Verify your installed version by checking your Python environment or requirements file; the fix is available in Zeep 4.3.3 and later.

Exploitability

Exploitation requires that an attacker either control or influence the WSDL/XSD content that a Zeep client parses. The CVSS vector indicates network-based attack (AV:N) but with high complexity (AC:H), reflecting that successful exploitation depends on attacker ability to supply malicious schema content and knowledge of the target application's network environment. Exploitation does not require authentication or user interaction. The attack is not currently tracked in the CISA Known Exploited Vulnerabilities catalog, suggesting active exploitation in the wild has not yet been widely reported, though the technical barrier to exploitation is relatively low for attackers with schema control.

Remediation

Update Zeep to version 4.3.3 or later, which enforces the forbid_external setting correctly. Before patching, review SOAP service integrations to identify which are consuming external or untrusted schemas. For high-risk integrations, consider temporarily disabling or restricting access to the Zeep client until patches can be deployed. Additionally, ensure forbid_external is explicitly set to true in Zeep configuration for any client handling external schemas, and verify that the patched version actually enforces this setting in your environment. Monitor for suspicious outbound connections from application servers during and after remediation.

Patch guidance

Update the zeep package to version 4.3.3 or any version released after the fix. Use `pip install --upgrade zeep>=4.3.3` or update your requirements.txt/pyproject.toml and re-install. Verify the patched version is active in your Python environment by running `python -c "import zeep; print(zeep.__version__)"`. After patching, redeploy affected applications and confirm they restart cleanly with the new version. No breaking changes are expected in the patch; the fix corrects a configuration enforcement bug without API changes.

Detection guidance

Monitor outbound HTTP and HTTPS connections from Python application servers running Zeep, especially to unexpected destinations or internal IP ranges. Check application logs and proxy/firewall logs for requests originating from Zeep processes to external or suspicious URLs during SOAP client initialization or schema parsing operations. Audit current Zeep installations: use `pip show zeep` or examine requirements files to identify instances below version 4.3.3. Review SOAP service configurations to identify which applications consume external schemas and assess whether forbid_external is explicitly enabled. If available, enable HTTPS inspection and DNS logging to catch potential data exfiltration attempts via external schema references.

Why prioritize this

Although assigned MEDIUM severity (CVSS 5.9) and not yet in the known exploited vulnerabilities catalog, this issue should be prioritized for rapid patching because: (1) the exploit mechanism is straightforward for any attacker controlling or intercepting SOAP schema content; (2) applications consuming external SOAP services are increasingly common in enterprise integrations; (3) data exfiltration via SSRF can be silent and difficult to detect; (4) the fix is a simple version bump with no known breaking changes. Prioritize applications consuming schemas from third-party providers or over untrusted network paths first, then remediate all remaining instances as part of regular patch cycles.

Risk score, explained

The CVSS 5.9 MEDIUM score reflects high confidentiality impact (H) balanced against high attack complexity (H) and network-only attack surface (AV:N/AC:H). The complexity is elevated because successful exploitation depends on the attacker's ability to supply or influence WSDL/XSD content to the target application. However, in scenarios where an organization consumes untrusted third-party SOAP services or operates on networks vulnerable to interception, the practical risk is elevated. No integrity or availability impact is scored, limiting the severity ceiling. Organizations should apply their own risk context: applications on high-trust networks consuming only internal schemas may defer patching slightly, while those consuming external schemas should treat this as HIGH priority locally.

Frequently asked questions