pytorch-lightning
8 published advisories; version 2.4.0 or later fixes all but 3 of them.
- Registry
- PyPI
- Advisories
- 8
- Latest fix
- 2.4.0
- Exploited in the wild
- None listed
3 advisories have no fixed release in any version yet. What can be done meanwhile:
General guidance from ShieldPi, not a vendor fix
- Compromised release. Move to a release the advisory names as clean, and rotate every credential, token and key the environment that ran the affected release could read.GHSA-w37p-236h-pfx3
- Unsafe deserialization. Do not let it load files, models or data from sources you do not trust, and keep its RPC and socket ports reachable only from localhost or hosts you trust.GHSA-75m9-98v2-hjpm
Check your projects
shieldpi agent-config checks agent and MCP packages from npm and PyPI, not pytorch-lightning. Any scanner that reads the OSV database finds it in your lockfiles, for example Google's open-source OSV-Scanner.
osv-scanner scan source -r .Or check a lockfile against ShieldMap in your browser.
Packages reported malicious by OpenSSF whose names imitate pytorch-lightning. Check that you install pytorch-lightning itself.
- pytorch-lighting 1 letter off
Source: github.com/lightning-ai/lightning, named in the package metadata (not verified)
3 of the last 10 releases of pytorch-lightning were published with build provenance: a signed record of the repository and commit each was built from, which the registry checks before it accepts the release.
- 2.6.6
- 2.6.5
- 2.6.4
- 2.6.1
- 2.6.0
- 2.5.6
- 2.5.5
- 2.5.4
- 2.5.3
- 2.5.2
Green: published with provenance. Grey: without.
OpenSSF Scorecard has not scored this repository.
Provenance from deps.dev (CC BY 4.0); Scorecard from OpenSSF (CDLA-Permissive-2.0). As of 2026-11-18.
| Advisory | Severity | Affected | Fixed in | Published |
|---|---|---|---|---|
| PyTorch Lightning load_from_checkpoint has an insecure checkpoint deserializationCVE-2026-31221 | High | <= 2.6.0 | No fix yet | 2026-05-12 |
| Compromise of PyTorch Lightning PyPi Package VersionsCVE-2026-44484 | Critical | = 2.6.2 | No fix yet | 2026-05-07 |
| Compromise of PyTorch Lightning PyPi Package VersionsCVE-2026-44484 | Critical | = 2.6.3 | No fix yet | 2026-05-07 |
| PyTorch Lightning path traversal vulnerabilityCVE-2024-8019 | Critical | < 2.4.0 | 2.4.0 | 2025-03-20 |
| PyTorch Lightning denial of service vulnerabilityCVE-2024-8020 | High | <= 2.3.2 | No fix yet | 2025-03-20 |
| pytorch-lightning vulnerable to Arbitrary File Write via /v1/runs API endpointCVE-2024-5980 | Critical | < 2.3.3 | 2.3.3 | 2024-06-27 |
| Remote code execution in pytorch lightningCVE-2024-5452 | Critical | < 2.3.3 | 2.3.3 | 2024-06-06 |
| Code Injection in PyTorch LightningCVE-2022-0845 | Critical | < 1.6.0 | 1.6.0 | 2022-03-06 |
| pytorch-lightning is vulnerable to Deserialization of Untrusted DataCVE-2021-4118 | High | < 1.6.0 | 1.6.0 | 2022-01-06 |
Sources: GitHub Advisory Database, reviewed and malware advisories (CC BY 4.0, https://github.com/advisories); advisories published by Cursor (https://github.com/cursor/cursor/security/advisories); advisories published by OpenClaw (https://github.com/openclaw/openclaw/security/advisories); advisories published by vLLM (https://github.com/vllm-project/vllm/security/advisories); advisories published by Open WebUI (https://github.com/open-webui/open-webui/security/advisories); advisories published by n8n (https://github.com/n8n-io/n8n/security/advisories); advisories published by Flowise (https://github.com/FlowiseAI/Flowise/security/advisories); advisories published by Langflow (https://github.com/langflow-ai/langflow/security/advisories); advisories published by the MCP Python SDK project (https://github.com/modelcontextprotocol/python-sdk/security/advisories); advisories published by MLflow (https://github.com/mlflow/mlflow/security/advisories); CISA Known Exploited Vulnerabilities catalog (CC0). Data as of 2026-11-22. ShieldMap describes how each problem works and how to fix it; it does not publish exploit code. Report a correction to [email protected].