CVE-2026-47748

MEDIUMPre-NVD 5.55.5
EchelonGraph scoreMEDIUM confidence

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

This medium-severity CVE scores 5.5 under a secondary CVSS source (NVD's own analysis pending). EPSS exploit probability: 0.2% (5th percentile of EPSS-scored CVEs). No GitHub Security Advisory CVSS is on record for this CVE.

Triggered by: Headline CVSS from a secondary CVSS source
Sources: EPSS, a secondary CVSS source
Elevated

Also known asEUVD-2026-37137 (ENISA EUVD)Source: ENISA EUVD

5.5EG
EchelonGraph verdictPlan mitigationRemediate 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.2%CVSS: 5.5Exploit: No code on recordExposed services: Not assessed

A fix is referenced (a reference tagged "Patch", often a source commit), but no release containing it is confirmed — find the release that contains it; until it is applied, mitigate (WAF / firewall / segmentation).

stable-diffusion.cpp is a pure C/C++ library for running diffusion model (Stable Diffusion, Flux, Wan, Qwen Image, Z-Image, and more) inference. Versions prior to master-584-0a7ae07 are vulnerable to an out-of-bounds reads error through PyTorch checkpoint pickle opcode parsing. The pickle .ckpt parser in src/model.cpp did not consistently check that enough input remained before reading opcode arguments or advancing the parser buffer with a crafted or truncated .ckpt file. Throughout the pickle parser, opcode handlers advanced the parser position with expressions such as buffer += N without first checking that buffer + N <= buffer_end. A truncated file could therefore cause reads past the end of the metadata buffer. LibFuzzer found crashes in under one second using malformed checkpoint inputs. Any application using affected stable-diffusion.cpp releases to load untrusted .ckpt model files could be vulnerable. The attack requires the victim or application to load a .ckpt file from an untrusted source, such as a downloaded model from a model sharing site. This issue has been fixed in version master-584-0a7ae07. If developers are unable to immediately update their applications, they can work around this issue by ensuring they do not load .ckpt checkpoint files from untrusted sources. They should prefer trusted model sources and safer formats such as .safetensors where possible.

CVSS v3
5.5
EG Score
5.5MEDIUMmedium confidence
EG Risk
41
EG Risk 41/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)
Severity55% × 45%
Impact severity (EG Severity): CVSS 5.5 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 referenced, but no release containing it is confirmed. Check the referenced fix and the vendor's advisory for a release that contains it and apply that within your standard update timelines; until then, restrict network exposure of the affected system or apply the vendor's mitigation.
EPSS PROB
0.2%
EPSS %ILE
5th
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 (5.5): severity, escalated by confirmed exploitation. This CVE's 5.5 is its impact severity (EG Severity), not escalated.

EG Severity
5.5 MEDIUMCVSS-B, impact only: no KEV listing, EPSS or EG-KEV tier raises it.a secondary CVSS source · CVSS v3.0 or v3.1
EG Likelihood
0.2% within 30 daysSource: FIRST EPSS (model v2026.06.15, score date 2026-10-25). 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: 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 referenced, but no release containing it is confirmed. Check the referenced fix and the vendor's advisory for a release that contains it and apply that within your standard update timelines; until then, restrict network exposure of the affected system or apply the vendor's mitigation.

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.

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

June 16, 2026

Last Modified

October 25, 2026

Advisory Details (2)

Auto-updated Jun 16, 2026
Fix referenced — no release confirmed yet. Sources: github_commit, github.
GitHub advisoryMentions a patch (unverified)

Out-of-bounds reads in PyTorch checkpoint pickle opcode parsing · Advisory · leejet/stable-diffusion.cpp · GitHub

https://github.com/leejet/stable-diffusion.cpp/security/advisories/GHSA-rx4w-x86j-vx57
GitHub commit

commit 0a7ae07f948e (leejet/stable-diffusion.cpp)

Fix landed in leejet/stable-diffusion.cpp commit 0a7ae07f948e — awaiting tagged release

https://github.com/leejet/stable-diffusion.cpp/commit/0a7ae07f948eff4611968a65a22bd7c7031ad74f

Weakness Classification(1)

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

Data Freshness Timeline

(refreshed 9× in last 7d / 36× 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 154 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 54 oldest rows on record are not shown and were not checked, so the counts can still include repeats.

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

Frequently asked(5)

What is CVE-2026-47748?
CVE-2026-47748 is a medium-severity vulnerability; its CVE record was published on June 16, 2026. stable-diffusion.cpp is a pure C/C++ library for running diffusion model (Stable Diffusion, Flux, Wan, Qwen Image, Z-Image, and more) inference. Versions prior to master-584-0a7ae07 are vulnerable to an out-of-bounds reads error through PyTorch checkpoint pickle opcode parsing. The pickle .ckpt…
When was the CVE record for CVE-2026-47748 published?
The CVE record for CVE-2026-47748 was published on June 16, 2026. That is the record's publication date; the vulnerability itself may have been made public earlier. EchelonGraph's copy of the record carries a last-modified date of October 25, 2026; the record at its source may have been updated since.
Is CVE-2026-47748 actively exploited?
CVE-2026-47748 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.2% probability of exploitation in the next 30 days (5th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-47748?
CVE-2026-47748 has a CVSS base score of 5.5 (a secondary CVSS source that NVD displays; NVD's own analysis pending).
How do I remediate CVE-2026-47748?
A fix for CVE-2026-47748 is referenced (a reference tagged "Patch", often a source commit), but EchelonGraph has no release containing it on record. Check that reference and the vendor's advisory for a release that contains the fix and update to it; until then, restrict network exposure of the affected system or apply the vendor's mitigation.

Dependency Blast Radius

Explore the affected products and dependency analysis for CVE-2026-47748

Explore →

Is Your Infrastructure Affected by CVE-2026-47748?

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