CVE-2026-49263
Description
A flaw was found in Capstone, a disassembly framework, affecting its WebAssembly (WASM) backend. A remote attacker could exploit this by providing a specially crafted br_table instruction. This could lead to a denial of service, where the disassembler gets stuck in a loop, or cause parser desynchronization, leading to incorrect disassembly of subsequent instructions. This issue impacts the availability and integrity of the disassembler.
Statement
A flaw of moderate impact was found in the Capstone disassembly framework's WebAssembly (WASM) backend, which is shipped in Red Hat Enterprise Linux, Red Hat In-Vehicle OS, and OpenShift (via the RHEL CoreOS 9 container image), as well as in Fedora, EPEL, and Red Hat Hardened Images community offerings and community packages that bundle Capstone (such as imhex and pe-bear). Capstone's WASM decoder accepts attacker-controlled raw WASM instruction bytes through the public cs_disasm() and cs_disasm_iter() APIs. For a large but well-formed br_table instruction, the decoder accumulates the immediate length in a wider local variable but returns it through a uint16_t instruction-size path. When the encoded instruction length is exactly 65,536 bytes, the size wraps to zero and cs_disasm() can repeatedly decode the same instruction without advancing, causing a denial of service; for larger lengths, cs_disasm_iter() advances into the middle of the br_table payload and decodes target bytes as subsequent instructions, causing parser desynchronization and incorrect disassembly output. The flaw affects the availability and, to a lesser degree, the integrity of applications that use Capstone to disassemble attacker-controlled WASM content; there is no known confidentiality impact. Red Hat rated this flaw Moderate severity (CVSS 3.1 score 6.8), which is higher than the Low rating in the upstream CVEORG record; the difference stems from differing CVSS metric assessments between the issuers. For Red Hat Enterprise Linux, Red Hat In-Vehicle OS, and OpenShift RHEL CoreOS 9, the fix is currently deferred: exploitation requires an application to pass attacker-controlled WASM bytes to the affected disassembly APIs, so the residual risk is limited to denial of service or incorrect disassembly in such applications. For the community (Fedora, EPEL) and Red Hat Hardened Images offerings, a fix is being pursued through the delegated maintenance process.
Mitigation
Mitigation for this issue is either not available or the currently available options do not meet the Red Hat Product Security criteria comprising ease of use and deployment, applicability to widespread installation base, or stability. Upgrading to Capstone 6.0.0-Alpha9, which contains the upstream fix, addresses this issue.
Common Vulnerability Scoring System (CVSS) Score Details
Info alert:Important note
CVSS scores for open source components depend on vendor-specific factors (e.g. version or build chain). Therefore, Red Hat's score and impact rating can be different from NVD and other vendors. Red Hat remains the authoritative CVE Naming Authority (CNA) source for its products and services (see Red Hat classifications).
CVSS v3 Score Breakdown
| Red Hat | NVD | cve.org | |
|---|---|---|---|
| Base Score | 6.8 | N/A | N/A |
| Attack Vector | Local | N/A | N/A |
| Attack Complexity | Low | N/A | N/A |
| Privileges Required | None | N/A | N/A |
| User Interaction | None | N/A | N/A |
| Scope | Unchanged | N/A | N/A |
| Confidentiality | None | N/A | N/A |
| Integrity Impact | Low | N/A | N/A |
| Availability Impact | High | N/A | N/A |
Vector
Red Hat: CVSS:3.1/AV:L/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:H
Understanding the Weakness (CWE)
Availability
Technical Impact: DoS: Crash, Exit, or Restart; DoS: Resource Consumption (Memory); DoS: Instability
This weakness can generally lead to undefined behavior and therefore crashes. When the calculated result is used for resource allocation, this weakness can cause too many (or too few) resources to be allocated, possibly enabling crashes if the product requests more resources than can be provided. If the calculated result involves time values, then the product might crash when it encounters a time that is less than the previously-calculated time.
Integrity
Technical Impact: Modify Memory
If the value in question is important to data (as opposed to flow), simple data corruption has occurred. Also, if the overflow/wraparound results in other conditions such as buffer overflows, further memory corruption may occur.
Confidentiality,Availability,Access Control
Technical Impact: Execute Unauthorized Code or Commands; Bypass Protection Mechanism
This weakness can sometimes trigger buffer overflows, which can be used to execute arbitrary code. This is usually outside the scope of the product's implicit security policy.
Availability,Other
Technical Impact: Alter Execution Logic; DoS: Crash, Exit, or Restart; DoS: Resource Consumption (CPU)
If the overflow/wraparound occurs in a loop index variable, this could cause the loop to terminate at the wrong time - too early, too late, or not at all (i.e., infinite loops). With too many iterations, some loops could consume too many resources such as memory, file handles, etc., possibly leading to a crash or other DoS.
Access Control
Technical Impact: Bypass Protection Mechanism
If integer values are used in security-critical decisions, such as calculating quotas or allocation limits, integer overflows can be used to cause an incorrect security decision.
Access Control
Technical Impact: Bypass Protection Mechanism; DoS: Crash, Exit, or Restart
If integer values are used in time-based, security-critical decisions, such as calculating expiration times or determining whether an event occurs within a specific time or date range, to cause an incorrect security decision. The consequences could even include "self-DoS" if the overflow produces a time value that is not accounted for in protection mechanism logic [REF-1570].
Frequently Asked Questions
Not sure what something means? Check out our Security Glossary.
Want to get errata notifications? Sign up here.