Sign in Sign up
JA · EN · FR
SecPulse
Categories
CVE-2026-58659 high CVSS 7.8

Vulnerability in lightning (CVE-2026-58659)

Summary

Vulnerability in lightning (CVE-2026-58659). Successful exploitation can lead to full system takeover. Mitigation: upgrade to 2.6.6 or later.

Original description

The description as published by the source.

PyTorch Lightning through 2.6.5, fixed in commit d710d68, contains a remote code execution vulnerability in the _load_state function that imports and executes attacker-controlled module names from checkpoint _instantiator hyperparameters. Attackers can craft malicious checkpoint files that bypass weights_only=True protections to execute arbitrary code when LightningModule.load_from_checkpoint is called.

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-58659 has been found in lightning.
Successful exploitation can lead to full system takeover. CVSS score: 7.8/10.
What to do: upgrade lightning to 2.6.6 or later.
If unsure, ask your IT team or search "lightning CVE-2026-58659" on the vendor's site.

CVE-2026-58659 (lightning) — CWE-470 / CVSS v3 7.8
Attack vector: local / unauthenticated
Patched: 2.6.6 — apply immediately
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-470) exists in lightning.

📍 Affected scope

Check the vendor advisory for the affected versions of lightning.

🔥 Severity

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

🔧 How to fix

Update to 2.6.6.

🛡️ 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 '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 'lightning' . | grep -v node_modules

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

  2. 2
    Apply patch patch 
    Upgrade lightning to 2.6.6

    ステージング環境で 2.6.6 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスを含めること。

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

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

Affected packages

pip lightning
[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"2.6.6"}]}]

References

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