CVE-2026-115393
Description
A flaw was found in Wasmtime. Several Store application programming interfaces (APIs) fail to verify that objects belong to the expected execution engine. If an embedding application mixes objects between different engines, this type confusion can lead to memory corruption, including out-of-bounds stack writes, or cause crashes resulting in a Denial of Service (DoS).
Statement
This vulnerability is rated as having a Low impact because exploitation requires an embedding host application to improperly share runtime structures across distinct engine instances, which untrusted WebAssembly guests cannot trigger on their own. In standard deployments across Red Hat Enterprise Linux and containerized environments, host integrations maintain isolated engine contexts or manage single runtime lifecycles. Consequently, the flaw cannot be exploited without specific and flawed host-level API usage, limiting the overall security exposure.
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).
The following CVSS metrics and score provided are preliminary and subject to review.
CVSS v3 Score Breakdown
| Red Hat | NVD | cve.org | |
|---|---|---|---|
| Base Score | 3.8 | N/A | 3.8 |
| Attack Vector | Local | N/A | Local |
| Attack Complexity | High | N/A | High |
| Privileges Required | High | N/A | High |
| User Interaction | Required | N/A | Required |
| Scope | Unchanged | N/A | Unchanged |
| Confidentiality | Low | N/A | Low |
| Integrity Impact | Low | N/A | Low |
| Availability Impact | Low | N/A | Low |
Vector
Red Hat: CVSS:3.1/AV:L/AC:H/PR:H/UI:R/S:U/C:L/I:L/A:L
cve.org: CVSS:3.1/AV:L/AC:H/PR:H/UI:R/S:U/C:L/I:L/A:L
Understanding the Weakness (CWE)
Other
Technical Impact: Varies by Context
When the product accesses the resource using an incompatible type, this could trigger logical errors because the resource does not have expected properties.
Availability,Integrity,Confidentiality
Technical Impact: Read Memory; Modify Memory; Execute Unauthorized Code or Commands; DoS: Crash, Exit, or Restart
If a memory buffer is accessed using an incompatible type, and the allocated buffer is smaller than the type that the code is attempting to access, then an attacker could read or write memory outside the bounds of the buffer, leading to a crash or possibly code execution.
Frequently Asked Questions
Not sure what something means? Check out our Security Glossary.
Want to get errata notifications? Sign up here.
