Categories
CVE-2026-44484 critical CVSS 9.8

Vulnerability in pytorch-lightning (CVE-2026-44484)

Summary

Vulnerability in pytorch-lightning (CVE-2026-44484). Successful exploitation can lead to full system takeover.

Original description

The description as published by the source.

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
  • Re…

Source: GitHub Security Advisories (Global) NVD GitHub Advisory

Auto-generated summary

Assembled by SecPulse from the source data (CVSS, CWE, affected versions) using templates — no AI involved. Check the original description and references below for exact details.

A vulnerability tracked as CVE-2026-44484 has been found in pytorch-lightning.
Successful exploitation can lead to full system takeover. CVSS score: 9.8/10.
What to do: apply the vendor's official patched release.
If unsure, ask your IT team or search "pytorch-lightning CVE-2026-44484" on the vendor's site.

CVE-2026-44484 (pytorch-lightning) — CWE-506 / CVSS v3 9.8
Attack vector: remote (network-reachable) / unauthenticated / no user interaction
Plan: 1) Audit SBOM/dependencies, 2) Stage→prod upgrade, 3) Add WAF/proxy monitoring on affected endpoints, 4) Hunt IOCs in logs.
Refs: see the GHSA / vendor advisory / patched release linked on this page.

❓ What is the problem

A vulnerability (CWE-506) exists in pytorch-lightning.

📍 Affected scope

Check the vendor advisory for the affected versions of pytorch-lightning.

🔥 Severity

Severity: Critical (CVSS 9.8/10). Successful exploitation can lead to full system takeover.

🔧 How to fix

Update to the patched release per vendor advisory.

🛡️ Workaround

Until the patch is applied: disable the affected feature, apply WAF rules, or restrict access via network ACLs.

🔍 Detection

Search webserver/proxy logs for unusual request patterns matching this CVE's known IOCs. Run grep -r 'pytorch-lightning' . against your dependency files (package-lock.json, requirements.txt, go.sum) to find affected services.

Response actions

Concrete steps and command examples for SOC/SRE teams to execute in order

  1. 1
    Identify exposure identify
    grep -r 'pytorch-lightning' . | grep -v node_modules

    リポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で pytorch-lightning を grep し、稼働しているサービス・バージョンを把握する。

  2. 2
    Post-deployment verification verify
    Confirm patched version is live in production

    パッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番ではアクセスログ・WAF でアラート再発が無いか継続監視。

Affected packages

pip pytorch-lightning
[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}]
PyPI pytorch-lightning

References

We use cookies for analytics and ad measurement. This setting applies to all Game co., Ltd. sites. Details