CVE-2026-58659

HIGHPre-NVD 7.87.8
EchelonGraph scoreMEDIUM confidence

“—” beside the score: it is equal to the CVSS score beside it.

Score 7.8 from GitHub Security Advisory (severity: HIGH) published 2026-07-15. A secondary CVSS source baseline 7.8; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: EPSS, GitHub Security Advisory, a secondary CVSS source
Trending — 3 sources updated this weekElevated
7.8EG
EchelonGraph verdictPlan a fixRemediate within your standard update timelines at low or medium mission impact and sooner than that at high (the SSVC decision on this page).
  • CISA's Vulnrichment rates exploitation as PoC; EchelonGraph holds no exploit-code reference for it
CISA-KEV: Not listedEPSS PROB: 0.6%CVSS: 7.8Exploit: No code on recordExposed services: Not assessed

A fix is available — apply it.

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.

CVSS v3
7.8
EG Score
7.8HIGHmedium confidence
EG Risk
51
EG Risk 51/100

EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).

How it’s computed (value × EchelonGraph’s weight)
Severity78% × 45%
The EG Score, 7.8 of 10.
Exploitation40% × 40%
EchelonGraph's fixed weight for EG-KEV Tier 3 (Elevated): a constant, not a probability.
Automatability0% × 15%
CISA's SSVC Automatable value: no (Vulnrichment).
SSVC (CISA's decision table, applied by EchelonGraph): Track at low, Track* at medium and Attend at high mission impact.
Exploitation public PoC (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact total (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE.
Action: A fix is available. Apply it within your standard update timelines at low or medium mission impact and sooner than that at high.
EPSS PROB
0.6%
EPSS %ILE
48th
KEV
Not listed

SSVC (CISA's decision table, applied by EchelonGraph)Track at low, Track* at medium and Attend at high mission impact.

A fix is available. Apply it within your standard update timelines at low or medium mission impact and sooner than that at high.

Exploitation public PoC (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact total (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE. Mission impact is CISA's Mission & Well-being decision point, and only you can judge it. CISA's table makes it high when Mission Prevalence is Essential — the vulnerable component "directly provides capabilities that constitute at least one MEF for at least one entity" (MEF: mission essential function) — or when Public Well-Being Impact is Irreversible: "multiple fatalities are likely", the cyber-physical system "is likely lost or destroyed", "extreme or serious externalities" are imposed on other parties, or social systems such as elections or the financial grid "are destabilized and potentially collapse". CISA's decision table

BOD 26-04 (CISA's remediation timeline, Table 1)14 days if the affected system is publicly exposed; Fix on system upgrade if it is not.

In CISA KEV no (CISA's KEV catalog) · Automatable no (CISA Vulnrichment) · Technical impact total (CISA Vulnrichment). Whether your system is publicly exposed is yours to answer. BOD 26-04 binds US Federal Civilian Executive Branch agencies; for anyone else it is CISA's published timeline, a reference rather than an obligation. The directive · how EchelonGraph applies it

Published

July 15, 2026

Last Modified

October 8, 2026

Advisory Details (4)

Auto-updated Jul 15, 2026
Patch available. Sources: github_commit, github_pr.
Web page

PyTorch Lightning Arbitrary Code Execution via _instantiator Hyperparameter | Advisories | VulnCheck

https://www.vulncheck.com/advisories/pytorch-lightning-arbitrary-code-execution-via-instantiator-hyperparameter
GitHub pull request

fix(checkpoint): prevent arbitrary code execution via `_instantiator` in `load_from_checkpoint`

Fix merged in Lightning-AI/pytorch-lightning PR #21832 on 2026-07-14 — awaiting tagged release

https://github.com/Lightning-AI/pytorch-lightning/pull/21832
Web page

Arbitrary code execution via the `_instantiator` hyperparameter in `LightningModule.load_from_checkpoint` — defeats `torch.load(weights_only=True)` · Issue #21822 · Lightning-AI/pytorch-lightning · GitHub

https://github.com/Lightning-AI/pytorch-lightning/issues/21822
GitHub commit

commit d710d689510d (Lightning-AI/pytorch-lightning)

Fix landed in Lightning-AI/pytorch-lightning commit d710d689510d — awaiting tagged release

https://github.com/Lightning-AI/pytorch-lightning/commit/d710d689510d50e800f53b3cd773cbca20b1f86f

Patch Availability(10)

Vendor / EcosystemFix (by version range) / PatchReleasedSource
redhatrhelai3/bootc-rocm-rhel9:17907918932026-10-05redhat
redhatrhelai3/disk-image-cuda-rhel9:17909541792026-10-05redhat
redhatrhelai3/disk-image-cuda-rhel9:17909574172026-10-05redhat
redhatrhelai3/bootc-gcp-cuda-rhel9:17908811232026-10-05redhat
redhatrhaii/vllm-cpu-rhel9:17900757932026-09-23redhat
redhatrhaii/vllm-cuda-rhel9:17900901312026-09-23redhat
redhatrhaii/vllm-cpu-rhel9:17896811282026-09-21redhat
redhatrhaii/vllm-cuda-rhel9:17896811262026-09-21redhat
redhatrhaiis/vllm-cuda-rhel9:17895827762026-09-17redhat
redhatrhaiis/vllm-rocm-rhel9:17895043712026-09-17redhat

Patches are aggregated from vendor advisories (Red Hat, Microsoft, Cisco, GitHub) and package ecosystems (OSV, GHSA). Multiple rows for the same upstream release have been deduplicated.

Affected Packages

(2 across 1 ecosystem)
PyPI(2)
PackageVulnerable rangeFix by version rangeDependents
lightning1.8.0 ... 2.6.5 (171 versions)
  • every version up to 2.6.6: fixed in 2.6.6
—
pytorch-lightning0.0.2 ... 2.6.5 (222 versions)
  • every version up to 2.6.6: fixed in 2.6.6
—

Weakness Classification(1)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

Data Freshness Timeline

(refreshed 15× in last 7d / 43× in last 30d)

Each row is a time one of our pipelines fetched, updated or re-scored this CVE. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. An arrow marks a change the record states ("CVSS v3 → 9.1"); EPSS and GHSA rows show the values recorded at that time, not what changed (EPSS values are rounded; hover one for the exact figures). Most recent first.

Showing the most recent 100 of 221 refreshes on record for this CVE.

A repeat, a row identical to one the same pipeline wrote less than 10 seconds earlier, is not a separate refresh and is not counted. None are among the latest 100 rows. The 121 oldest rows on record are not shown and were not checked, so the counts can still include repeats.

  1. 2026-10-13 16:34 UTCEPSS rescoreEPSS 0.6% · 48th percentile
  2. 2026-10-12 16:34 UTCEPSS rescoreEPSS 0.6% · 48th percentile
  3. 2026-10-12 15:53 UTCEG score recompute
  4. 2026-10-11 19:36 UTCEG score recompute
  5. 2026-10-11 16:51 UTCEG score recompute
  6. 2026-10-11 14:14 UTCEG score recompute
  7. 2026-10-11 13:49 UTCEPSS rescoreEPSS 0.6% · 48th percentile
  8. 2026-10-10 20:00 UTCEPSS rescoreEPSS 0.6% · 48th percentile
  9. 2026-10-09 20:07 UTCEPSS rescoreEPSS 0.6% · 48th percentile
  10. 2026-10-08 17:13 UTCEPSS rescoreEPSS 0.6% · 48th percentile
  11. 2026-10-08 16:39 UTCEG score recompute
  12. 2026-10-08 16:39 UTCVendor advisory
  13. 2026-10-08 15:45 UTCEG score recompute
  14. 2026-10-08 15:45 UTCVendor advisory
  15. 2026-10-07 23:48 UTCEPSS rescoreEPSS 0.6% · 48th percentile
  16. 2026-10-06 15:18 UTCEPSS rescoreEPSS 0.6% · 48th percentile
  17. 2026-10-05 17:43 UTCEPSS rescoreEPSS 0.6% · 48th percentile
  18. 2026-10-04 23:22 UTCEPSS rescoreEPSS 0.6% · 48th percentile
  19. 2026-10-03 14:26 UTCEPSS rescoreEPSS 0.6% · 48th percentile
  20. 2026-10-02 17:56 UTCEPSS rescoreEPSS 0.6% · 48th percentile
  21. 2026-10-01 19:50 UTCEPSS rescoreEPSS 0.6% · 48th percentile
  22. 2026-10-01 12:40 UTCEG score recompute
  23. 2026-10-01 12:40 UTCVendor advisory
  24. 2026-09-30 15:03 UTCEPSS rescoreEPSS 0.6% · 48th percentile
  25. 2026-09-29 15:22 UTCEPSS rescoreEPSS 0.6% · 47th percentile
Show 75 more
  1. 2026-09-28 13:51 UTCEPSS rescoreEPSS 0.6% · 47th percentile
  2. 2026-09-28 08:44 UTCEG score recompute
  3. 2026-09-28 08:44 UTCVendor advisory
  4. 2026-09-27 13:48 UTCEPSS rescoreEPSS 0.6% · 47th percentile
  5. 2026-09-26 15:59 UTCEPSS rescoreEPSS 0.6% · 47th percentile
  6. 2026-09-24 14:04 UTCEPSS rescoreEPSS 0.6% · 47th percentile
  7. 2026-09-24 08:50 UTCEG score recompute
  8. 2026-09-24 08:50 UTCVendor advisory
  9. 2026-09-23 17:54 UTCEPSS rescoreEPSS 0.3% · 25th percentile
  10. 2026-09-23 03:16 UTCEG score recompute
  11. 2026-09-23 03:16 UTCVendor advisory
  12. 2026-09-20 20:16 UTCEPSS rescoreEPSS 0.3% · 25th percentile
  13. 2026-09-18 19:28 UTCEPSS rescoreEPSS 0.3% · 25th percentile
  14. 2026-09-18 04:44 UTCEG score recompute
  15. 2026-09-17 19:31 UTCEPSS rescoreEPSS 0.3% · 25th percentile
  16. 2026-09-16 14:08 UTCEPSS rescoreEPSS 0.3% · 25th percentile
  17. 2026-09-16 05:15 UTCEPSS rescoreEPSS 0.3% · 25th percentile
  18. 2026-09-15 03:11 UTCEPSS rescoreEPSS 0.3% · 25th percentile
  19. 2026-09-13 23:12 UTCEG score recompute
  20. 2026-09-13 16:47 UTCEPSS rescoreEPSS 0.3% · 25th percentile
  21. 2026-09-13 07:13 UTCEG score recompute
  22. 2026-09-11 21:45 UTCEG score recompute
  23. 2026-09-11 14:53 UTCEPSS rescoreEPSS 0.3% · 25th percentile
  24. 2026-09-10 09:35 UTCEPSS rescoreEPSS 0.3% · 25th percentile
  25. 2026-09-08 22:01 UTCEPSS rescoreEPSS 0.3% · 25th percentile
  26. 2026-09-08 00:50 UTCEG score recompute
  27. 2026-09-07 16:01 UTCEPSS rescoreEPSS 0.3% · 25th percentile
  28. 2026-09-06 13:47 UTCEPSS rescoreEPSS 0.3% · 25th percentile
  29. 2026-09-05 20:50 UTCEG score recompute
  30. 2026-09-04 05:07 UTCEPSS rescoreEPSS 0.3% · 25th percentile
  31. 2026-09-02 14:12 UTCEPSS rescoreEPSS 0.3% · 25th percentile
  32. 2026-09-01 13:54 UTCEPSS rescoreEPSS 0.3% · 25th percentile
  33. 2026-09-01 04:40 UTCEPSS rescoreEPSS 0.3% · 25th percentile
  34. 2026-08-31 03:51 UTCEG score recompute
  35. 2026-08-31 03:51 UTCGHSA enrichmentGHSA-qqmf-gpg7-g8gw · GitHub severity HIGH · GitHub CVSS 7.8
  36. 2026-08-30 19:17 UTCEPSS rescoreEPSS 0.3% · 25th percentile
  37. 2026-08-30 16:04 UTCGHSA enrichmentGHSA-qqmf-gpg7-g8gw · GitHub severity HIGH · GitHub CVSS 7.8
  38. 2026-08-30 03:51 UTCEG score recompute
  39. 2026-08-30 03:51 UTCGHSA enrichmentGHSA-qqmf-gpg7-g8gw · GitHub severity HIGH · GitHub CVSS 7.8
  40. 2026-08-30 01:22 UTCEPSS rescoreEPSS 0.3% · 25th percentile
  41. 2026-08-28 21:42 UTCEPSS rescoreEPSS 0.3% · 24th percentile
  42. 2026-08-27 23:59 UTCEG score recompute
  43. 2026-08-27 23:59 UTCGHSA enrichmentGHSA-qqmf-gpg7-g8gw · GitHub severity HIGH · GitHub CVSS 7.8
  44. 2026-08-27 14:25 UTCEPSS rescoreEPSS 0.3% · 24th percentile
  45. 2026-08-27 12:40 UTCGHSA enrichmentGHSA-qqmf-gpg7-g8gw · GitHub severity HIGH · GitHub CVSS 7.8
  46. 2026-08-26 23:07 UTCEG score recompute
  47. 2026-08-26 23:07 UTCGHSA enrichmentGHSA-qqmf-gpg7-g8gw · GitHub severity HIGH · GitHub CVSS 7.8
  48. 2026-08-26 14:46 UTCEPSS rescoreEPSS 0.3% · 24th percentile
  49. 2026-08-26 07:30 UTCGHSA enrichmentGHSA-qqmf-gpg7-g8gw · GitHub severity HIGH · GitHub CVSS 7.8
  50. 2026-08-25 19:01 UTCEG score recompute
  51. 2026-08-25 19:01 UTCGHSA enrichmentGHSA-qqmf-gpg7-g8gw · GitHub severity HIGH · GitHub CVSS 7.8
  52. 2026-08-25 13:49 UTCEPSS rescoreEPSS 0.3% · 24th percentile
  53. 2026-08-25 06:52 UTCGHSA enrichmentGHSA-qqmf-gpg7-g8gw · GitHub severity HIGH · GitHub CVSS 7.8
  54. 2026-08-24 19:32 UTCEG score recompute
  55. 2026-08-24 19:32 UTCGHSA enrichmentGHSA-qqmf-gpg7-g8gw · GitHub severity HIGH · GitHub CVSS 7.8
  56. 2026-08-24 06:25 UTCGHSA enrichmentGHSA-qqmf-gpg7-g8gw · GitHub severity HIGH · GitHub CVSS 7.8
  57. 2026-08-23 18:50 UTCGHSA enrichmentGHSA-qqmf-gpg7-g8gw · GitHub severity HIGH · GitHub CVSS 7.8
  58. 2026-08-23 07:31 UTCEG score recompute
  59. 2026-08-23 07:31 UTCGHSA enrichmentGHSA-qqmf-gpg7-g8gw · GitHub severity HIGH · GitHub CVSS 7.8
  60. 2026-08-23 00:19 UTCEPSS rescoreEPSS 0.3% · 25th percentile
  61. 2026-08-22 20:11 UTCGHSA enrichmentGHSA-qqmf-gpg7-g8gw · GitHub severity HIGH · GitHub CVSS 7.8
  62. 2026-08-22 08:52 UTCEG score recompute
  63. 2026-08-22 08:52 UTCGHSA enrichmentGHSA-qqmf-gpg7-g8gw · GitHub severity HIGH · GitHub CVSS 7.8
  64. 2026-08-21 23:49 UTCEPSS rescoreEPSS 0.3% · 25th percentile
  65. 2026-08-21 21:33 UTCGHSA enrichmentGHSA-qqmf-gpg7-g8gw · GitHub severity HIGH · GitHub CVSS 7.8
  66. 2026-08-21 10:14 UTCEG score recompute
  67. 2026-08-21 10:14 UTCGHSA enrichmentGHSA-qqmf-gpg7-g8gw · GitHub severity HIGH · GitHub CVSS 7.8
  68. 2026-08-20 22:55 UTCEPSS rescoreEPSS 0.3% · 25th percentile
  69. 2026-08-20 22:54 UTCGHSA enrichmentGHSA-qqmf-gpg7-g8gw · GitHub severity HIGH · GitHub CVSS 7.8
  70. 2026-08-20 11:35 UTCGHSA enrichmentGHSA-qqmf-gpg7-g8gw · GitHub severity HIGH · GitHub CVSS 7.8
  71. 2026-08-20 00:16 UTCEG score recompute
  72. 2026-08-20 00:16 UTCGHSA enrichmentGHSA-qqmf-gpg7-g8gw · GitHub severity HIGH · GitHub CVSS 7.8
  73. 2026-08-19 17:04 UTCEPSS rescoreEPSS 0.3% · 25th percentile
  74. 2026-08-19 07:18 UTCGHSA enrichmentGHSA-qqmf-gpg7-g8gw · GitHub severity HIGH · GitHub CVSS 7.8
  75. 2026-08-18 19:59 UTCEG score recompute

Frequently asked(5)

What is CVE-2026-58659?
CVE-2026-58659 is a high-severity vulnerability; its CVE record was published on July 15, 2026. PyTorch Lightning through 2.6.5, fixed in commit d710d68, contains a remote code execution vulnerability in the loadstate function that imports and executes attacker-controlled module names from checkpoint instantiator hyperparameters. Attackers can craft malicious checkpoint files that bypass…
When was CVE-2026-58659 made public?
CVE-2026-58659 was made public on July 10, 2026: that is the date its CVE record's CNA, VulnCheck, gives for when the vulnerability was made public. The CVE record itself was published on July 15, 2026. EchelonGraph's copy of the record carries a last-modified date of October 8, 2026; the record at its source may have been updated since.
Is CVE-2026-58659 actively exploited?
CVE-2026-58659 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.6% probability of exploitation in the next 30 days (48th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-58659?
CVE-2026-58659 has a CVSS base score of 7.8 (a secondary CVSS source that NVD displays; NVD's own analysis pending).
How do I remediate CVE-2026-58659?
A fix for CVE-2026-58659 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2026-58659 are linked in the Vendor Advisories panel on this page.

Dependency Blast Radius

See which npm, PyPI, Go, and Maven packages are affected by CVE-2026-58659

Explore →

Is Your Infrastructure Affected by CVE-2026-58659?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.