Loading vulnerability…
An out-of-bounds write vulnerability exists in Cubism Core within Live2D Cubism Editor version 4.2.03. The vulnerability is triggered when the application processes a maliciously crafted MOC3 file containing a malformed Section Offset Table or Count Info Table, leading to memory corruption.
Mallory correlates every CVE against your assets, your vendors, and active adversary campaigns. Know which vulnerabilities matter for you, not just which ones are loud.
What it means. What to do now. Patch path, mitigations, and the assume-compromise checklist.
What an attacker gets, and what they’ve been doing with it.
If you can’t patch tonight, do this now.
Patch, then assume compromise.
1 valid exploit after Mallory filtered fakes, detection scripts, and README-only repos.
This repository provides a proof-of-concept (PoC) denial-of-service (DoS) exploit targeting applications that use the Live2D Cubism Core library to load MOC3 model files. The exploit is delivered as a specially crafted MOC3 file (referenced as 'exploit.moc3'), which, when loaded by a vulnerable application (such as Live2D Cubism Viewer or VTube Studio), causes an out-of-bounds memory write and crashes the application. The repository includes pattern files (src/moc3.hexpat and src/cmo3.hexpat) for use with the ImHex hex editor, allowing researchers to inspect and modify MOC3 and CAFF file formats. Several JSON files define the structure of the model and its associated data, but the actual exploit payload is the MOC3 file itself, which is not included in the repository but is referenced in the documentation. The purpose of the repository is to demonstrate the security weakness in the Live2D Cubism Core library and to encourage improved security practices. No code execution is achieved by this PoC, but the documentation notes that code execution may be possible with further research. The attack vector is local, requiring the victim to open the malicious file in a vulnerable application.
Products and vendors Mallory has correlated with this vulnerability. Open in Mallory to drill down to specific CPE configurations and version ranges.
Vendor-confirmed product mapping. Mallory continuously reconciles this list against your asset inventory.
No public activity tracked yet. Mallory keeps watching.
No public activity observed for this vulnerability.
Query your assets running an affected version, and investigate the blast radius.
Every observed campaign linking this CVE to a named adversary.
Malware families riding this exploit, with evidence and IOCs.
YARA, Sigma, Snort, and vendor rules, auto-deployed to your SIEM.
Cross-references every affected SKU, including bundled OEM variants.
Community discussion across Reddit, Mastodon, and other social sources.