Skip to content
Patch Next
Sign inAdd to your agent

← Actionable
Medium, CVSS 5.9amended

Excessive allocated memory on the host when guests don't have stdio

CVE-2026-115381GHSA-gqmc-89g8-p25r

What to do

Vendor fix available. Upgrade each affected package to the fixed version on its release line (wasmtime-wasi 49.0.2, 48.0.4, 36.0.17), redeploy, then verify what is actually installed.

This page has no inventory attached, so it cannot say whether you are affected. A vendor fix is not proof that your deployment is fixed.

Add to your agent

Affected packages

  • crates.io wasmtime-wasi

    Affected
    >= 0.0.0-0, < 36.0.17>= 37.0.0, < 48.0.4>= 49.0.0, < 49.0.2
    Fixed in
    36.0.17, 48.0.4, 49.0.2

Sources

Severity and exploitation
Exploitation
No confirmed exploitation recorded. Patch Next marks exploitation only from CISA KEV.
CVSS 4.0
5.9 · CVSS:4.0/AV:N/AC:L/AT:P/PR:L/UI:P/VC:N/VI:N/VA:H/SC:N/SI:N/SA:N · score source
EPSS
  • CVE-2026-115381: 0.21% estimated exploitation activity in the next 30 days; percentile 11.49 (FIRST EPSS, 2026-11-03). This is a model estimate, not proof of exploitation or customer exposure.
Source description

As published by the source; long descriptions are shortened.

This is an entry in the RustSec database for the Wasmtime security advisory located at https://github.com/bytecodealliance/wasmtime/security/advisories/GHSA-gqmc-89g8-p25r For more information see the GitHub-hosted security advisory.

Dates and revisions
Published by the source
Last modified by the source
Source last checked
  1. Revision 2 · amended ·

    Reviewed OSV alias/range/CVSS4 correction; package source scopes and original publication preserved. No customer finding resolved.

  2. Revision 1 · created ·

    Published from osv record RUSTSEC-2026-0322

Agent brief

Preview the exact text before you copy it. Commands are read-only suggestions; review them before running anything.

# Patch Next advisory brief: CVE-2026-115381

Advisory: Excessive allocated memory on the host when guests don't have stdio
IDs: CVE-2026-115381, GHSA-gqmc-89g8-p25r
Record: https://patchnext.com/advisories/cve-2026-115381 (revision 2, source checked 25 Oct 2026, 04:53 UTC)
Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected.
Severity: Medium (CVSS 5.9)
Exploitation: no confirmed exploitation recorded. Patch Next confirms exploitation only from CISA KEV.
Vendor response: Vendor fix available; fixed versions by package: wasmtime-wasi 49.0.2, 48.0.4, 36.0.17. A vendor fix does not mean a deployment is fixed.

## Affected components
- crates.io wasmtime-wasi: affected >= 0.0.0-0, < 36.0.17; >= 37.0.0, < 48.0.4; >= 49.0.0, < 49.0.2; fixed in 36.0.17, 48.0.4, 49.0.2

## Suggested inspection (read-only)
- crates.io wasmtime-wasi: check the installed version with your package manager.

## Supported action
Upgrade each affected component to a fixed version on its release line. For a transitive dependency, upgrade the parent package or add an override or constraint, then regenerate the lockfile. Redeploy every environment that ran an affected version.

## Required regression checks
- Run the test suite and a production build.
- Exercise the features that depend on wasmtime-wasi.
- Repeat the inspection and confirm that only fixed versions remain installed.

## Rollback considerations
- Keep the previous lockfile and deployment artifact. Rolling back reinstates the vulnerable version, so apply any documented mitigation while you fix forward.

## Unresolved questions
- Which deployments run an affected version?
- Exploitation status can change. Check again before lowering the priority.
- Mark the work resolved only after the fixed version is verified in production.

## Sources
- Verified: https://osv.dev/vulnerability/RUSTSEC-2026-0322 (OSV record RUSTSEC-2026-0322 lists affected ranges: crates.io wasmtime-wasi >=0.0.0-0 =37.0.0 =49.0.0 <49.0.2 (fixed))

Commands are suggestions: review each one before running it.

Loading voting…