VulertSecurity VulertSecurity

Vulnerability Database · PyPI · Package report

swift: vulnerability history, versions and safety

swift is a package in the PyPI ecosystem. Vulert records 28 vulnerabilities for it across 57 releases, from Jan 2014 to Oct 2026. Each vulnerability names the versions it affects, the fixed version to move to, and a workaround where no fix has been published.

i
28 vulnerabilities recorded C1 H5 M7 L1 U14
i
4 with no fix published

No patched version yet — these are the ones to plan around.

See the unfixed vulnerabilities →
i
15 in the last 12 months

Most recent disclosure 01 Oct 2026.

See the disclosure history →
i
0 malicious-package vulnerabilities

No published version shipped hostile code.

See all swift vulnerabilities

Vulert verdict on swift 2.38.3 i

Updated on 22 Oct 2026

Careful: 2.38.3 has 4 known vulnerabilities, and 4 have no fix yet. Use an earlier safe version, or the workaround listed for each one.

Package health score 48/100
  • Security Unfixed issues
  • Maintenance Sustainable
  • Popularity Not enough data
  • Community Not enough data

The current release has a vulnerability with no published fix, which caps this score.

What to do: Pin an earlier, unaffected release if you can, and apply the workaround each vulnerability lists until a fix is published. No fix yet: Vulert alerts you the moment one is published. Monitor it with Vulert →

  • Current release 2.38.3 — affected i
  • Vulnerabilities on record 28 over 12 years · 15 in the last year i
  • Latest disclosure 01 Oct 2026 i
  • Highest CVSS 9.8 i
  • With no published fix 4 i
  • Last release this month i
  • Licence non-standard 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 swift, 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
2.37.4 21 Oct 2026 H2 U2 non-standard No Details →
2.36.4 21 Oct 2026 H2 M1 U3 non-standard No Details →
2.38.3 21 Oct 2026 H2 U2 non-standard No Details →
2.35.5 21 Oct 2026 H1 M1 U2 non-standard No Details →
2.38.2 25 Sep 2026 H2 U2 non-standard No Details →
2.37.3 20 Aug 2026 H2 U2 non-standard No Details →
2.38.1 20 Aug 2026 H2 U2 non-standard No Details →
2.36.3 20 Aug 2026 M1 U1 non-standard Yes Details →
2.35.4 20 Aug 2026 M1 U1 non-standard Yes Details →
2.38.0 09 Jul 2026 H2 U2 non-standard No Details →
2.37.2 09 Jul 2026 H2 U2 non-standard No Details →
2.36.2 09 Jul 2026 M1 U1 non-standard Yes Details →
2.35.3 09 Jul 2026 M1 U1 non-standard Yes Details →
2.37.1 20 Mar 2026 M1 U2 non-standard No Details →
2.35.2 30 Jan 2026 M1 U1 non-standard Yes Details →
2.36.1 30 Jan 2026 H1 M1 U2 non-standard No Details →
2.34.2 30 Jan 2026 M1 U1 non-standard Yes Details →
2.37.0 28 Jan 2026 M1 U2 non-standard No Details →
2.36.0 11 Sep 2025 H1 M1 U2 Apache-2.0 No Details →
2.35.1 28 Aug 2025 M1 U1 Apache-2.0 Yes Details →
2.33.1 25 Jul 2025 M1 U1 Apache-2.0 Yes Details →
2.34.1 25 Jul 2025 M1 U1 Apache-2.0 Yes Details →
2.35.0 14 Mar 2025 M1 U1 Apache-2.0 Yes Details →
2.32.1 24 Feb 2025 M1 U1 Apache-2.0 Yes Details →
2.34.0 12 Sep 2024 M1 U1 non-standard Yes Details →
2.33.0 15 Mar 2024 M1 U1 non-standard Yes Details →
2.32.0 01 Sep 2023 M1 U1 non-standard Yes Details →
2.31.1 10 Mar 2023 M1 U1 non-standard Yes Details →
2.28.1 02 Feb 2023 M1 U1 non-standard Yes Details →
2.31.0 31 Jan 2023 M1 U1 non-standard Yes Details →
2.29.2 31 Jan 2023 M1 U1 non-standard Yes Details →
2.30.1 31 Jan 2023 M1 U1 non-standard Yes Details →
2.30.0 24 Aug 2022 M1 U2 non-standard Yes Details →
2.29.1 21 Mar 2022 M1 U2 non-standard Yes Details →
2.29.0 14 Feb 2022 M1 U2 non-standard Yes Details →
2.25.2 01 Sep 2021 M2 U2 non-standard Yes Details →
2.28.0 27 Jul 2021 M2 U2 non-standard Yes Details →
2.23.3 04 Jun 2021 M2 U2 non-standard Yes Details →
2.27.0 18 Mar 2021 M2 U2 non-standard Yes Details →
2.25.1 09 Oct 2020 M2 U2 non-standard Yes Details →
2.23.2 09 Oct 2020 M2 U2 non-standard Yes Details →
2.26.0 18 Sep 2020 M2 U2 non-standard Yes Details →
2.25.0 20 Apr 2020 M2 U2 non-standard Yes Details →
2.24.0 03 Feb 2020 M2 U2 non-standard Yes Details →
2.19.2 26 Nov 2019 M2 U2 non-standard Yes Details →
2.21.1 26 Nov 2019 M2 U2 non-standard Yes Details →
2.23.1 22 Oct 2019 M2 U2 non-standard Yes Details →
2.23.0 03 Oct 2019 M2 U2 non-standard Yes Details →
2.22.0 22 Jul 2019 M2 U2 non-standard Yes Details →
2.21.0 25 Mar 2019 M2 U2 non-standard Yes Details →
2.19.1 25 Feb 2019 M2 U2 non-standard Yes Details →
2.17.1 25 Feb 2019 M2 U2 non-standard Yes Details →
2.15.2 25 Feb 2019 M2 U2 non-standard Yes Details →
2.20.0 17 Dec 2018 M2 U2 non-standard Yes Details →
1.0.2 22 Jul 2010 C1 H3 M6 L1 U11 Apache-2.0 Yes Details →
1.0.2-py2.6 — C1 H3 M6 L1 U11 — Yes Details →
1.0.2.linux-x86_64 — C1 H3 M6 L1 U11 — Yes Details →

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

02 Disclosure history

How often vulnerabilities are recorded

  • 2014 1
  • 2021 1
  • 2022 10
  • 2023 1
  • 2026 15

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

03 Vulnerabilities

Recorded vulnerabilities for swift

The 5 most severe of 28 vulnerabilities recorded for this package

Search all 28 in the database →
Vulnerability Severity Fixed version ↓ Disclosed ↓
CVE-2012-4406: OpenStack Object Storage (swift) Code Injection Vulnerability 9.8 critical 1.7.0 29 Jun 2026
CVE-2012-4406: OpenStack Object Storage (swift) Code Injection vulnerability 9.8 critical 1.7.0 17 May 2022
CVE-2016-0737: OpenStack Object Storage (Swift) Denial of Service Vulnerability 7.5 high 2.4.0 06 Jul 2026
CVE-2016-0737: OpenStack Object Storage (Swift) Denial of Service 7.5 high 2.4.0 17 May 2022
CVE-2016-0738: OpenStack Object Storage (Swift) Denial of Service Vulnerability 7.5 high 2.3.1 17 May 2022

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

Updated: 22/Oct/2026 · Vulnerabilities in our DB: 524173

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 swift

Is swift safe to use?

Vulert records 28 vulnerabilities for swift in PyPI: 1 critical, 5 high, 7 medium and 1 low, plus 14 not yet rated. 4 of them have no published fix yet, so those are the ones to avoid or mitigate.

What is swift's Vulert package health score?

Vulert scores swift 48/100, which reads as risky. 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). The current release has a vulnerability with no published fix, which caps this score.

Is the latest version of swift affected?

Yes. 2.38.3, the version you would install today, has 4 known vulnerabilities, and 4 has no published fix yet. Use an earlier unaffected release, or the workaround each vulnerability lists.

How many vulnerabilities does swift have?

28 vulnerabilities are recorded for swift in the PyPI ecosystem: 1 critical, 5 high, 7 medium and 1 low, plus 14 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 swift vulnerabilities disclosed?

15 vulnerabilities were recorded for swift in the last 12 months, and the oldest entry in this database dates to 23 Jan 2014. 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 swift 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 swift for upcoming vulnerabilities?

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