VulertSecurity VulertSecurity

Vulnerability Database · PyPI · Package report

zeep: vulnerability history, versions and safety

zeep is a package in the PyPI ecosystem. Vulert records 2 vulnerabilities for it across 7 releases, from Jun 2026 to Jul 2026. Each vulnerability names the versions it affects, the fixed version to move to, and a workaround where no fix has been published.

i
2 vulnerabilities recorded M1 U1
i
0 with no fix published

Every vulnerability has a patched version to move to.

i
2 in the last 12 months

Most recent disclosure 08 Jul 2026.

See the disclosure history →
i
0 malicious-package vulnerabilities

No published version shipped hostile code.

See all zeep vulnerabilities

Vulert verdict on zeep 4.3.3 i

Updated on 23 Oct 2026

Good news: 4.3.3, the version you would install today, has no known vulnerabilities. Older releases do — the table below lists all 2.

Package health score 81/100
  • Security Minor issues
  • Maintenance Sustainable
  • Popularity Widely used
  • Community Moderate

What to do: Stay on 4.3.3 or newer. This can change: a vulnerability disclosed tomorrow can affect 4.3.3 too — Vulert watches the package and alerts you if that happens. Monitor it with Vulert →

  • Current release 4.3.3 — unaffected i
  • Vulnerabilities on record 2 over 1 year · 2 in the last year i
  • Latest disclosure 08 Jul 2026 i
  • Highest CVSS 5.9 i
  • With no published fix 0 i
  • Depended on by 590 packages i
  • Stars 2,009 i
  • OpenSSF scorecard 5/10 i
  • Last release 4 months ago i
  • Licence MIT i

Version list, release dates, licence and dependants published by PyPI, refreshed 22 Oct 2026. Licence information is not legal advice.

Concerned about your application's security?

Vulert continues monitoring your dependencies and alerts you when new vulnerabilities are disclosed. No installation and no source-code access required.

01 Versions

Which versions are affected

Every version Vulert tracks for zeep, newest first, with the vulnerabilities recorded against each one. A version showing none has no vulnerability in the Vulert database — open it for the full picture on that release.

i
Version Released Vulert vulnerabilities Licence Fix published Details
4.3.3 18 Jun 2026 none MIT — Details →
4.3.2 15 Sep 2025 M1 U1 MIT Yes Details →
4.3.1 16 Oct 2024 M1 U1 MIT Yes Details →
4.3.0 13 Oct 2024 M1 U1 MIT Yes Details →
4.2.1 20 Nov 2022 M1 U1 MIT Yes Details →
4.2.0 03 Nov 2022 M1 U1 MIT Yes Details →
4.1.0 15 Aug 2021 M1 U1 MIT Yes Details →
4.0.0 12 Oct 2020 M1 U1 MIT Yes Details →
4.0.0b1 26 Sep 2020 none MIT — Details →
3.4.0 05 Jun 2019 none MIT — Details →
3.3.1 10 Mar 2019 none MIT — Details →
3.3.0 08 Mar 2019 none MIT — Details →
3.2.0 17 Dec 2018 none MIT — Details →
3.1.0 28 Jul 2018 none MIT — Details →
3.0.0 16 Jun 2018 none MIT — Details →
2.5.0 06 Jan 2018 none MIT — Details →
2.4.0 26 Aug 2017 none MIT — Details →
2.3.0 06 Aug 2017 none MIT — Details →
2.2.0 19 Jun 2017 none MIT — Details →
2.1.1 11 Jun 2017 none MIT — Details →
2.1.0 11 Jun 2017 none MIT — Details →
2.0.0 22 May 2017 none MIT — Details →
1.6.0 27 Apr 2017 none MIT — Details →
1.5.0 22 Apr 2017 none MIT — Details →
1.4.1 01 Apr 2017 none MIT — Details →
1.4.0 01 Apr 2017 none MIT — Details →
1.3.0 14 Mar 2017 none MIT — Details →
1.2.0 12 Mar 2017 none MIT — Details →
1.1.0 18 Feb 2017 none MIT — Details →
1.0.0 31 Jan 2017 none MIT — Details →
0.27.0 28 Jan 2017 none MIT — Details →
0.26.0 26 Jan 2017 none MIT — Details →
0.25.0 23 Jan 2017 none MIT — Details →
0.24.0 16 Dec 2016 none MIT — Details →
0.23.0 24 Nov 2016 none MIT — Details →
0.22.1 22 Nov 2016 none MIT — Details →
0.22.0 13 Nov 2016 none MIT — Details →
0.21.0 02 Nov 2016 none MIT — Details →
0.20.0 24 Oct 2016 none MIT — Details →
0.19.0 18 Oct 2016 none MIT — Details →
0.18.1 23 Sep 2016 none MIT — Details →
0.18.0 23 Sep 2016 none MIT — Details →
0.17.0 12 Sep 2016 none MIT — Details →
0.16.0 06 Sep 2016 none MIT — Details →
0.15.0 04 Sep 2016 none MIT — Details →
0.14.0 03 Aug 2016 none MIT — Details →
0.13.0 17 Jul 2016 none MIT — Details →
0.12.0 09 Jul 2016 none MIT — Details →
0.11.0 03 Jul 2016 none MIT — Details →
0.10.0 22 Jun 2016 none MIT — Details →
0.9.1 17 Jun 2016 none MIT — Details →
0.9.0 14 Jun 2016 none MIT — Details →
0.8.1 08 Jun 2016 none MIT — Details →
0.8.0 07 Jun 2016 none MIT — Details →
0.7.1 01 Jun 2016 none MIT — Details →
0.7.0 31 May 2016 none MIT — Details →
0.6.0 21 May 2016 none MIT — Details →
0.5.0 08 May 2016 none MIT — Details →
0.4.0 17 Apr 2016 none MIT — Details →
0.3.0 10 Apr 2016 none MIT — Details →
0.2.5 05 Apr 2016 none MIT — Details →
0.2.4 03 Apr 2016 none MIT — Details →
0.2.3 03 Apr 2016 none MIT — Details →
0.2.2 03 Apr 2016 none MIT — Details →
0.2.1 03 Apr 2016 none MIT — Details →
0.2.0 03 Apr 2016 none MIT — Details →
0.1.1 20 Mar 2016 none MIT — Details →
0.1.0 20 Mar 2016 none MIT — Details →

All 68 versions Vulert tracks for this package. Severity counts are the vulnerabilities recorded against that exact release.

02 Disclosure history

How often vulnerabilities are recorded

  • 2026 2

Counted by the year Vulert recorded each vulnerability — the same date the table below shows as disclosed. 2 of the 2 were recorded in the last 12 months.

03 Vulnerabilities

Recorded vulnerabilities for zeep

The 2 most severe of 2 vulnerabilities recorded for this package

Search all 2 in the database →
Vulnerability Severity Fixed version ↓ Disclosed ↓
Server-Side Request Forgery (SSRF) Vulnerability in Zeep Package 5.9 medium 4.3.3 19 Jun 2026
CVE-2026-58501: Zeep SOAP Client Vulnerability Allows External Entity Injection 5.9 medium 4.3.3 08 Jul 2026

Vulnerability wrong, a fix missing, or a package we should cover? Report it and we will fix the record. Report Vulnerability Provide Feedback

Updated: 23/Oct/2026 · Vulnerabilities in our DB: 524315

Subscribe to Vulert on Telegram
Daily digest of new CVEs, critical and high severity, affected packages and fixes — plus a weekly roundup.
Join the channel →

Questions

About zeep

Is zeep safe to use?

Vulert records 2 vulnerabilities for zeep in PyPI: 0 critical, 0 high, 1 medium and 0 low, plus 1 not yet rated. Every one of them has a published fix, so the practical answer is to run a supported release and keep it patched.

What is zeep's Vulert package health score?

Vulert scores zeep 81/100, which reads as in good shape. The score weighs the vulnerability record (40), maintenance and release cadence (25), adoption from dependents and stars (20) and community signals such as the OpenSSF scorecard and forks (15).

Is the latest version of zeep affected?

No. 4.3.3, the version you would install today, has no vulnerabilities on record against it. Earlier releases do — the version table above lists each release with what affects it.

Which version of zeep should I use?

4.3.3 is the version Vulert recommends for the affected releases. The version table above lists every release with the vulnerabilities recorded against it, so you can confirm the range you actually run.

How many vulnerabilities does zeep have?

2 vulnerabilities are recorded for zeep in the PyPI ecosystem: 0 critical, 0 high, 1 medium and 0 low, plus 1 not yet rated. The ledger on this page lists the same counts next to the date of the most recent disclosure.

How often are new zeep vulnerabilities disclosed?

2 vulnerabilities were recorded for zeep in the last 12 months, and the oldest entry in this database dates to 19 Jun 2026. Recency matters more than a lifetime total: it shows how actively new issues are being disclosed for the package you are considering.

Which versions of zeep are affected?

Each vulnerability on this page lists the affected version range and the fixed version to move to. Open the vulnerability for the version you actually run — fixes are specific to a release line, not to the package as a whole.

How do I monitor zeep for upcoming vulnerabilities?

Upload the manifest or SBOM for your application at vulert.com/scanner and Vulert keeps checking the zeep version you actually run against new disclosures, then alerts you when one affects it. There is no installation and no source-code access required.