[GHSA-qqmf-gpg7-g8gw] Add pytorch-lightning as affected package; correct lightning fixed version - #9771
Open
arielbosa wants to merge 1 commit into
Conversation
The same vulnerable load_from_checkpoint implementation ships in the pytorch-lightning distribution; fixed in 2.6.6. Also corrects the lightning fixed boundary from the nonexistent 2022.6.15 to 2.6.6. Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
Contributor
There was a problem hiding this comment.
Copilot review overview
🟢 Approval recommended
The package additions and fixed boundaries match the upstream 2.6.6 security release.
Review effort: Balanced
Findings: None
What changed in this PR
Corrects affected-package data for GHSA-qqmf-gpg7-g8gw.
Changes:
- Corrects
lightningfixed version to2.6.6. - Adds
pytorch-lightningas affected before2.6.6.
| File | Description |
|---|---|
advisories/github-reviewed/2026/07/GHSA-qqmf-gpg7-g8gw/GHSA-qqmf-gpg7-g8gw.json |
Updates affected PyPI package ranges. |
💡 Add a code-review agent skill or configure MCP servers for context-aware, tailored reviews. Learn more in the docs.
github-actions
Bot
changed the base branch from
main
to
arielbosa/advisory-improvement-9771
September 24, 2026 15:41
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.
Updates
Comments
This PR makes two corrections to the affected-package data for GHSA-qqmf-gpg7-g8gw / CVE-2026-58659, and supersedes #9770 (created via the "Suggest improvements" portal, so I cannot amend its branch).
1. Add
pytorch-lightning(PyPI) as an affected package, fixed in 2.6.6The advisory currently lists only the
lightningdistribution, but the same vulnerableload_from_checkpointimplementation ships in thepytorch-lightningPyPI package:pytorch_lightning.pytorch-lightning==2.6.6wheel on PyPI contains the fix: the_ALLOWED_INSTANTIATORSallowlist inpytorch_lightning/core/saving.pythat blocks untrusted_instantiatorimport paths (fix commitd710d68was cherry-picked onto the release branch, which is why it is not an ancestor of the2.6.6tag).pytorch-lightningfor the same API in GHSA-75m9-98v2-hjpm (<= 2.6.0).Without this entry, users of the
pytorch-lightningdistribution receive no alert.2. Correct the
lightningfixed boundary from2022.6.15to2.6.6lightning==2022.6.15does not exist on PyPI, and under PEP 440 version ordering2022.6.15sorts above every2.xrelease, so the current range (introduced: 0, fixed: 2022.6.15) permanently flags even patched users. The correct boundary is2.6.6, consistent with the advisory text ("through 2.6.5") and the release that ships the fix.Relationship to #9770
#9770 contains only the
lightningboundary fix and accidentally removed the CVSS v3 vector (a portal form artifact). This PR includes the boundary fix, adds the missingpytorch-lightningentry, and preserves the CVSS v3 vector. Please close #9770 in favor of this one.🤖 Generated with Claude Code