Skip to main content
VulnerabilityPublished Updated

CVE-2026-49282: capstone · Out-of-bounds Read

Affects capstoneSource CVE Database V5

0
Compare

Not known to be exploited · CVSS 5.1 Medium : upgrade to 6.0.0-Alpha9 when convenient.

Data as of 12 Nov 2026, 23:24 UTC

CVSS 3.1 base score
5.1Medium
How severe the flaw is on the 0–10 CVSS scale.
EPSS
0.1% chance of exploitation in 30 days – higher than 7% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
Patch
Available – fixed in 6.0.0-Alpha9
CVSS:3.1/AV:L/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:L

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 14 Aug 2026

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponized: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 13 Nov 2026.

What to do

Upgrade capstone to 6.0.0-Alpha9.

Affected software

ProductAffectedFixed in
capstone-enginecapstoneAffected
  • <6.0.0-Alpha9
Fixed in
  • 6.0.0-Alpha9
GitHubcapstone-engine/capstonepkg:github/capstone-engine/capstoneOther threatsAffected
  • =6.0.0-Alpha9
Fixed in–

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

AI-suggested

Upgrade to Capstone version 6.0.0-Alpha9 or later, which contains the fix for this vulnerability. Patch status is not explicitly confirmed beyond the version containing the fix; verify with the vendor advisory for the latest remediation guidance.

Description

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.

References

Community reviews

Loading reviews…