Pin lightning==2.6.1 to avoid compromised 2.6.2/2.6.3#229
Closed
imbgar-roboflow wants to merge 142 commits into
Closed
Pin lightning==2.6.1 to avoid compromised 2.6.2/2.6.3#229imbgar-roboflow wants to merge 142 commits into
imbgar-roboflow wants to merge 142 commits into
Conversation
…ection add Florence-2 object detection cookbook
Updates the requirements on [mypy](https://github.com/python/mypy) to permit the latest version. - [Changelog](https://github.com/python/mypy/blob/master/CHANGELOG.md) - [Commits](python/mypy@v1.11.2...v1.15.0) --- updated-dependencies: - dependency-name: mypy dependency-type: direct:production ... Signed-off-by: dependabot[bot] <support@github.com>
…and-lt-1.16.0 ⬆️ Update mypy requirement from <1.15.0,>=1.11.2 to >=1.11.2,<1.16.0
Signed-off-by: Onuralp SEZER <thunderbirdtr@gmail.com>
ci(docs): 👷 update docs ci with mkdocs-insiders and use uv
… [ wrong Update index.md Update florence_2.md Update paligemma_2.md Update qwen_2_5_vl.md - add quotes to fix pip instruction for Mac Update qwen_2_5_vl.md, quote around package Update paligemma_2.md quote around package for Mac Update qwen_2_5_vl.md add quotes to all pip command for consistency
Updates the requirements on [transformers](https://github.com/huggingface/transformers) to permit the latest version. - [Release notes](https://github.com/huggingface/transformers/releases) - [Commits](huggingface/transformers@v4.43.0...v4.48.3) --- updated-dependencies: - dependency-name: transformers dependency-type: direct:production ... Signed-off-by: dependabot[bot] <support@github.com>
…4.49.0 ⬆️ Update transformers requirement from <4.48.0 to <4.49.0
docs: 📝 enable comments on documentation pages and add comment section template
…atest (#155) Signed-off-by: Onuralp SEZER <thunderbirdtr@gmail.com>
- update contributor guidelines - update README.md - add `open in colab` and `roboflow dataset` buttons in cookbooks
add JSONL docs + examples
…o_latest set version of maestro to latest in cookbooks
…Transformers Signed-off-by: Onuralp SEZER <thunderbirdtr@gmail.com>
…for clarity Signed-off-by: Onuralp SEZER <thunderbirdtr@gmail.com>
…mple usage Signed-off-by: Onuralp SEZER <thunderbirdtr@gmail.com>
feat(logging): 🔊 add logging configuration for PyTorch Lightning and Transformers
updates: - [github.com/astral-sh/ruff-pre-commit: v0.9.4 → v0.9.6](astral-sh/ruff-pre-commit@v0.9.4...v0.9.6) - [github.com/pre-commit/mirrors-mypy: v1.14.1 → v1.15.0](pre-commit/mirrors-mypy@v1.14.1...v1.15.0)
chore(pre_commit): ⬆ pre_commit autoupdate
…and text -> box parsing
updates: - [github.com/astral-sh/ruff-pre-commit: v0.11.2 → v0.11.4](astral-sh/ruff-pre-commit@v0.11.2...v0.11.4)
chore(pre_commit): ⬆ pre_commit autoupdate
updates: - [github.com/astral-sh/ruff-pre-commit: v0.11.4 → v0.11.5](astral-sh/ruff-pre-commit@v0.11.4...v0.11.5)
chore(pre_commit): ⬆ pre_commit autoupdate
updates: - [github.com/astral-sh/ruff-pre-commit: v0.11.5 → v0.11.6](astral-sh/ruff-pre-commit@v0.11.5...v0.11.6)
chore(pre_commit): ⬆ pre_commit autoupdate
updates: - [github.com/astral-sh/ruff-pre-commit: v0.11.6 → v0.11.7](astral-sh/ruff-pre-commit@v0.11.6...v0.11.7)
chore(pre_commit): ⬆ pre_commit autoupdate
Updates the requirements on [tox](https://github.com/tox-dev/tox) to permit the latest version. - [Release notes](https://github.com/tox-dev/tox/releases) - [Changelog](https://github.com/tox-dev/tox/blob/main/docs/changelog.rst) - [Commits](tox-dev/tox@4.18.1...4.26.0) --- updated-dependencies: - dependency-name: tox dependency-version: 4.26.0 dependency-type: direct:production ... Signed-off-by: dependabot[bot] <support@github.com>
Updates the requirements on [mypy](https://github.com/python/mypy) to permit the latest version. - [Changelog](https://github.com/python/mypy/blob/master/CHANGELOG.md) - [Commits](python/mypy@v1.11.2...v1.16.0) --- updated-dependencies: - dependency-name: mypy dependency-version: 1.16.0 dependency-type: direct:production ... Signed-off-by: dependabot[bot] <support@github.com>
updates: - [github.com/astral-sh/ruff-pre-commit: v0.11.7 → v0.11.12](astral-sh/ruff-pre-commit@v0.11.7...v0.11.12) - [github.com/pre-commit/mirrors-mypy: v1.15.0 → v1.16.0](pre-commit/mirrors-mypy@v1.15.0...v1.16.0)
Updates the requirements on [pytest](https://github.com/pytest-dev/pytest) to permit the latest version. - [Release notes](https://github.com/pytest-dev/pytest/releases) - [Changelog](https://github.com/pytest-dev/pytest/blob/main/CHANGELOG.rst) - [Commits](pytest-dev/pytest@8.3.2...8.4.0) --- updated-dependencies: - dependency-name: pytest dependency-version: 8.4.0 dependency-type: direct:production ... Signed-off-by: dependabot[bot] <support@github.com>
…-and-lt-8.5.0 ⬆️ Update pytest requirement from ~=8.3.2 to >=8.3.2,<8.5.0
…and-lt-1.17.0 ⬆️ Update mypy requirement from <1.16.0,>=1.11.2 to >=1.11.2,<1.17.0
…nd-lt-4.27.0 ⬆️ Update tox requirement from <4.26.0,>=4.18.1 to >=4.18.1,<4.27.0
chore(pre_commit): ⬆ pre_commit autoupdate
updates: - [github.com/PyCQA/bandit: 1.8.3 → 1.8.5](PyCQA/bandit@1.8.3...1.8.5) - [github.com/astral-sh/ruff-pre-commit: v0.11.12 → v0.12.1](astral-sh/ruff-pre-commit@v0.11.12...v0.12.1) - [github.com/pre-commit/mirrors-mypy: v1.16.0 → v1.16.1](pre-commit/mirrors-mypy@v1.16.0...v1.16.1)
chore(pre_commit): ⬆ pre_commit autoupdate
Add new theme
Lightning AI advisory GHSA-w37p-236h-pfx3 reports the lightning / pytorch-lightning 2.6.2 and 2.6.3 wheels on PyPI contain a credential-harvesting payload that auto-executes on import. 2.6.1 is the last known clean release. The previous spec 'lightning>=2.4.0' would resolve to 2.6.3 on a fresh install. Pinning to 2.6.1 forces resolvers to skip the malicious versions until upstream publishes a clean replacement. Refs: GHSA-w37p-236h-pfx3
|
|
Contributor
Author
|
Closing — accidentally targeted main instead of the default branch develop. Reopening against develop. |
imbgar-roboflow
deleted the
security/pin-lightning-2.6.1-cve-ghsa-w37p-236h-pfx3
branch
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
8 participants
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.
Summary
lightningto==2.6.1(was>=2.4.0) so a fresh install does not resolve to the malicious wheels on PyPI.Why
Lightning AI advisory GHSA-w37p-236h-pfx3 (published 2026-04-30) confirms that
lightning/pytorch-lightning2.6.2 and 2.6.3 on PyPI were compromised. The wheels include a hidden_runtime/directory with astart.pydownloader and an ~11 MB obfuscatedrouter_runtime.jspayload that auto-executes onimport lightning, harvests credentials (GitHub/npm/PyPI tokens, cloud creds, env vars, SSH keys), and attempts to commit encoded data back to victim repos. See Socket's writeup: https://socket.dev/blog/lightning-pypi-package-compromised.2.6.1(published 2026-01-30) is the last known clean release. The current speclightning>=2.4.0is unbounded and would resolve to2.6.3on a fresh install — this PR forces resolvers to skip the malicious versions until upstream ships a clean replacement.Notes
>=range again.uv lock/poetry lockregeneration is needed — thepyproject.tomlchange is sufficient.Test plan
pip install -e .still resolves successfully