VulertSecurity VulertSecurity

Vulnerability Database · PyPI · Package report

snowflake-sqlalchemy: vulnerability history, versions and safety

snowflake-sqlalchemy is a package in the PyPI ecosystem. Vulert records 2 vulnerabilities for it across 48 releases, from Jul 2026 to Sep 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 H1 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 10 Sep 2026.

See the disclosure history →
i
0 malicious-package vulnerabilities

No published version shipped hostile code.

See all snowflake-sqlalchemy vulnerabilities

Vulert verdict on snowflake-sqlalchemy 2.0.0 i

Updated on 23 Oct 2026

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

Package health score 78/100
  • Security Minor issues
  • Maintenance Sustainable
  • Popularity Niche
  • Community Moderate

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

  • Current release 2.0.0 — unaffected i
  • Vulnerabilities on record 2 over 1 year · 2 in the last year i
  • Latest disclosure 10 Sep 2026 i
  • Highest CVSS 8.3 i
  • With no published fix 0 i
  • Depended on by 98 packages i
  • Stars 271 i
  • Last release this month i
  • Licence Apache-2.0 i

Version list, release dates, licence and dependants published by PyPI, refreshed 23 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-sqlalchemy, 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.0.0 19 Oct 2026 none Apache-2.0 — Details →
2.0.0rc2 29 Sep 2026 none Apache-2.0 — Details →
2.0.0rc1 14 Sep 2026 none Apache-2.0 — Details →
1.11.1 04 Sep 2026 none Apache-2.0 — Details →
2.0.0a2 20 Aug 2026 none Apache-2.0 — Details →
2.0.0a0 16 Jul 2026 none Apache-2.0 — Details →
1.11.0 08 Jul 2026 none Apache-2.0 — Details →
1.10.2 22 Jun 2026 H1 U1 Apache-2.0 Yes Details →
1.10.1 15 Jun 2026 H1 U1 Apache-2.0 Yes Details →
1.10.0 21 May 2026 H1 U1 Apache-2.0 Yes Details →
1.9.0 04 Mar 2026 H1 U1 Apache-2.0 Yes Details →
1.8.2 10 Dec 2025 H1 U1 Apache-2.0 Yes Details →
1.8.0 04 Dec 2025 H1 U1 Apache-2.0 Yes Details →
1.7.7 09 Sep 2025 H1 U1 Apache-2.0 Yes Details →
1.7.6 10 Jul 2025 H1 U1 Apache-2.0 Yes Details →
1.7.5 24 Jun 2025 H1 U1 Apache-2.0 Yes Details →
1.7.4 10 Jun 2025 H1 U1 Apache-2.0 Yes Details →
1.7.3 14 Jan 2025 H1 U1 Apache-2.0 Yes Details →
1.7.2 17 Dec 2024 H1 U1 Apache-2.0 Yes Details →
1.7.1 04 Dec 2024 H1 U1 Apache-2.0 Yes Details →
1.7.0 21 Nov 2024 H1 U1 Apache-2.0 Yes Details →
1.6.1 09 Jul 2024 H1 U1 Apache-2.0 Yes Details →
1.5.3 17 Apr 2024 H1 U1 Apache-2.0 Yes Details →
1.5.2 11 Apr 2024 H1 U1 Apache-2.0 Yes Details →
1.5.1 02 Nov 2023 H1 U1 Apache-2.0 Yes Details →
1.5.0 24 Aug 2023 H1 U1 Apache-2.0 Yes Details →
1.4.7 21 Mar 2023 H1 U1 Apache-2.0 Yes Details →
1.4.6 09 Feb 2023 H1 U1 Apache-2.0 Yes Details →
1.4.5 09 Dec 2022 H1 U1 Apache-2.0 Yes Details →
1.4.4 16 Nov 2022 H1 U1 Apache-2.0 Yes Details →
1.4.3 17 Oct 2022 H1 U1 Apache-2.0 Yes Details →
1.4.2 28 Sep 2022 H1 U1 Apache-2.0 Yes Details →
1.4.1 23 Aug 2022 H1 U1 Apache-2.0 Yes Details →
1.4.0 21 Jul 2022 H1 U1 Apache-2.0 Yes Details →
1.3.4 27 Apr 2022 H1 U1 Apache-2.0 Yes Details →
1.3.3 16 Dec 2021 H1 U1 Apache-2.0 Yes Details →
1.3.2 14 Sep 2021 H1 U1 Apache-2.0 Yes Details →
1.3.1 24 Jul 2021 H1 U1 Apache-2.0 Yes Details →
1.2.5 20 Jul 2021 H1 U1 Apache-2.0 Yes Details →
1.2.4 05 Oct 2020 H1 U1 Apache-2.0 Yes Details →
1.2.3 31 Mar 2020 H1 U1 Apache-2.0 Yes Details →
1.2.2 10 Mar 2020 H1 U1 Apache-2.0 Yes Details →
1.2.1 19 Feb 2020 H1 U1 Apache-2.0 Yes Details →
1.2.0 28 Jan 2020 H1 U1 Apache-2.0 Yes Details →
1.1.18 07 Jan 2020 H1 U1 Apache-2.0 Yes Details →
1.1.17 02 Dec 2019 H1 U1 Apache-2.0 Yes Details →
1.1.16 22 Oct 2019 H1 U1 Apache-2.0 Yes Details →
1.1.15 30 Sep 2019 H1 U1 Apache-2.0 Yes Details →
1.1.14 12 Aug 2019 H1 U1 Apache-2.0 Yes Details →
1.1.13 20 May 2019 H1 U1 Apache-2.0 Yes Details →
1.1.12 09 Apr 2019 H1 U1 Apache-2.0 Yes Details →
1.1.11 26 Mar 2019 H1 U1 Apache-2.0 Yes Details →
1.1.10 22 Feb 2019 H1 U1 Apache-2.0 Yes Details →
1.1.9 11 Feb 2019 H1 U1 Apache-2.0 Yes Details →
1.1.6 04 Jan 2019 H1 U1 Apache-2.0 Yes Details →
1.1.5 19 Dec 2018 none Apache-2.0 — Details →
1.1.4 13 Nov 2018 none Apache-2.0 — Details →
1.1.3 30 Oct 2018 none Apache-2.0 — Details →
1.1.2 07 Jun 2018 none Apache-2.0 — Details →
1.1.1 17 May 2018 none Apache-2.0 — Details →
1.1.0 01 Feb 2018 none Apache-2.0 — Details →
1.0.9 04 Jan 2018 none Apache-2.0 — Details →
1.0.8 21 Dec 2017 none Apache-2.0 — Details →
1.0.7 18 May 2017 none Apache-2.0 — Details →

All 64 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 snowflake-sqlalchemy

The 1 most severe of 2 vulnerabilities recorded for this package

Search all 2 in the database →
Vulnerability Severity Fixed version ↓ Disclosed ↓
CVE-2026-15736: Snowflake SQLAlchemy SQL Injection and Local File Disclosure Vulnerabilities 8.3 high 1.11.0 10 Sep 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 snowflake-sqlalchemy

Is snowflake-sqlalchemy safe to use?

Vulert records 2 vulnerabilities for snowflake-sqlalchemy in PyPI: 0 critical, 1 high, 0 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 snowflake-sqlalchemy's Vulert package health score?

Vulert scores snowflake-sqlalchemy 78/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 snowflake-sqlalchemy affected?

No. 2.0.0, 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.

How many vulnerabilities does snowflake-sqlalchemy have?

2 vulnerabilities are recorded for snowflake-sqlalchemy in the PyPI ecosystem: 0 critical, 1 high, 0 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 snowflake-sqlalchemy vulnerabilities disclosed?

2 vulnerabilities were recorded for snowflake-sqlalchemy in the last 12 months, and the oldest entry in this database dates to 14 Jul 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 snowflake-sqlalchemy 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-sqlalchemy for upcoming vulnerabilities?

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