Quick answers
- Is CVE-2026-47747 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-47747 being exploited in the wild.
- How severe is CVE-2026-47747?
- High severity, with a CVSS score of 7.8, published 16 June 2026.
- Which products and versions are affected?
- Leejet Stable-Diffusion.Cpp < master-584-0a7ae07.
- Is there a fix for CVE-2026-47747?
- A patch was published on 2026-04-19: Fix committed in master-584-0a7ae07 Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
- How is CVE-2026-47747 attacked?
- It is attacked with local access, in a software library.
- Am I affected by CVE-2026-47747?
- Check whether you run Leejet Stable-Diffusion.Cpp at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.
Technical details
A heap-based buffer overflow exists in the BINUNICODE opcode handler within src/model.cpp of stable-diffusion.cpp. The vulnerability is caused by sign confusion when validating the opcode length field; an attacker can provide a negative signed integer (e.g., -1) that bypasses length checks but is interpreted as a massive unsigned value (SIZE_MAX) during a subsequent memcpy operation. This leads to immediate heap corruption. Exploitation requires a user to load a malformed .ckpt checkpoint file. The issue is resolved in version master-584-0a7ae07 by refactoring the checkpoint loading logic.
Affected products
- leejet stable-diffusion.cpp < master-584-0a7ae07
Timeline
- 2026-04-19: patched: Fix committed in master-584-0a7ae07
- 2026-05-22: advisory: GitHub Security Advisory published
- 2026-06-16: disclosed: CVE published to NVD