sqlfluff (pypi) has 3 known vulnerabilities, the worst rated HIGH. Upgrade to 4.2.0 or later to clear all of them. No malicious-package signal is recorded.
3 packages depend on it
an advisory here reaches each of them
No published models are known to use this package.
CVSS v3.1 base score out of 10
chance of exploitation in 30 days, 18th percentile of all CVEs
CyberXYZ composite out of 10
fig. 01 — GHSA-73jc-5mrq-prw7, the advisory selected below
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…
Full advisory text at GitHub advisory or NVD.
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H
CyberXYZ does not call a package safe in absolute terms. It records 3 known vulnerabilities for sqlfluff (pypi), the worst rated HIGH, and no malicious-package signal. Whether it is acceptable depends on the version you run.
Yes. CyberXYZ records 3 known vulnerabilities for sqlfluff (pypi), the worst rated HIGH. They are GHSA-73jc-5mrq-prw7, GHSA-wmhf-fqc8-vxhh, GHSA-jqhc-m2j3-fjrx.
4.2.0 or later clears every advisory recorded for sqlfluff (pypi). Check the release you pick before installing it.
Search sqlfluff in CyberXYZ Check at https://cyberxyz.io/check?q=sqlfluff. The xyz Scanner checks a project's dependencies, and CyberXYZ Proxy checks each package as it is installed.
Checked 2026-11-14 at 10:14 UTC. The most recent advisory here was published 2026-05-19. Updated continuously from NVD, GHSA, OSV and CNA feeds.