CVE-2026-65918

HIGHPre-NVD 7.17.1
EchelonGraph scoreMEDIUM confidence

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

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

Triggered by: GitHub Security Advisory CVSS
Sources: EPSS, GitHub Security Advisory, a secondary CVSS source
Elevated

Also known asEUVD-2026-48341 (ENISA EUVD) · GHSA-xhgh-4jhq-chj3 (GitHub Security Advisories)Source: ENISA EUVD

7.1EG
EchelonGraph verdictPlan a fixRemediate within your standard update timelines (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.4%CVSS: 7.1Exploit: No code on recordExposed services: Not assessed

A fix is available — apply it.

PyTorch torchvision through 0.28.0, fixed in commit 4e05dc2, contains an out-of-bounds heap read vulnerability in the GIF decoder's read_from_tensor callback that passes unclamped length to memcpy. Attackers can supply malicious or truncated GIF files to cause denial of service via segmentation fault or disclose adjacent heap memory contents.

CVSS
7.1
EG Score
7.1HIGHmedium confidence
EG Risk
48
EG Risk 48/100

EG Risk is EchelonGraph's 0–100 priority score. It fuses impact severity (EG Severity, the CVSS base score, never the KEV-floored or EPSS-lifted EG Score) with real-world exploitation and automatability, under weights EchelonGraph set by hand, so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner.

How it’s computed (value × EchelonGraph’s weight)
Severity71% × 45%
Impact severity (EG Severity): CVSS 7.1 of 10. Never the KEV-floored or EPSS-lifted EG Score.
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 or medium mission impact; Track* at high (mission-essential systems).
Exploitation public PoC (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact partial (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.
EPSS PROB
0.4%
EPSS %ILE
39th
KEV
Not listed

What the EG score is made of (scorer v4.0: the three questions the 0–10 score mixes, published apart · methodology)

The EG score (7.1): severity, escalated by confirmed exploitation. This CVE's 7.1 is its impact severity (EG Severity), not escalated.

EG Severity
7.1 HIGHCVSS-B, impact only: no KEV listing, EPSS or EG-KEV tier raises it.GitHub Security Advisory CVSS
EG Likelihood
0.4% within 30 daysSource: FIRST EPSS (model v2026.06.15, score date 2026-11-11). FIRST's exploitation probability, not an EchelonGraph model.
Confirmed exploitation
None on record (CISA KEV, EG-KEV Tier 1)Reported apart from the likelihood: an observed fact, not a probability.
EG Priority
SSVC Track at medium mission impactTrack at low or medium mission impact; Track* at high (mission-essential systems).CISA BOD 26-04: 60 days if the affected system is publicly exposed; Fix on system upgrade if it is not.Each input and its source, and whom BOD 26-04 binds: the SSVC and BOD 26-04 blocks below.

SSVC (CISA's decision table, applied by EchelonGraph)Track at low or medium mission impact; Track* at high (mission-essential systems).

A fix is available. Apply it within your standard update timelines.

Exploitation public PoC (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact partial (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)60 days if the affected system is publicly exposed; Fix on system upgrade if it is not.

The score's inputs: In CISA KEV no (CISA's KEV catalog) · Automatable no (CISA Vulnrichment) · Technical impact partial (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 23, 2026

Last Modified

October 24, 2026

Advisory Details (4)

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

PyTorch torchvision GIF Decoder Out-of-bounds Heap Read | Advisories | VulnCheck

https://www.vulncheck.com/advisories/pytorch-torchvision-gif-decoder-out-of-bounds-heap-read
GitHub pull request

Fix gif decoder bug

Fix merged in pytorch/vision PR #9520 on 2026-06-22 — awaiting tagged release

https://github.com/pytorch/vision/pull/9520
Web page

Out-of-bounds read in the GIF decoder when decoding an untrusted image · Issue #9551 · pytorch/vision · GitHub

https://github.com/pytorch/vision/issues/9551
GitHub commit

commit 4e05dc22f5f0 (pytorch/vision)

Fix landed in pytorch/vision commit 4e05dc22f5f0 — awaiting tagged release

https://github.com/pytorch/vision/commit/4e05dc22f5f050a9528cc0ea09ceca6cdaf8f4ed

Patch Availability(2)

Vendor / EcosystemFix (by version range) / PatchReleasedSource
redhatrhoai/odh-workbench-jupyter-pytorch-llmcompressor-cuda-py312-rhel9:17918671892026-10-21redhat
redhatrhoai/odh-training-rocm64-torch29-py312-rhel9:17918094022026-10-19redhat

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

(4 across 4 ecosystems)
Debian:11(1)
PackageVulnerable rangeFix by version rangeDependents
pytorch-vision0.13.1-1 ... 0.8.2-1 (15 versions)
  • every version on: no fix on record
—
Debian:12(1)
PackageVulnerable rangeFix by version rangeDependents
pytorch-vision0.14.1-2 ... 0.29.1-1~exp1 (13 versions)
  • every version on: no fix on record
—
Debian:13(1)
PackageVulnerable rangeFix by version rangeDependents
pytorch-vision0.21.0-3 ... 0.29.1-1~exp1 (7 versions)
  • every version on: no fix on record
—
Debian:14(1)
PackageVulnerable rangeFix by version rangeDependents
pytorch-vision0.21.0-3 ... 0.29.1-1~exp1 (7 versions)
  • every version on: no fix on record
—

Weakness Classification(1)

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

Data Freshness Timeline

(refreshed 8× in last 7d / 38× 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 its CVE.org record (CNA or CISA ADP). An arrow marks a change the record states ("CVSS → 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). "EchelonGraph re-scored" is our own recompute of this CVE's score, not an update from a source, and is not counted in the refreshes above. Most recent first.

Showing the most recent 100 of 274 rows 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 174 oldest rows on record are not shown and were not checked, so the counts can still include repeats.

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

Frequently asked(5)

What is CVE-2026-65918?
CVE-2026-65918 is a high-severity vulnerability; its CVE record was published on July 23, 2026. PyTorch torchvision through 0.28.0, fixed in commit 4e05dc2, contains an out-of-bounds heap read vulnerability in the GIF decoder's read_from_tensor callback that passes unclamped length to memcpy. Attackers can supply malicious or truncated GIF files to cause denial of service via segmentation…
When was CVE-2026-65918 made public?
CVE-2026-65918 was made public on July 13, 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 23, 2026. EchelonGraph's copy of the record carries a last-modified date of October 24, 2026; the record at its source may have been updated since.
Is CVE-2026-65918 actively exploited?
CVE-2026-65918 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.4% probability of exploitation in the next 30 days (39th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-65918?
CVE-2026-65918 has a CVSS base score of 7.1 (a secondary CVSS source that NVD displays; NVD's own analysis pending).
How do I remediate CVE-2026-65918?
A fix for CVE-2026-65918 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2026-65918 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-65918

Explore →

Is Your Infrastructure Affected by CVE-2026-65918?

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