Live › vulnerability › CVE-2026-47235
Go to dashboardSimulationCraft's Battle.net profile importer writes more socket entries than its four-element gem arrays can hold, corrupting heap memory. An attacker who supplies a crafted profile can crash the tool and, per the advisory, run code.
Summary written from the sources below. Check the originals before acting.
First seen by InfraStack 2026-10-28 16:33 UTC. All times on this page are UTC.
Users who run SimulationCraft builds between release-820-01 and the May 7, 2026 nightly and import untrusted character profiles, addon exports, or Battle.net API data. Anyone on a release tag at or before release-820-01, or on the fixed nightly, is not affected by this flaw.
No product ranges from the sources yet.
simc --version or check the build identifier; builds after release-820-01 and before the May 7, 2026 nightly are exposed..simc files or Battle.net API data are used on the machine.simc-1205-01-516b5d7 or later; no containing release tag is available.Each row is the first time that source carried this signal. The analyst’s rows are its own findings.
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.
This page as .md · .json · in your agent: get_signal("CVE-2026-47235")
NVD data is provided by NIST and is public domain. Posts quoted belong to their authors.