CVE-2026-47235
7.5HighPublished 28 Oct 2026 · NVD status: Awaiting Analysis · AI triage by gemini-3.1-flash-lite
High
0CVSS v4.010
- Attack vector
- Adjacent network
- Complexity
- High
- Privileges
- None
- User action
- Passive
- Impact
- Full C/I/A compromise
- Weakness
- CWE-122, CWE-787
What an attacker gets
Attackers can achieve remote code execution by providing a malicious .simc profile or intercepting Battle.net API responses. This requires a user to load the crafted file or the application to process compromised API data.
Root cause
The application fails to bound the JSON socket array index, leading to a heap-based buffer overflow that corrupts vector pointers.
Affected versions
SimulationCraft builds after release-820-01 and before the May 7, 2026 nightly build.
CVSS v4.0 · CVSS:4.0/AV:A/AC:H/AT:P/PR:N/UI:P/VC:H/VI:H/VA:H/SC:L/SI:L/SA:L/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X
Fix & remediation
Update to the nightly build simc-1205-01-516b5d7 or later. Avoid loading untrusted .simc profile files or connecting to unverified API sources until patched.
AI-suggested. Run it in staging first and check it against the vendor advisory. Why?
NVD description
SimulationCraft is a tool to explore combat mechanics in World of Warcraft. In builds after release-820-01 and before the identified May 7, 2026 nightly, the `bcp_api.cpp` loop over the JSON `sockets` array uses `slot_data["sockets"].Size()` without bounding `gem_idx` by `MAX_GEM_SLOTS`, which is four in `engine/sc_enums.hpp`. The destination `gem_id` and `gem_bonus_id` arrays in `engine/item/item.hpp` have only four elements. More than four socket entries therefore write beyond `gem_id` into the adjacent `gem_bonus_id` vector storage; `bonus_list` entries can also access `gem_bonus_id` out of bounds. Corrupting a vector's `_M_start` pointer causes the `item_t` destructor to free an attacker-influenced pointer during normal cleanup. The advisory reports crashes and code execution demonstrated in a testing environment. Attack inputs can arrive through a malicious `.simc` profile with a `[[equipment]]` section, a compromised addon export, or `Battle.net API` responses modified by an attacker with a privileged network position. The fix is contained in the nightly build identified as simc-1205-01-516b5d7; no containing release tag is available.