SSRF (Server-Side Request Forgery) in zeep (CVE-2026-58501)
Summary
SSRF in zeep (CVE-2026-58501). Confidential information can be exposed externally. Mitigation: upgrade to 4.3.3 or later.
Original description
The description as published by the source.
Zeep is a Python SOAP client. From 4.0.0 before 4.3.3, Settings.forbid_external is defined but not enforced when parsing WSDL or XSD documents, allowing transitive xsd:import, xsd:include, wsdl:import, and lxml entity or DTD references to fetch attacker-chosen HTTP or HTTPS URLs. This issue is fixed in version 4.3.3.
Source: NIST National Vulnerability Database NVD GitHub Advisory
Auto-generated summary
Assembled by SecPulse from the source data (CVSS, CWE, affected versions) using templates — no AI involved. Check the original description and references below for exact details.
A vulnerability tracked as CVE-2026-58501 has been found in zeep.
Confidential information can be exposed externally. CVSS score: 5.9/10.
What to do: upgrade zeep to 4.3.3 or later.
If unsure, ask your IT team or search "zeep CVE-2026-58501" on the vendor's site.
CVE-2026-58501 (zeep) — CWE-918 / CVSS v3 5.9
Attack vector: remote (network-reachable) / unauthenticated / no user interaction
Patched: 4.3.3 — apply immediately
Plan: 1) Audit SBOM/dependencies, 2) Stage→prod upgrade, 3) Add WAF/proxy monitoring on affected endpoints, 4) Hunt IOCs in logs.
Refs: see the GHSA / vendor advisory / patched release linked on this page.
SSRF (CWE-918) exists in zeep.
Check the vendor advisory for the affected versions of zeep.
Severity: Medium (CVSS 5.9/10). Confidential information can be exposed externally.
Update to 4.3.3.
Until the patch is applied: disable the affected feature, apply WAF rules, or restrict access via network ACLs.
Search webserver/proxy logs for unusual request patterns matching this CVE's known IOCs. Run grep -r 'zeep' . against your dependency files (package-lock.json, requirements.txt, go.sum) to find affected services.
Response actions
Concrete steps and command examples for SOC/SRE teams to execute in order
-
1Identify exposure identify
grep -r 'zeep' . | grep -v node_modulesリポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で
zeepを grep し、稼働しているサービス・バージョンを把握する。 -
2Apply patch patch
Upgrade zeep to 4.3.3ステージング環境で 4.3.3 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスを含めること。
-
3Post-deployment verification verify
Confirm patched version is live in productionパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番ではアクセスログ・WAF でアラート再発が無いか継続監視。
Affected packages
Fix status by distribution
Fixed packages published by each distribution for this CVE
- Debian DEBIAN-CVE-2026-58501 python-zeep
- Ubuntu UBUNTU-CVE-2026-58501 python-zeep
References
- advisory github.com
- advisory github.com
- advisory nvd.nist.gov
- package github.com
- patch github.com
- web github.com