Quick answers
- Is CVE-2026-46374 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-46374 being exploited in the wild.
- How severe is CVE-2026-46374?
- High severity, with a CVSS score of 7.5, published 9 June 2026.
- Which products and versions are affected?
- sqlfluff (PyPI) < 4.2.0, ECOSYSTEM:introduced=0,fixed=4.2.0.
- Is there a fix for CVE-2026-46374?
- Yes. sqlfluff (PyPI): upgrade to 4.2.0 or later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
- How is CVE-2026-46374 attacked?
- It is attacked over the network, in a software library.
- Am I affected by CVE-2026-46374?
- Check whether you run sqlfluff (PyPI) at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.
How to fix
- sqlfluff (PyPI): upgrade to 4.2.0 or later
pip install "sqlfluff>=4.2.0"
Technical details
A Denial of Service (DoS) vulnerability exists in the SQLFluff parser due to uncontrolled resource consumption (CWE-400). The root cause is the lack of limits on the complexity or length of parse nodes during the linting process. An unauthenticated remote attacker can exploit this by submitting a maliciously crafted, long SQL query to any application utilizing the SQLFluff library. This results in resource exhaustion, effectively crashing the service. The issue is addressed in version 4.2.0 by the introduction of a configurable parse node limit that is enabled by default.
Affected products
- sqlfluff sqlfluff < 4.2.0
Identifiers
- CVE-2026-46374
- GHSA-73jc-5mrq-prw7
- PYSEC-2026-210
Timeline
- 2026-05-14: advisory: GitHub Security Advisory published
- 2026-06-09: disclosed: CVE published to NVD
- 2026-04-20: patched: Fixed in version 4.2.0