Skip to content

Bump tornado from 6.5.5 to 6.5.6 - #103

Closed
dependabot[bot] wants to merge 1 commit into
mainfrom
dependabot/uv/tornado-6.5.6
Closed

Bump tornado from 6.5.5 to 6.5.6#103
dependabot[bot] wants to merge 1 commit into
mainfrom
dependabot/uv/tornado-6.5.6

Conversation

@dependabot

@dependabot dependabot Bot commented on behalf of github Jun 12, 2026

Copy link
Copy Markdown
Contributor

Bumps tornado from 6.5.5 to 6.5.6.

Changelog

Sourced from tornado's changelog.

Release notes

.. toctree:: :maxdepth: 2

releases/v6.5.7 releases/v6.5.6 releases/v6.5.5 releases/v6.5.4 releases/v6.5.3 releases/v6.5.2 releases/v6.5.1 releases/v6.5.0 releases/v6.4.2 releases/v6.4.1 releases/v6.4.0 releases/v6.3.3 releases/v6.3.2 releases/v6.3.1 releases/v6.3.0 releases/v6.2.0 releases/v6.1.0 releases/v6.0.4 releases/v6.0.3 releases/v6.0.2 releases/v6.0.1 releases/v6.0.0 releases/v5.1.1 releases/v5.1.0 releases/v5.0.2 releases/v5.0.1 releases/v5.0.0 releases/v4.5.3 releases/v4.5.2 releases/v4.5.1 releases/v4.5.0 releases/v4.4.3 releases/v4.4.2 releases/v4.4.1 releases/v4.4.0 releases/v4.3.0 releases/v4.2.1 releases/v4.2.0 releases/v4.1.0 releases/v4.0.2 releases/v4.0.1 releases/v4.0.0 releases/v3.2.2 releases/v3.2.1

... (truncated)

Commits
  • aba2569 Merge pull request #3626 from bdarnell/fixes-656
  • a24b260 httpclient_test: Accept an additional error message variant
  • a74240a Release notes and version bump for 6.5.6.
  • e8fc7ed simple_httpclient: Strip auth headers on cross-origin redirects
  • 96dc88c speedups: validate mask length
  • ff808b3 http1connection: Enforce max_body_size in _GzipMessageDelegate
  • ede4e37 auth: Correctly parse check_authentication response
  • 1c178be Remove obsolete curl force_timeout workaround
  • c99d55b Replace deprecated pycurl IOCTLFUNCTION callback with SEEKFUNCTION
  • 2761431 Merge pull request #3587 from bdarnell/fix-link
  • Additional commits viewable in compare view

Dependabot compatibility score

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.


Dependabot commands and options

You can trigger Dependabot actions by commenting on this PR:

  • @dependabot rebase will rebase this PR
  • @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
  • @dependabot show <dependency name> ignore conditions will show all of the ignore conditions of the specified dependency
  • @dependabot ignore this major version will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
  • @dependabot ignore this minor version will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
  • @dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)
    You can disable automated security fix PRs for this repo from the Security Alerts page.

Bumps [tornado](https://github.com/tornadoweb/tornado) from 6.5.5 to 6.5.6.
- [Changelog](https://github.com/tornadoweb/tornado/blob/master/docs/releases.rst)
- [Commits](tornadoweb/tornado@v6.5.5...v6.5.6)

---
updated-dependencies:
- dependency-name: tornado
  dependency-version: 6.5.6
  dependency-type: indirect
...

Signed-off-by: dependabot[bot] <support@github.com>
@dependabot dependabot Bot added dependencies Pull requests that update a dependency file python:uv Pull requests that update python:uv code labels Jun 12, 2026
@amrit110

Copy link
Copy Markdown
Member

Security Vulnerability — No Patch Available Yet

aieng-bot found the following security vulnerability reported by pip-audit, but cannot fix it automatically because no patched version has been released to PyPI yet:

Package Version Vulnerability Fix Versions Status
torch 2.11.0 CVE-2025-3000 (none listed) No fix available on PyPI

Why this cannot be auto-fixed

The pip-audit scan flagged torch 2.11.0 with CVE-2025-3000 (memory corruption in torch.jit.script), but the vulnerability database does not list any fixed version. The latest torch release on PyPI is 2.12.0, but pip-audit's database does not indicate it resolves this CVE.

This is a pre-existing vulnerability unrelated to the tornado bump in this PR. A fix requires the upstream PyTorch maintainers to release a patched version and update the advisory with a fixed version.

Recommended next steps

  1. Monitor the CVE-2025-3000 advisory for a patch release
  2. If this vulnerability is deemed acceptable risk (e.g., torch.jit.script is not used in production code or is local-only), consider adding CVE-2025-3000 to the ignore-vulns list in .github/workflows/code_checks.yml after human review
  3. Once a patched PyTorch release is published to PyPI with the fix listed, aieng-bot can re-run and apply the update automatically

This PR will not be auto-merged until the vulnerability is resolved or explicitly ignored by a human reviewer.

@amrit110

Copy link
Copy Markdown
Member

Security Vulnerability — No Patch Available Yet

aieng-bot found the following security vulnerability reported by pip-audit, but cannot fix it automatically because no patched version has been released to PyPI yet:

Package Version Vulnerability Status
torch 2.11.0 CVE-2025-3000 (GHSA-rrmf-rvhw-rf47) No fix available on PyPI (last affected: 2.12.0)

Why this cannot be auto-fixed

The vulnerability exists in torch itself — a memory corruption issue in torch.jit.script. According to the OSV advisory, versions up to and including 2.12.0 (the current latest) are affected, with no fixed version published yet. A fix requires the PyTorch maintainers to release a new version.

Recommended next steps

  1. Monitor the CVE-2025-3000 / GHSA-rrmf-rvhw-rf47 advisory for a patch release from PyTorch
  2. Once a patched version is published to PyPI, aieng-bot can re-run and apply the update automatically
  3. Consider whether a temporary ignore-vulns exception can be added to the CI workflow (requires human review and approval)

This PR (tornado bump from 6.5.5 → 6.5.6) itself is a valid security fix. The blocking pip-audit failure is unrelated to the tornado change and is caused by a pre-existing torch vulnerability with no upstream fix. Human review is required to proceed.

@amrit110

Copy link
Copy Markdown
Member

Security Vulnerability — No Patch Available Yet

aieng-bot found the following security vulnerability reported by pip-audit, but cannot fix it automatically because no patched version has been recorded in the PyPI vulnerability database:

Package Version Vulnerability Fix Versions Status
torch 2.11.0 CVE-2025-3000 (none listed) No fix available on PyPI

Why this cannot be auto-fixed

pip-audit reports CVE-2025-3000 against torch 2.11.0 with an empty Fix Versions field, meaning the PyPI advisory database has not yet recorded a patched release. The CVE describes a memory corruption vulnerability in torch.jit.script (originally disclosed against PyTorch 2.6.0).

A fix requires the upstream PyTorch maintainers to release a patched version and for the PyPI vulnerability database to record it. Once that happens, aieng-bot can re-run and apply the update automatically.

Recommended next steps

  1. Monitor CVE-2025-3000 for a patch release announcement
  2. Check if a pip-audit ignore/exception can be added temporarily with justification (requires human review)
  3. Consider whether torch.jit.script is used in this project and whether the exposure is relevant

This PR will not be auto-merged until the vulnerability is resolved.

@amrit110

Copy link
Copy Markdown
Member

Security Vulnerability — No Patch Available Yet

aieng-bot found the following security vulnerabilities reported by pip-audit, but cannot fix them automatically because no patched version has been released to PyPI yet:

Package Version Vulnerability Status
torch 2.11.0 CVE-2025-3000 / GHSA-rrmf-rvhw-rf47 No fix available on PyPI (latest 2.12.0 is also affected)

Why this cannot be auto-fixed

The vulnerability exists in torch itself (torch.jit.script memory corruption — CVE-2025-3000). A fix requires the upstream PyTorch maintainers to release a patched version. All currently published PyPI releases (including 2.12.0, the latest) remain flagged by the OSV advisory database.

Recommended next steps

  1. Monitor the GHSA-rrmf-rvhw-rf47 advisory for a patch release
  2. Consider whether a pip-audit ignore/exception for this CVE can be added temporarily with justification (requires human review)
  3. Once a patched release is published to PyPI, aieng-bot can re-run and apply the update automatically

Note on this PR

This PR (bumping tornado 6.5.5 → 6.5.6) is itself a valid security fix and is otherwise ready to merge. The torch vulnerability is a pre-existing issue unrelated to this PR's changes.

This PR will not be auto-merged until the torch vulnerability is resolved or explicitly waived.

@dependabot @github

dependabot Bot commented on behalf of github Jun 17, 2026

Copy link
Copy Markdown
Contributor Author

Superseded by #106.

@dependabot dependabot Bot closed this Jun 17, 2026
@dependabot
dependabot Bot deleted the dependabot/uv/tornado-6.5.6 branch June 17, 2026 18:46
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

dependencies Pull requests that update a dependency file python:uv Pull requests that update python:uv code

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant