pypi package report

Is pytorch-lightning safe?

6 known vulnerabilities, worst severity CRITICAL.

// our research
// reach

40 direct dependencies

15 carry known advisories, worst CRITICAL

40 packages depend on it

an advisory here reaches each of them

  • 3lc
  • boltzgen
Create a free accountfor every dependency path, dependent and what to upgrade
// ai models

20 published models carry an advisory from this package

1 pin a version the advisory is confirmed against; the rest declare it without a version.

ChantalPellegrini/RaDialog-interactive-radiology-report-generationCRITICAL
Revai/reverb-diarization-v1CRITICALnot pinned

20 published models

1 declared · 3 observed · 16 inferred

ModelEvidence
ChantalPellegrini/RaDialog-interactive-radiology-report-generationdeclared
cross-encoder/mmarco-mMiniLMv2-L12-H384-v1observed
Create a free accountto see all 18 models and per-model risk

20 published AI models are associated with this package: 1 name it in a requirements or pyproject file, 3 load it or import it directly, and 16 are inferred from the runtime stack their declared library pulls in. Only 1 state a version requirement, so this is not a count of affected models.

cvss
9.8
critical

CVSS v3.1 base score out of 10

epss
0.39%
low

chance of exploitation in 30 days, 34th percentile of all CVEs

xyz score
4.9
medium

CyberXYZ composite out of 10

fig. 01 — GHSA-w37p-236h-pfx3, the advisory selected below

// 6 advisories

GHSA-w37p-236h-pfx3

CRITICALGitHub ratingCVE-2026-44484
// 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.2
  • 2.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// 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:

security@lightning.ai

// cvss v3.1 vector

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H

Attack vector
Network
Attack complexity
Low
Privileges required
None
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

Checked 2026-11-06 at 21:35 UTC. The most recent advisory here was published 2026-05-12. Updated continuously from NVD, GHSA, OSV and CNA feeds.

Think a verdict here is wrong? Tell us — we respond within 2 business days.