dbcve.org
SqlfluffApplication

CVE-2026-46373

HIGH · 7.5 CVSS v3.1 Published 2026-06-09
Fix available
A fix is available. Upgrade to 4.1.0 or later.
See remediation →
84/100
Remediation priority · High
Remotely reachable No privileges Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
SQLFluff is a modular SQL linter and auto-formatter with support for multiple dialects and templated code. Prior to version 4.1.0, in deployments where untrusted users can provide SQL queries to be linted, an untrusted user can submit a malicious query with deliberate excessive nesting to any application using the parser to trigger a Denial of Service through resource exhaustion. This issue has been patched in version 4.1.0.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · moderate confidence

SQLFluff versions prior to 4.1.0 contain a vulnerability in the SQL parser component where specially crafted SQL queries with excessive nesting depth can trigger unbounded resource consumption. When untrusted users submit malicious queries to an application using SQLFluff for linting, the parser enters a resource exhaustion state leading to denial of service.

MitigationUpgrade SQLFluff to version 4.1.0 or later. As a defense-in-depth measure, implement input validation to reject or truncate queries exceeding reasonable nesting depth limits before passing them to the linter, and apply rate limiting on query processing endpoints.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
SqlfluffApplication
Affected:< 4.1.0

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
None
User interaction
None
Scope
Unchanged
Confidentiality
None
Integrity
None
Availability
High

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Check if SQLFluff is installed
    Run 'pip show sqlfluff' or 'pip list | grep -i sqlfluff' to see if the package is present in your environment
    Affected if SQLFluff is not installed - the vulnerability does not apply
  2. Identify the installed SQLFluff version
    Run 'pip show sqlfluff' and note the Version field, or run 'sqlfluff --version'
    Affected if The version displayed is lower than 4.1.0 (e.g., 4.0.x, 3.x, 2.x, etc.)
  3. Determine if untrusted users can submit SQL to the linter
    Review your application architecture or configuration to see if external/untrusted users can send SQL queries to SQLFluff for linting (e.g., web application, API endpoint, or shared linting service)
    Affected if Untrusted or external users can submit SQL queries to be linted by your SQLFluff installation
  4. Check for resource limits on linting operations
    Review your SQLFluff configuration (e.g., pyproject.toml, .sqlfluff config file) or deployment environment for any timeout, memory limit, or nesting depth restrictions applied to linting operations
    Affected if No resource limits, timeouts, or nesting depth constraints are configured for SQLFluff linting

You are affected if SQLFluff version is below 4.1.0 AND untrusted users can submit SQL queries to your linter without resource limits or input validation.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Upgrade available Upgrade to 4.1.0 or later
Fixed in 4.1.0
Interim mitigation

Upgrade SQLFluff to version 4.1.0 or later. As a defense-in-depth measure, implement input validation to reject or truncate queries exceeding reasonable nesting depth limits before passing them to the linter, and apply rate limiting on query processing endpoints.

Recommended fix High confidence

sqlfluff 4.1.0

  1. Upgrade Sqlfluff to version 4.1.0 or later by running: pip install --upgrade sqlfluff
  2. Verify the upgrade was successful by running: sqlfluff --version
  3. Test that the linter still works correctly with your existing SQL files

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Sqlfluff Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing6.0 h
  • Review / QA2.0 h
14.0 hours of engineering $2,380
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,808.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-46373 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2026-46373 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data