CVE-2026-44484 — pytorch-lightning
CRITICALCVE-2026-44484 is a critical-severity (CVSS 9.8) CWE-506 vulnerability in pytorch-lightning. The records list no fixed version yet; check the vendor advisory below and apply the mitigations in the meantime.
Compromise of PyTorch Lightning PyPi Package Versions
Exploitation Status
No confirmed exploitation observed yet
- CISA assesses this as automatable — exploitation doesn’t require manual, per-target effort, which raises the odds of mass scanning and opportunistic attacks.
- A successful exploit gives an attacker total control of the affected component, not partial access.
- CISA’s own triage has not observed active exploitation or public proof-of-concept code for this CVE as of its last assessment.
Exploitation and automatability from CISA’s SSVC triage for CVE-2026-44484.
EPSS Exploitation Probability
Probability of exploitation in the next 30 days, from FIRST.org EPSS.
How urgent is this, really
Where this sits among everything scored
Real-World Exposure
pytorch-lightning🐍pytorch-lightningReal-time download stats are indexed for npm and PyPI packages. This vulnerability affects PyPI packages — download data is not available via public APIs for these ecosystems.
Description
Security Advisory: Compromise of PyTorch Lightning PyPI Package Versions
Published: 2026-04-30
Last Updated: 2026-05-12
Github Advisory: CVE-2026-44484
We have identified a security incident affecting certain versions of one of our PyPI packages.
What happened
We have determined that one or more released versions of this package have been compromised and include malicious code.
Our current investigation indicates that the affected versions have introduced functionality consistent with a credential harvesting mechanism. We are still actively analysing the scope and behaviour of the code.
At this stage, the root cause of the compromise is still under investigation.
What versions are affected
We are currently working to confirm the exact set of impacted versions.
We have determined the following versions as affected and ask that you delete them from your systems:
2.6.22.6.3
We will update this advisory if the versions impacted by this vulnerability change.
What you should do immediately
If you have installed or are running any potentially affected versions:
- Assume the environment may be compromised
- Immediately rotate all credentials and secrets that may have been exposed, including:
- API keys
- Access tokens
- SSH keys
- Service account credentials
- Rebuild affected systems from a known clean state
- Pin PyTorch Lightning to version
2.6.1 - Review logs for any suspicious or unauthorised activity
Actions we have taken
- Quarantined malicious versions from PyPI
- Recommend using version
2.6.1: https://github.com/Lightning-AI/pytorch-lightning/releases/tag/2.6.1 - Revoked and rotated all internal credentials associated with our release process
- Initiated a full investigation into the compromise
Ongoing investigation
We are actively working to:
- Identify the exact mechanism of compromise
- Confirm the full set of affected versions
- Determine the behaviour and impact of the malicious code
- Assess any downstream impact to users
We will provide updates as soon as more information becomes available.
Commitment to transparency
We take the security of our users and the integrity of our software supply chain extremely seriously.
We will continue to share timely and accurate updates as our investigation progresses.
Contact
If you have questions or believe you may be impacted, please contact us at:
Affected Packages
| Ecosystem | Package | Vulnerable range | Fix |
|---|---|---|---|
| 🐍PyPI | pytorch-lightning | all versions | No fix |
| 🐍PyPI | pytorch-lightning | all versions | No fix |
Affected Products
pytorch lightninglightningaiDetection & mitigation playbook
Open-source dependencyDetect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for pytorch-lightning, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Remediation status
The records we use list no patched version of pytorch-lightning for CVE-2026-44484. Check the maintainer's advisory, and where your build allows, override or pin the dependency away from the vulnerable range.
Mitigate without a patch
If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.
Fixing This On Your OS
If you run this on a Linux distribution, patch through your package manager against the distro's own security advisory below — it tracks the exact backported fix for your release, which can ship on a different timeline (and sometimes a different severity) than the upstream project.
Important: This flaw in PyTorch Lightning, which could enable remote credential harvesting, does not affect Red Hat products. The vulnerable code is not present in Red Hat Enterprise Linux AI or Red Hat AI Inference Server components.
Mitigation for this issue is either not available or the currently available options do not meet the Red Hat Product Security criteria comprising ease of use and deployment, applicability to widespread installation base, or stability.Source: Red Hat security advisory for CVE-2026-44484 (CC BY 4.0)
Frequently Asked Questions
Is CVE-2026-44484 in your dependencies?
Find it across PyPI, including transitive dependencies.