Attack ChainAIDerived
Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain
-
AccessCraft malicious VOCALOID6 project file
-
DeliveryDeliver file to victim
-
ExploitVictim opens file in editor
-
ExecutionXML parser resolves external entity
-
ImpactLeak local files or crash application
Vulnerability Assessment
| Weakness |
CWE
OWASP Top 10:2025
A02:2025 - Security Misconfiguration
ASVS 5.0
V13 - Configuration XML external entity prevention
MITRE ATT&CK
2 techniques across 2 tactics: Initial Access, Collection The technique list with ATT&CK links and the kill-chain view is part of the Basic plan and up. |
| Exploitation Conditions | Exploitation requires the victim to open a specially crafted VOCALOID6 project file in the VOCALOID6 Editor; the vulnerability stems from the editor's XML parser not restricting external entity references (XXE) when loading project files. Limiting factors: the attack vector is local (AV:L) and demands user interaction (UI:R) - the attacker cannot trigger it remotely or without the user actively loading the malicious file - which substantially narrows realistic exploitation to social-engineering-based file delivery. No authentication or special privileges on the attacker side are needed (PR:N), and default configurations appear affected since the issue is improper default restriction of external entities. |
| Impact | This is a genuine but not emergency-priority vulnerability. The CVSS 3.1 vector (AV:L/AC:L/PR:N/UI:R) confirms this is NOT a remotely triggerable flaw: although PR:N means no attacker privileges are required, AV:L plus UI:R means the attack only fires when a victim locally opens a specially crafted VOCALOID6 project file - this is a file-parsing (XXE) class issue, not a network-reachable service bug. Impact is split: C:H (exfiltration of sensitive local files via external entity resolution) and A:H (denial of service), with no integrity impact (I:N), consistent with classic CWE-611 behavior. No EPSS score, no CISA KEV listing, and no public POC were provided in the intelligence set, so this is 'no public exploit identified at time of analysis.' The signals are internally consistent - there is no conflict between the network-vector language and the vector here, since the vendor correctly scored it as local/user-interaction-dependent. Net: for a consumer/prosumer music-production tool with a required-user-interaction local vector and no evidence of exploitation, this is a real but moderate-urgency patch item rather than a drop-everything priority. |
| Exploit ScenarioDerived | An attacker distributes a malicious VOCALOID6 project file (e.g., via a shared song project, forum download, or email attachment) containing a crafted XML external entity. When the victim opens the file in the VOCALOID6 Editor, the XML parser resolves the external entity, causing the application to read a local sensitive file and/or initiate outbound communication to exfiltrate it, or to hang/crash in a denial-of-service condition. No public exploit code was identified at time of analysis, but XXE payloads are well-documented and trivial to construct. |
Get an e-mail when this CVE is exploited, patched or re-scored. Free account.
Alert meAnalysisAIv1 – Oct 19, 2026
VOCALOID6 Editor fails to disable XML external entity resolution when it parses project files, so a crafted project can cause unintended outbound communication, disclosure of files readable by the editor process, or a denial-of-service crash. The issue is rated CVSS 7.1 and requires local file loading plus user interaction (AV:L/UI:R, PR:N), which limits practical exploitation to social-engineering delivery of a malicious project file. No public exploit code or active exploitation was identified in the provided intelligence, making this a genuine but not emergency-priority risk.
RemediationAI
Apply the fixed VOCALOID6 Editor release announced in Yamaha's support notices at https://www.vocaloid.com/en/news/support_64/ and https://www.vocaloid.com/news/support_64/, and verify details against JVN JVNVU93520490 at https://jvn.jp/en/vu/JVNVU93520490/; the provided data does not specify an exact patched version number. Until the update is installed, do not open VOCALOID6 project files from untrusted sources, and treat unsolicited project files as high-risk because exploitation only requires the user to load the file. Run the editor under a low-privilege account so any file disclosure is limited to files that account can read, and use a host firewall to restrict the editor process's outbound network access, with the trade-off that this may interfere with legitimate online activation, update, or content-download features. If project exchange with external parties is required, open files in a sandboxed VM or disposable environment, and maintain backups because a successful attack can crash the editor (A:H).
Affected VersionsENISA
Affected Packages
Source: OSV (Open Source Vulnerabilities)
Affects your stack
Affects 1 package in euvd
Checking this CVE against your own stacks and servers is part of the Basic plan and up.
Technical ContextAI · show details
The vulnerability is CWE-611 (Improper Restriction of XML External Entity Reference) in Yamaha's VOCALOID6 Editor. Project files are XML-based, and the editor's parser resolves external entity declarations instead of rejecting or sandboxing them. A crafted project can define entities that reference local files or network endpoints, causing the editor to read local content into output/error channels (C:H), initiate unintended connections, and exhaust resources or crash (A:H); integrity impact is none (I:N). The CPE cpe:2.3:a:yamaha_corporation:vocaloid6_editor:*:*:*:*:*:*:*:* uses a wildcard version, indicating the advisory should be treated as covering all VOCALOID6 Editor builds prior to the vendor's fixed release. The CVSS vector AV:L/AC:L/PR:N/UI:R/S:U/C:H/I:N/A:H confirms the attack surface is local file parsing with a required user action and no attacker privileges; this is not a remotely triggerable or memory-corruption flaw.
Know when Vocaloid6 Editor gets its next vulnerability
- Watch products and get an email when something new is published
- Check this CVE against your own stack and servers
- Exploit and PoC references, threat intelligence from 22 sources
No credit card · 7-day full trial
Severity by source
CVSS:4.0/AV:L/AC:L/AT:N/PR:N/UI:P/VC:H/VI:N/VA:H/SC:N/SI:N/SA:N
File-parsing XXE needs the victim to open a crafted project file, so AV:L and UI:R; no attacker privileges (PR:N); high confidentiality (file leak) and availability (DoS), no integrity impact.
Primary rating from Vendor (jpcert).
CVSS VectorVendor: jpcert
Lifecycle Timeline
3DescriptionCVE.org
VOCALOID6 Editor provided by Yamaha Corporation improperly restricts XML external entity references. Loading a specially crafted project file may the product to initiate unintended communication, potentially leading to the leak of sensitive information from the device where the product is installed or resulting in a denial-of-service (DoS) condition.
Executive ViewAI
VOCALOID6 Editor, a music production application, contains an XML external entity flaw that can be triggered when a user opens a crafted project file, potentially exposing locally readable files, causing unintended outbound communication, or crashing the editor. Because exploitation requires local file loading plus user interaction and no public exploit was identified at time of analysis, the practical risk is concentrated among users who exchange project files, rather than representing an emergency-priority exposure. Leadership should care about potential disclosure of creative assets or sensitive local files and about disruption to production workflows, but can manage the issue through user awareness, file-handling controls, and network isolation until a vendor patch is available.
No vendor-released patch identified at time of analysis; restrict opening of untrusted VOCALOID6 project files, block outbound network access from the editor, run the application with least privilege, isolate or sandbox VOCALOID6 Editor, and monitor for suspicious outbound connections or crashes.
Threat Intelligence Overview
How this decision was reached
The engine reads each signal below and applies a fixed list of rules from top to bottom. The first rule that matches sets the recommended action – like a statement, every line is shown.
What every action level means
SSVC AssessmentENISA
Priority Score
Attack Technique
XML External Entity (XXE) attacks exploit XML parsers that process Document Type Definitions (DTDs) without proper restrictions.
EUVD-2026-104124
GHSA-g42h-2hmf-m2p6
NVD
CVE.org
EPSS
Vulnrichment
Exploit-DB