VulertSecurity VulertSecurity

Vulnerability Database · PyPI · Package report

sqlfluff: vulnerability history, versions and safety

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

i
6 vulnerabilities recorded H2 M1 U3
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 09 Jun 2026.

See the disclosure history →
i
0 malicious-package vulnerabilities

No published version shipped hostile code.

See all sqlfluff vulnerabilities

Vulert verdict on sqlfluff 4.4.0 i

Updated on 23 Oct 2026

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

Package health score 73/100
  • Security Some issues to review
  • Maintenance Sustainable
  • Popularity Widely used
  • Community Moderate

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

  • Current release 4.4.0 — unaffected i
  • Vulnerabilities on record 6 over 2 years · 4 in the last year i
  • Latest disclosure 09 Jun 2026 i
  • Highest CVSS 7.5 i
  • With no published fix 0 i
  • Depended on by 84 packages i
  • Stars 9,989 i
  • OpenSSF scorecard 4/10 i
  • Last release this month i
  • Licence non-standard 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 sqlfluff, 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.4.0 02 Oct 2026 none non-standard — Details →
4.3.0 07 Aug 2026 none non-standard — Details →
4.2.2 04 Jun 2026 none non-standard — Details →
4.2.1 14 May 2026 none non-standard — Details →
4.2.0 13 May 2026 none non-standard — Details →
4.1.0 26 Mar 2026 H1 U1 non-standard Yes Details →
4.0.4 09 Feb 2026 H2 U2 non-standard Yes Details →
4.0.4a1 08 Feb 2026 H2 U2 non-standard Yes Details →
4.0.3 08 Feb 2026 H2 U2 non-standard Yes Details →
4.0.1.post1 08 Feb 2026 H2 U2 non-standard Yes Details →
4.0.0 15 Jan 2026 H2 U2 non-standard Yes Details →
4.0.0a3 14 Jan 2026 H2 U2 non-standard Yes Details →
4.0.0a2 12 Nov 2025 H2 U2 non-standard Yes Details →
4.0.0a1 28 Oct 2025 H2 U2 non-standard Yes Details →
3.5.0 18 Oct 2025 H2 U2 non-standard Yes Details →
3.4.2 11 Jul 2025 H2 U2 non-standard Yes Details →
3.4.1 13 Jun 2025 H2 U2 non-standard Yes Details →
3.4.0 17 Apr 2025 H2 U2 non-standard Yes Details →
3.3.1 05 Feb 2025 H2 U2 non-standard Yes Details →
3.3.0 10 Dec 2024 H2 U2 non-standard Yes Details →
3.2.5 25 Oct 2024 H2 U2 non-standard Yes Details →
3.2.4 14 Oct 2024 H2 U2 non-standard Yes Details →
3.2.3 10 Oct 2024 H2 U2 non-standard Yes Details →
3.2.2 07 Oct 2024 H2 U2 non-standard Yes Details →
3.2.1 06 Oct 2024 H2 U2 non-standard Yes Details →
3.2.0 18 Sep 2024 H2 U2 non-standard Yes Details →
3.1.1 20 Aug 2024 H2 U2 non-standard Yes Details →
3.1.0 03 Jul 2024 H2 U2 non-standard Yes Details →
3.0.7 23 May 2024 H2 U2 non-standard Yes Details →
3.0.6 06 May 2024 H2 U2 non-standard Yes Details →
3.0.5 19 Apr 2024 H2 U2 non-standard Yes Details →
3.0.4 09 Apr 2024 H2 U2 non-standard Yes Details →
3.0.3 22 Mar 2024 H2 U2 non-standard Yes Details →
3.0.2 17 Mar 2024 H2 U2 non-standard Yes Details →
3.0.1 13 Mar 2024 H2 U2 non-standard Yes Details →
3.0.0 12 Mar 2024 H2 U2 non-standard Yes Details →
3.0.0a6 05 Mar 2024 H2 U2 non-standard Yes Details →
3.0.0a5 30 Jan 2024 H2 U2 non-standard Yes Details →
3.0.0a4 05 Dec 2023 H2 U2 non-standard Yes Details →
3.0.0a3 29 Nov 2023 H2 U2 non-standard Yes Details →
3.0.0a2 09 Nov 2023 H2 U2 non-standard Yes Details →
3.0.0a1 08 Nov 2023 H2 U2 non-standard Yes Details →
2.3.5 27 Oct 2023 H2 U2 MIT Yes Details →
2.3.4 17 Oct 2023 H2 U2 MIT Yes Details →
2.3.3 13 Oct 2023 H2 U2 MIT Yes Details →
2.3.2 10 Sep 2023 H2 U2 MIT Yes Details →
2.3.1 29 Aug 2023 H2 U2 MIT Yes Details →
2.3.0 14 Aug 2023 H2 U2 MIT Yes Details →
2.2.1 09 Aug 2023 H2 U2 MIT Yes Details →
2.2.0 04 Aug 2023 H2 U2 MIT Yes Details →
2.1.4 25 Jul 2023 H2 U2 MIT Yes Details →
2.1.3 19 Jul 2023 H2 U2 MIT Yes Details →
2.1.2 03 Jul 2023 H2 U2 MIT Yes Details →
2.1.1 25 May 2023 H2 M1 U3 MIT Yes Details →
2.1.0 03 May 2023 H2 M1 U3 MIT Yes Details →
2.0.7 20 Apr 2023 H2 M1 U3 MIT Yes Details →
2.0.6 20 Apr 2023 H2 M1 U3 MIT Yes Details →
2.0.5 14 Apr 2023 H2 M1 U3 MIT Yes Details →
2.0.4 14 Apr 2023 H2 M1 U3 MIT Yes Details →
2.0.3 05 Apr 2023 H2 M1 U3 MIT Yes Details →
2.0.2 23 Mar 2023 H2 M1 U3 MIT Yes Details →
2.0.1 18 Mar 2023 H2 M1 U3 MIT Yes Details →
2.0.0 14 Mar 2023 H2 M1 U3 MIT Yes Details →
2.0.0a6 07 Mar 2023 H2 M1 U3 MIT Yes Details →
2.0.0a5 25 Feb 2023 H2 M1 U3 MIT Yes Details →
2.0.0a4 27 Jan 2023 H2 M1 U3 MIT Yes Details →
2.0.0a3 16 Jan 2023 H2 M1 U3 MIT Yes Details →
2.0.0a2 07 Jan 2023 H2 M1 U3 MIT Yes Details →
2.0.0a1 28 Dec 2022 H2 M1 U3 MIT Yes Details →
1.4.5 19 Dec 2022 H2 M1 U3 MIT Yes Details →
1.4.4 14 Dec 2022 H2 M1 U3 MIT Yes Details →
1.4.3 14 Dec 2022 H2 M1 U3 MIT Yes Details →
1.4.2 13 Nov 2022 H2 M1 U3 MIT Yes Details →
1.4.1 31 Oct 2022 H2 M1 U3 MIT Yes Details →
1.4.0 31 Oct 2022 H2 M1 U3 MIT Yes Details →
1.3.2 27 Sep 2022 H2 M1 U3 MIT Yes Details →
1.3.1 09 Sep 2022 H2 M1 U3 MIT Yes Details →
1.3.0 21 Aug 2022 H2 M1 U3 MIT Yes Details →
1.2.1 15 Jul 2022 H2 M1 U3 MIT Yes Details →
1.2.0 13 Jul 2022 H2 M1 U3 MIT Yes Details →
1.1.0 03 Jul 2022 H2 M1 U3 MIT Yes Details →
1.0.0 17 Jun 2022 H2 M1 U3 MIT Yes Details →
0.13.2 20 May 2022 H2 M1 U3 MIT Yes Details →
0.13.1 06 May 2022 H2 M1 U3 MIT Yes Details →
0.13.0 22 Apr 2022 H2 M1 U3 MIT Yes Details →
0.12.0 07 Apr 2022 H2 M1 U3 MIT Yes Details →
0.11.2 25 Mar 2022 H2 M1 U3 MIT Yes Details →
0.11.1 17 Mar 2022 H2 M1 U3 MIT Yes Details →
0.11.0 07 Mar 2022 H2 M1 U3 MIT Yes Details →
0.10.1 16 Feb 2022 H2 M1 U3 MIT Yes Details →
0.10.0 10 Feb 2022 H2 M1 U3 MIT Yes Details →
0.9.4 30 Jan 2022 H2 M1 U3 MIT Yes Details →
0.9.3 26 Jan 2022 H2 M1 U3 MIT Yes Details →
0.9.2 24 Jan 2022 H2 M1 U3 MIT Yes Details →
0.9.1 09 Jan 2022 H2 M1 U3 MIT Yes Details →
0.9.0 13 Dec 2021 H2 M1 U3 MIT Yes Details →
0.8.2 22 Nov 2021 H2 M1 U3 MIT Yes Details →
0.8.1 07 Nov 2021 H2 M1 U3 MIT Yes Details →
0.8.0 07 Nov 2021 H2 M1 U3 MIT Yes Details →
0.7.1 22 Oct 2021 H2 M1 U3 MIT Yes Details →
0.7.0 14 Oct 2021 H2 M1 U3 — Yes Details →
0.7.0a8 12 Oct 2021 H2 M1 U3 — Yes Details →
0.7.0a5 12 Oct 2021 H2 M1 U3 — Yes Details →
0.7.0a3 10 Oct 2021 H2 M1 U3 — Yes Details →
0.7.0a2 09 Oct 2021 H2 M1 U3 — Yes Details →
0.7.0a1 09 Oct 2021 H2 M1 U3 — Yes Details →
0.6.9 09 Oct 2021 H2 M1 U3 — Yes Details →
0.6.8 05 Oct 2021 H2 M1 U3 — Yes Details →
0.6.7 04 Oct 2021 H2 M1 U3 — Yes Details →
0.6.6 20 Sep 2021 H2 M1 U3 — Yes Details →
0.6.5 10 Sep 2021 H2 M1 U3 — Yes Details →
0.6.4 21 Aug 2021 H2 M1 U3 — Yes Details →
0.6.3 16 Aug 2021 H2 M1 U3 — Yes Details →
0.6.2 22 Jul 2021 H2 M1 U3 — Yes Details →
0.6.1 16 Jul 2021 H2 M1 U3 — Yes Details →
0.6.0 09 Jun 2021 H2 M1 U3 — Yes Details →
0.6.0a2 27 May 2021 H2 M1 U3 — Yes Details →
0.6.0a1 15 May 2021 H2 M1 U3 — Yes Details →
0.5.6 14 May 2021 H2 M1 U3 — Yes Details →
0.5.5 13 May 2021 H2 M1 U3 — Yes Details →

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

02 Disclosure history

How often vulnerabilities are recorded

  • 2023 2
  • 2026 4

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

03 Vulnerabilities

Recorded vulnerabilities for sqlfluff

The 5 most severe of 6 vulnerabilities recorded for this package

Search all 6 in the database →
Vulnerability Severity Fixed version ↓ Disclosed ↓
CVE-2026-46374: SQLFluff Parser Uncontrolled Resource Consumption Vulnerability 7.5 high 4.2.0 19 May 2026
CVE-2026-46373: SQLFluff Recursive Stack Overflow Vulnerability Leading to Denial of Service 7.5 high 4.1.0 19 May 2026
CVE-2026-46373: SQLFluff Denial of Service Vulnerability Due to Excessive Query Nesting 7.5 high 4.1.0 09 Jun 2026
CVE-2026-46374: SQLFluff Denial of Service Vulnerability Due to Malicious Query Submission 7.5 high 4.2.0 09 Jun 2026
CVE-2023-36830: SQLFluff Arbitrary Code Execution 6.3 medium 2.1.2 06 Jul 2023

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 sqlfluff

Is sqlfluff safe to use?

Vulert records 6 vulnerabilities for sqlfluff in PyPI: 0 critical, 2 high, 1 medium and 0 low, plus 3 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 sqlfluff's Vulert package health score?

Vulert scores sqlfluff 73/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 sqlfluff affected?

No. 4.4.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.

Which version of sqlfluff should I use?

4.4.0 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 sqlfluff have?

6 vulnerabilities are recorded for sqlfluff in the PyPI ecosystem: 0 critical, 2 high, 1 medium and 0 low, plus 3 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 sqlfluff vulnerabilities disclosed?

4 vulnerabilities were recorded for sqlfluff in the last 12 months, and the oldest entry in this database dates to 06 Jul 2023. 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 sqlfluff 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 sqlfluff for upcoming vulnerabilities?

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