Vulnerability Database · PyPI · Package report

snowflake-connector-python: vulnerability history, versions and safety

snowflake-connector-python is a package in the PyPI ecosystem. Vulert records 15 vulnerabilities for it across 120 releases, from Nov 2022 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
15 vulnerabilities recorded C1 H2 M4 U8
i
0 with no fix published

Every vulnerability has a patched version to move to.

i
4 in the last 12 months

Most recent disclosure 15 Oct 2026.

See the disclosure history →
i
0 malicious-package vulnerabilities

No published version shipped hostile code.

Vulert verdict on snowflake-connector-python 5.1.0 i

Updated on 23 Oct 2026

Action needed: 5.1.0 has 2 known vulnerabilities, but every one of them has a fix. Upgrade to the version listed below and you are clear.

Package health score 56/100
  • Security Some issues to review
  • Maintenance Sustainable
  • Popularity Little adoption
  • Community Inactive

What to do: Upgrade to the version that resolves each vulnerability below. Fix it, then keep watch: this version is affected today, and the next one may be too — Vulert alerts you when a new vulnerability lands. Monitor it with Vulert →

  • Current release 5.1.0 — affected i
  • Vulnerabilities on record 15 over 3 years · 4 in the last year i
  • Latest disclosure 15 Oct 2026 i
  • Highest CVSS 9.2 i
  • With no published fix 0 i
  • Stars 14 i
  • Last release this month i
  • Licence Apache-2.0 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 snowflake-connector-python, 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
5.1.0 21 Oct 2026 U2 Apache-2.0 Yes Details →
5.0.0 15 Oct 2026 U2 Apache-2.0 Yes Details →
5.0.0rc5 08 Oct 2026 U2 Apache-2.0 Yes Details →
4.8.0 30 Sep 2026 U2 Apache-2.0 Yes Details →
5.0.0rc4 30 Sep 2026 U2 Apache-2.0 Yes Details →
4.7.5 21 Sep 2026 U2 Apache-2.0 Yes Details →
4.7.4 16 Sep 2026 U2 Apache-2.0 Yes Details →
5.0.0rc3 10 Sep 2026 U2 Apache-2.0 Yes Details →
5.0.0rc2 04 Sep 2026 U2 Apache-2.0 Yes Details →
4.7.3 03 Sep 2026 U2 Apache-2.0 Yes Details →
5.0.0rc1 19 Aug 2026 U2 Apache-2.0 Yes Details →
4.7.2 07 Aug 2026 U1 Apache-2.0 Yes Details →
5.0.0b6 23 Jul 2026 U2 Apache-2.0 Yes Details →
5.0.0b5 16 Jul 2026 U2 Apache-2.0 Yes Details →
3.18.1 15 Jul 2026 U1 Apache-2.0 Yes Details →
4.7.1 15 Jul 2026 U1 Apache-2.0 Yes Details →
4.7.0 02 Jul 2026 U2 Apache-2.0 Yes Details →
5.0.0b4 01 Jul 2026 U2 Apache-2.0 Yes Details →
5.0.0b3 18 Jun 2026 U2 Apache-2.0 Yes Details →
4.6.0 28 May 2026 U2 Apache-2.0 Yes Details →
5.0.0b2 21 May 2026 U2 Apache-2.0 Yes Details →
4.5.0 12 May 2026 U2 Apache-2.0 Yes Details →
5.0.0b1 30 Apr 2026 U2 Apache-2.0 Yes Details →
4.4.0 25 Mar 2026 U2 Apache-2.0 Yes Details →
4.3.0 12 Feb 2026 U2 Apache-2.0 Yes Details →
4.2.0 07 Jan 2026 U2 Apache-2.0 Yes Details →
4.1.1 02 Dec 2025 U2 Apache-2.0 Yes Details →
4.1.0 19 Nov 2025 U2 Apache-2.0 Yes Details →
4.0.0 09 Oct 2025 U2 Apache-2.0 Yes Details →
3.18.0 06 Oct 2025 C1 U2 Apache-2.0 Yes Details →
3.17.4 22 Sep 2025 C1 U2 Apache-2.0 Yes Details →
3.17.3 03 Sep 2025 C1 U2 Apache-2.0 Yes Details →
3.17.2 20 Aug 2025 C1 U2 Apache-2.0 Yes Details →
3.17.1 14 Aug 2025 C1 U2 Apache-2.0 Yes Details →
3.17.0 14 Aug 2025 C1 U2 Apache-2.0 Yes Details →
3.16.0 01 Jul 2025 C1 U2 Apache-2.0 Yes Details →
3.15.0 28 Apr 2025 C1 U2 Apache-2.0 Yes Details →
3.14.1 21 Apr 2025 C1 U2 Apache-2.0 Yes Details →
3.14.0 04 Mar 2025 C1 U2 Apache-2.0 Yes Details →
3.13.2 30 Jan 2025 C1 U2 Apache-2.0 Yes Details →
3.13.1 29 Jan 2025 C1 U2 Apache-2.0 Yes Details →
3.13.0 24 Jan 2025 C1 H1 M2 U5 Apache-2.0 Yes Details →
3.12.4 04 Dec 2024 C1 H1 M2 U5 Apache-2.0 Yes Details →
3.12.3 24 Oct 2024 C1 H1 M2 U5 Apache-2.0 Yes Details →
3.12.2 11 Sep 2024 C1 H1 M3 U6 Apache-2.0 Yes Details →
3.12.1 20 Aug 2024 C1 H1 M3 U6 Apache-2.0 Yes Details →
3.12.0 24 Jul 2024 C1 H1 M3 U6 Apache-2.0 Yes Details →
3.11.0 18 Jun 2024 C1 H1 M3 U6 Apache-2.0 Yes Details →
3.10.1 21 May 2024 C1 H1 M3 U6 Apache-2.0 Yes Details →
3.10.0 29 Apr 2024 C1 H1 M3 U6 Apache-2.0 Yes Details →
3.9.1 22 Apr 2024 C1 H1 M3 U6 Apache-2.0 Yes Details →
3.9.0 18 Apr 2024 C1 H1 M3 U6 Apache-2.0 Yes Details →
3.8.1 09 Apr 2024 C1 H1 M3 U6 Apache-2.0 Yes Details →
3.8.0 04 Apr 2024 C1 H1 M3 U6 Apache-2.0 Yes Details →
3.7.1 22 Feb 2024 C1 H1 M3 U6 Apache-2.0 Yes Details →
3.7.0 26 Jan 2024 C1 H1 M3 U6 Apache-2.0 Yes Details →
3.6.0 07 Dec 2023 C1 H1 M3 U6 Apache-2.0 Yes Details →
3.5.0 13 Nov 2023 C1 H1 M3 U6 Apache-2.0 Yes Details →
3.4.1 10 Nov 2023 C1 H1 M3 U6 Apache-2.0 Yes Details →
3.4.0 02 Nov 2023 C1 H1 M3 U6 Apache-2.0 Yes Details →
3.3.1 18 Oct 2023 C1 H1 M3 U6 Apache-2.0 Yes Details →
3.3.0 12 Oct 2023 C1 H1 M3 U6 Apache-2.0 Yes Details →
3.2.1 03 Oct 2023 C1 H1 M3 U6 Apache-2.0 Yes Details →
3.3.0b1 13 Sep 2023 C1 H1 M3 U6 Apache-2.0 Yes Details →
3.2.0 07 Sep 2023 C1 H1 M3 U6 Apache-2.0 Yes Details →
3.1.1 29 Aug 2023 C1 H1 M3 U6 Apache-2.0 Yes Details →
3.1.0a2 01 Aug 2023 C1 H1 M3 U6 Apache-2.0 Yes Details →
3.1.0 31 Jul 2023 C1 H1 M3 U6 Apache-2.0 Yes Details →
3.1.0a1 25 Jul 2023 C1 H1 M3 U6 Apache-2.0 Yes Details →
3.0.4 25 May 2023 C1 H1 M3 U6 Apache-2.0 Yes Details →
3.0.3 20 Apr 2023 C1 H1 M3 U6 Apache-2.0 Yes Details →
3.0.2 23 Mar 2023 C1 H1 M3 U6 Apache-2.0 Yes Details →
3.0.1 01 Mar 2023 C1 H2 M3 U7 Apache-2.0 Yes Details →
3.0.0 30 Jan 2023 C1 H2 M3 U7 Apache-2.0 Yes Details →
2.9.0 14 Dec 2022 C1 H2 M3 U7 Apache-2.0 Yes Details →
2.8.3 29 Nov 2022 C1 H2 M3 U7 Apache-2.0 Yes Details →
2.8.2 19 Nov 2022 C1 H2 M3 U7 Apache-2.0 Yes Details →
2.8.1 02 Nov 2022 C1 H2 M4 U8 Apache-2.0 Yes Details →
2.8.0 27 Sep 2022 C1 H2 M4 U8 Apache-2.0 Yes Details →
2.7.12 25 Aug 2022 C1 H2 M4 U8 Apache-2.0 Yes Details →
2.7.11 28 Jul 2022 C1 H2 M3 U7 Apache-2.0 Yes Details →
2.7.10 25 Jul 2022 C1 H2 M3 U7 Apache-2.0 Yes Details →
2.7.9 24 Jun 2022 C1 H2 M3 U7 Apache-2.0 Yes Details →
2.7.8 26 May 2022 C1 H2 M3 U7 Apache-2.0 Yes Details →
2.7.7 27 Apr 2022 C1 H2 M3 U7 Apache-2.0 Yes Details →
2.7.6 18 Mar 2022 C1 H2 M3 U7 Apache-2.0 Yes Details →
2.7.5 16 Mar 2022 C1 H2 M3 U7 Apache-2.0 Yes Details →
2.7.4 02 Feb 2022 C1 H2 M3 U7 Apache-2.0 Yes Details →
2.7.3 20 Jan 2022 C1 H2 M3 U7 Apache-2.0 Yes Details →
2.7.2 17 Dec 2021 C1 H2 M3 U7 Apache-2.0 Yes Details →
2.7.1 17 Nov 2021 C1 H2 M3 U7 Apache-2.0 Yes Details →
2.7.0 25 Oct 2021 C1 H2 M3 U7 Apache-2.0 Yes Details →
2.6.2 27 Sep 2021 C1 H2 M3 U7 Apache-2.0 Yes Details →
2.6.1 14 Sep 2021 C1 H2 M3 U7 Apache-2.0 Yes Details →
2.6.0 27 Aug 2021 C1 H2 M3 U7 Apache-2.0 Yes Details →
2.5.1 28 Jul 2021 C1 H2 M3 U7 Apache-2.0 Yes Details →
2.5.0 20 Jul 2021 C1 H2 M3 U7 Apache-2.0 Yes Details →
2.4.6 22 Jun 2021 C1 H2 M3 U7 Apache-2.0 Yes Details →
2.4.5 15 Jun 2021 C1 H2 M3 U7 Apache-2.0 Yes Details →
2.4.4 28 May 2021 C1 H2 M3 U7 Apache-2.0 Yes Details →
2.4.3 26 Apr 2021 C1 H2 M3 U7 — Yes Details →
2.4.2 01 Apr 2021 C1 H2 M3 U7 — Yes Details →
2.4.1 04 Mar 2021 C1 H2 M3 U7 — Yes Details →
2.4.0 02 Mar 2021 C1 H2 M3 U7 — Yes Details →
2.3.10 01 Feb 2021 C1 H2 M3 U7 — Yes Details →
2.3.9 27 Jan 2021 C1 H2 M3 U7 — Yes Details →
2.3.8 12 Jan 2021 C1 H2 M3 U7 — Yes Details →
2.3.7 08 Dec 2020 C1 H2 M3 U7 — Yes Details →
2.3.6 17 Nov 2020 C1 H2 M2 U6 — Yes Details →
2.3.5 03 Nov 2020 C1 H2 M2 U6 — Yes Details →
2.3.4 27 Oct 2020 C1 H2 M2 U6 — Yes Details →
2.3.3 05 Oct 2020 C1 H2 M2 U6 — Yes Details →
2.3.2 14 Sep 2020 C1 H2 M2 U6 — Yes Details →
2.3.1 25 Aug 2020 C1 H2 M2 U6 — Yes Details →
2.3.0 24 Aug 2020 C1 H2 M2 U6 — Yes Details →
2.2.10 04 Aug 2020 C1 H2 M2 U6 — Yes Details →
2.2.9 15 Jul 2020 C1 H2 M2 U6 — Yes Details →
2.2.8 23 Jun 2020 C1 H2 M2 U6 — Yes Details →
2.2.7 01 Jun 2020 C1 H2 M2 U6 — Yes Details →
2.2.6 12 May 2020 C1 H2 M2 U6 — Yes Details →

The newest 120 of 191 versions Vulert tracks. Severity counts are the vulnerabilities recorded against that exact release.

02 Disclosure history

How often vulnerabilities are recorded

  • 2022 1
  • 2023 2
  • 2024 2
  • 2025 6
  • 2026 4

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

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 snowflake-connector-python

Is snowflake-connector-python safe to use?

Vulert records 15 vulnerabilities for snowflake-connector-python in PyPI: 1 critical, 2 high, 4 medium and 0 low, plus 8 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 snowflake-connector-python's Vulert package health score?

Vulert scores snowflake-connector-python 56/100, which reads as usable, but worth attention. 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 snowflake-connector-python affected?

Yes. 5.1.0, the version you would install today, has 2 known vulnerabilities, and every one of them has a published fix. Upgrade to the version listed for each.

How many vulnerabilities does snowflake-connector-python have?

15 vulnerabilities are recorded for snowflake-connector-python in the PyPI ecosystem: 1 critical, 2 high, 4 medium and 0 low, plus 8 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 snowflake-connector-python vulnerabilities disclosed?

4 vulnerabilities were recorded for snowflake-connector-python in the last 12 months, and the oldest entry in this database dates to 10 Nov 2022. 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 snowflake-connector-python 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 snowflake-connector-python for upcoming vulnerabilities?

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