EUVD-2026-58744Severity by source
AV:L/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:L
Exploitation requires local library API invocation with attacker-controlled IDs; description explicitly confirms no data disclosure, so C:N overrides the provided C:L.
Primary rating from Vendor (GitHub_M).
CVSS VectorVendor: GitHub_M
Lifecycle Timeline
2DescriptionCVE.org
Capstone is a disassembly framework. Prior to version 6.0.0-Alpha9, Capstone's public cs_insn_name() API forwards caller-supplied instruction IDs directly to the selected architecture backend. Most backends validate the ID before indexing instruction-name tables, but the M68K and RISCV backends have missing or incomplete bounds checks. On a Capstone handle opened for M68K or RISCV, a caller-controlled invalid instruction ID can trigger an out-of-bounds read and crash the process. The demonstrated impact is availability loss in applications or bindings that expose instruction-name lookup to untrusted IDs. No code execution or data disclosure was demonstrated. Version 6.0.0-Alpha9 patches the issue.
AnalysisAI
Out-of-bounds read in Capstone's cs_insn_name() public API crashes host processes when the M68K or RISCV architecture backends receive caller-controlled invalid instruction IDs that bypass missing or incomplete bounds checks. Affected are all Capstone deployments prior to 6.0.0-Alpha9 where those two architecture handles are in use and instruction ID input is not sanitized by the calling application. The demonstrated impact is strictly a denial-of-service crash; no code execution or data exfiltration was shown, and no public exploit or active exploitation has been identified at time of analysis.
Technical ContextAI
Capstone (cpe:2.3:a:capstone-engine:capstone:*:*:*:*:*:*:*:*) is a multi-architecture disassembly framework widely used in security tooling, reverse-engineering platforms, and language bindings. The vulnerability is classified CWE-125 (Out-of-Bounds Read): the public cs_insn_name() API forwards a caller-supplied integer instruction ID directly into architecture-specific backend dispatch logic. While most backends validate the ID before indexing their instruction-name string tables, the M68K and RISCV backends lack sufficient bounds enforcement, allowing an out-of-range index to read memory beyond the array boundary. The crash results from the invalid memory access rather than any memory-corruption write primitive, which is why no code execution path was demonstrated. The fix in 6.0.0-Alpha9 adds the missing validation in both backends.
RemediationAI
Upgrade to Capstone 6.0.0-Alpha9, which patches the missing bounds checks in both the M68K and RISCV backends per the vendor advisory at https://github.com/capstone-engine/capstone/security/advisories/GHSA-jrw4-wj52-2vw8. For applications unable to upgrade immediately, the effective compensating control is to validate instruction IDs against architecture-specific valid ranges in the calling code before passing them to cs_insn_name(), rejecting any ID outside the known maximum for the active architecture. Alternatively, restrict Capstone handle creation to trusted, internally-generated instruction IDs rather than any caller-supplied value. Applications that do not use M68K or RISCV architecture handles are not affected and require no action beyond this audit. Note that the 6.0.0-Alpha9 release is an alpha; operators with stability requirements should assess whether a pre-release is acceptable or whether the calling-code validation workaround better suits production environments.
Integer overflow in the cs_winkernel_malloc function in winkernel_mm.c in Capstone 3.0.4 and earlier allows attackers to
Heap buffer overflow in Capstone's SuperH (SH) architecture floating-point disassembler affects all releases through 6.0
Out-of-bounds read in Capstone's SuperH (SH) architecture disassembler crashes the host process when fed crafted SH2A or
Capstone disassembly framework package in Alpine Linux has been patched at version 5.0.8-r0, addressing an unspecified v
Same weakness CWE-125 – Out-of-bounds Read
View allVendor StatusVendor
SUSE
Severity: Moderate| Product | Status |
|---|---|
| SUSE Linux Enterprise High Performance Computing 15 SP7 | Affected |
| SUSE Linux Enterprise Micro 5.5 | Affected |
| SUSE Linux Enterprise Module for Server Applications 15 SP7 | Affected |
| SUSE Linux Enterprise Server 15 SP7 | Affected |
| SUSE Linux Enterprise Server 16.0 | Affected |
| SUSE Linux Enterprise Server 16.1 | Affected |
| SUSE Linux Enterprise Server for SAP Applications 15 SP7 | Affected |
| SUSE Linux Enterprise Server for SAP applications 16.0 | Affected |
| SUSE Linux Enterprise Server for SAP applications 16.1 | Affected |
| SUSE Linux Micro 6.0 | Affected |
| SUSE Linux Micro 6.1 | Affected |
| SUSE Linux Micro 6.2 | Affected |
| openSUSE Leap 16.0 | Affected |
| SUSE Linux Enterprise High Performance Computing 15 SP5 | Affected |
| SUSE Linux Enterprise High Performance Computing 15 SP5-LTSS | Affected |
| SUSE Linux Enterprise Module for Server Applications 15 SP5 | Affected |
| SUSE Linux Enterprise Module for Server Applications 15 SP6 | Affected |
| SUSE Linux Enterprise Server 15 SP5 | Affected |
| SUSE Linux Enterprise Server 15 SP5-LTSS | Affected |
| SUSE Linux Enterprise Server 15 SP6 | Affected |
| SUSE Linux Enterprise Server 15 SP6-LTSS | Affected |
| SUSE Linux Enterprise Server for SAP Applications 15 SP5 | Affected |
| SUSE Linux Enterprise Server for SAP Applications 15 SP6 | Affected |
| SUSE Linux Enterprise High Performance Computing 15 SP5-ESPOS | Affected |
| SUSE Linux Enterprise High Performance Computing 15 SP6 | Affected |
| openSUSE Leap 15.5 | Affected |
| openSUSE Leap 15.6 | Affected |
| openSUSE Leap Micro 5.5 | Affected |
Share
External POC / Exploit Code
Leaving vuln.today