Repository navigation
fix(deps): lock tornado 6.6 for its three advisories - #35
Merged
Merged
Conversation
tornado 6.5.10, which jupyter's kernel and client bring in, has CVE-2026-115927, CVE-2026-116577 and CVE-2026-116578, all fixed in 6.6 (released 2026-10-21); the dependency audit fails on them. The lock moves tornado alone, and an audit of every extra in the lock finds no advisory after it.
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
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.
tornado 6.5.10 has three advisories, CVE-2026-115927, CVE-2026-116577 and CVE-2026-116578, all fixed in 6.6 (released 2026-10-21). This repository's dependency audit fails on them, on main and on every open pull request; jupyter's kernel and client bring tornado in.
The lock moves tornado from 6.5.10 to 6.6 and nothing else; the lock was diffed package by package before and after. It was made on an export of main with the uv this repository's CI runs, and
uv lock --checkpasses. substrax's audit-lock, run over every extra in the lock against PyPI and OSV, finds no advisory after it.Once this merges, the open
ci/repin-already-testedpull request rebases onto it and its Security job goes green.