CVE-2026-24747

HIGHPre-NVD 8.88.8—
EchelonGraph scoreMEDIUM confidence

This high-severity CVE scores 8.8 under a secondary CVSS source (NVD's own analysis pending). EPSS exploit probability: 0.7%, top 50% of all CVEs by exploit prediction. GitHub Security Advisory data not yet ingested — confidence will rise once GHSA publishes (typical lag: hours to days for open-source ecosystem CVEs; never for infrastructure-only CVEs).

Triggered by: NVD CVSS baseline
Sources: epss, secondary
8.8EG
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 1%CVSS: 8.8Exploit: None knownExposed: 0

A fix is available — apply it.

PyTorch is a Python package that provides tensor computation. Prior to version 2.10.0, a vulnerability in PyTorch's weights_only unpickler allows an attacker to craft a malicious checkpoint file (.pth) that, when loaded with torch.load(..., weights_only=True), can corrupt memory and potentially lead to arbitrary code execution. Version 2.10.0 fixes the issue.

CVSS v3
8.8
EG Score
8.8(medium)
EG Risk
40(Track)
EG Risk 40/100SSVC: Track

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
Severity88% × 45%
Exploitation1% × 40%
Automatability0% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
1%
EPSS %ILE
52%
KEV
Not listed

Published

January 27, 2026

Last Modified

July 15, 2026

Advisory Details (7)

Auto-updated Jun 30, 2026
Patch available. Sources: github_release, github, redhat.
redhat Patch Available
https://security.access.redhat.com/data/csaf/v2/vex/2026/cve-2026-24747.json
redhat

2433612 – (CVE-2026-24747) CVE-2026-24747 pytorch: PyTorch: Arbitrary code execution via malicious checkpoint file loading

https://bugzilla.redhat.com/show_bug.cgi?id=2433612
redhat Patch Available

cve-details

https://access.redhat.com/security/cve/CVE-2026-24747
redhat Patch Available
https://access.redhat.com/errata/RHSA-2026:24977
github Patch Available

Loading a malicious PyTorch checkpoint with weights_only=True can result in arbitrary code execution · Advisory · pytorch/pytorch · GitHub

https://github.com/pytorch/pytorch/security/advisories/GHSA-63cw-57p8-fm3p
github_release Patch Available

PyTorch 2.10.0 Release

Patch available: pytorch/pytorch v2.10.0

https://github.com/pytorch/pytorch/releases/tag/v2.10.0
generic

[lr_scheduler] SWALR serializes anneal_func, causing an error when loading state_dict with weight_only=True · Issue #163105 · pytorch/pytorch · GitHub

https://github.com/pytorch/pytorch/issues/163105

Vendor Advisories for CVE-2026-24747(1)

These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.

Patch Availability(1)

Vendor / EcosystemFixed in / PatchReleasedSource
redhatrhoai/odh-vllm-gaudi-rhel9:17800690692026-06-10redhat

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

(6 across 5 ecosystems)
PyPI(2)
PackageVulnerable rangeFixed inDependents
pytorch0.1.2, 1.0.22.10.0—
torch1.0.0 ... 2.9.1 (44 versions)2.10.0—
Debian:11(1)
PackageVulnerable rangeFixed inDependents
pytorch1.12.0-1 ... 2.9.1+dfsg-1~exp2 (51 versions)——
Debian:12(1)
PackageVulnerable rangeFixed inDependents
pytorch1.13.1+dfsg-4 ... 2.9.1+dfsg-1~exp2 (38 versions)——
Debian:13(1)
PackageVulnerable rangeFixed inDependents
pytorch2.12.0+dfsg2-1 ... 2.9.1+dfsg-1~exp2 (14 versions)——
Debian:14(1)
PackageVulnerable rangeFixed inDependents
pytorch2.12.0+dfsg2-1~exp1 ... 2.9.1+dfsg-1~exp2 (9 versions)2.12.0+dfsg2-1—

Weakness Classification(2)

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

Data Freshness Timeline

(refreshed 5× in last 7d / 25× in last 30d)

Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. 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. Most recent first.

Showing the most recent 100 of 169 total refreshes for this CVE.

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

Related CVEs(same vendor + same CWE)

Frequently asked(5)

What is CVE-2026-24747?
CVE-2026-24747 is a high vulnerability published on January 27, 2026. PyTorch is a Python package that provides tensor computation. Prior to version 2.10.0, a vulnerability in PyTorch's weightsonly unpickler allows an attacker to craft a malicious checkpoint file (.pth) that, when loaded with torch.load(..., weightsonly=True), can corrupt memory and potentially lead…
When was CVE-2026-24747 disclosed?
CVE-2026-24747 was first published in the National Vulnerability Database on January 27, 2026, with the most recent update on July 15, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-24747 actively exploited?
CVE-2026-24747 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 1% probability of exploitation in the next 30 days, which ranks it in the top 47.6% of all scored CVEs.
What is the CVSS score of CVE-2026-24747?
CVE-2026-24747 has a CVSS v3 base score of 8.8 (NVD).
How do I remediate CVE-2026-24747?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-24747, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

Dependency Blast Radius

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

Explore →

Is Your Infrastructure Affected by CVE-2026-24747?

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

Start Free Scan →Browse All CVEs