Quick answers
- Is CVE-2026-104679 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-104679 being exploited in the wild.
- How severe is CVE-2026-104679?
- High severity, with a CVSS score of 7.1, published 19 October 2026.
- Which products and versions are affected?
- Yamaha VOCALOID6 Editor 6.13.2 and earlier.
- Is there a fix for CVE-2026-104679?
- Yes: fixed in VOCALOID6 Editor 6.13.3. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
- How is CVE-2026-104679 attacked?
- It is attacked with local access, in a software library.
- Am I affected by CVE-2026-104679?
- Check whether you run Yamaha VOCALOID6 Editor 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.
How to fix
- Fixed in: VOCALOID6 Editor 6.13.3
Technical details
The vulnerability is an XML External Entity (XXE) injection flaw in VOCALOID6 Editor's handling of project files (.vpr and .vsqx formats). A user must manually open a specially crafted project file to trigger the vulnerability, which can then read local files or cause a denial-of-service condition. The issue has been fixed in version 6.13.3.
Affected products
- Yamaha VOCALOID6 Editor 6.13.2 and earlier
Timeline
- 2026-10-19: disclosed
- 2026-09-17: patched: VOCALOID6 Editor Updater Ver.6.13.3 released