CVE-2026-46374
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 · uneditedSQLFluff is a modular SQL linter and auto-formatter with support for multiple dialects and templated code. Prior to version 4.2.0, in deployments where untrusted users can provide SQL queries to be linted, an untrusted user can submit a malicious long query to any application using the parser to trigger a Denial of Service through resource exhaustion. This issue has been patched in version 4.2.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 · high confidenceSQLFluff versions prior to 4.2.0 contain a denial of service vulnerability where untrusted users can submit maliciously long SQL queries to trigger resource exhaustion through the parser, affecting deployments where untrusted users can provide SQL queries to be linted.
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< 4.2.0CVSS 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 checksWork through these to decide whether this CVE applies to you.
-
Identify installed SQLFluff versionRun `pip show sqlfluff` or `pip list | grep -i sqlfluff` to retrieve the installed version numberAffected if The displayed version is lower than 4.2.0 (e.g., 4.1.0, 4.0.0, 3.x, etc.)
-
Verify SQLFluff is accessible to untrusted usersReview application code, API endpoints, or service configuration to determine whether SQLFluff linting functionality is exposed to unauthenticated or untrusted usersAffected if Untrusted users can submit SQL queries directly to the linting function without authentication or input sanitization
-
Check for query input controlsInspect application configuration files, middleware settings, or code that handles SQL input before passing to SQLFluffAffected if No input length limits or query size restrictions are enforced on SQL submissions
-
Test resource consumption behaviorSubmit an unusually large SQL query (e.g., >1MB) to the linting endpoint and observe server response time and resource usageAffected if The server becomes unresponsive, crashes, or exhibits significantly degraded performance when processing large queries
You are affected if SQLFluff version is below 4.2.0 AND untrusted users can submit SQL queries directly to your linting service without input size constraints.
Generated from the published advisory. Verify against your own configuration.
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 · scoped4.2.0
Upgrade SQLFluff to version 4.2.0 or later. Additionally, implement input validation and rate limiting on any endpoints that accept untrusted SQL queries for linting.
4.2.0
- Upgrade SQLFluff to version 4.2.0 or later using your package manager (e.g., pip install sqlfluff>=4.2.0 or conda install -c conda-forge sqlfluff>=4.2.0)
- Verify the upgrade was successful by running `sqlfluff --version` and confirming it shows 4.2.0 or higher
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation2.0 h
- Implementation1.0 h
- Testing2.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,696.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-46374 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2026-46374 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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