Conversation
The current floor is 0.3.0, so an existing environment can satisfy the requirement with any 0.5.x release. All of them carry the advisories that 0.6.0 fixes: three denial-of-service issues (CVE-2026-59893, CVE-2026-54284, CVE-2026-71491) and a string-escaping bug (CVE-2026-59894). OSV reports eleven entries for 0.5.3 and none for 0.6.0. Upstream already allows 0.6.x (the cap is <0.7), so this only raises the floor: a fresh install is unaffected, and an upgrade no longer silently keeps a vulnerable sqlparse.
DiegoDAF
added a commit
to DiegoDAF/pgcli.daf
that referenced
this pull request
Sep 17, 2026
dbcli#1639 (CodeQL) and dbcli#1640 (sqlparse floor) are open. The two remaining branches are written and tested, waiting for room in the queue. Upcoming had grown to 84 items, and three of its sections were stating things that stopped being true weeks ago: that four merged PRs were still open, that the SQL_ASCII work was undecided, and that $XDG_STATE_HOME was not done. Everything moved down to its date, nothing was deleted.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
The current requirement is
sqlparse >=0.3.0,<0.7, so an existing environment can satisfy it with any 0.5.x release. All of them are affected by the advisories that 0.6.0 fixes: three denial-of-service issues (CVE-2026-59893, CVE-2026-54284, CVE-2026-71491) and a string-escaping bug (CVE-2026-59894). Querying OSV returns eleven entries for sqlparse 0.5.3 and none for 0.6.0.The cap already allows 0.6.x, so this only raises the floor. A fresh install is unaffected, since pip resolves to the newest release either way. What changes is the upgrade path: today
pip install -U pgclion a machine that already has 0.5.3 keeps that version, because it still satisfies the requirement.pgcli itself needs no change for 0.6.0: the full test suite passes against a live server on this branch, and
pgspecialonly requiressqlparse>=0.1.19.