LiveActive security incident?Get immediate response
CVE Record

CVE-2026-27204: Wasmtime WASI implementations are vulnerable to guest-controlled resource exhaustion

Wasmtime is a runtime for WebAssembly. Prior to versions 24.0.6, 36.0.6, 4.0.04, 41.0.4, and 42.0.0, Wasmtime's implementation of WASI host interfaces are susceptible to guest-controlled resource exhaustion on the host. Wasmtime did not appropriately place limits on resource allocations requested by the guests. This serves as a Denial of Service vector. Wasmtime 24.0.6, 36.0.6, 40.0.4, 41.0.4, and 42.0.0 have all been released with the fix for this issue. These versions do not prevent this issue in their default configuration to avoid breaking preexisting behaviors. All versions of Wasmtime have appropriate knobs to prevent this behavior, and Wasmtime 42.0.0-and-later will have these knobs tuned by default to prevent this issue from happening. There are no known workarounds for this issue without upgrading. Embedders are recommended to upgrade and configure their embeddings as necessary to prevent possibly-malicious guests from triggering this issue.

MediumCVSS 6.9Not KEV-listedUpdated
Glexia's TakeAutomated analysismoderate

Security readout for executives and security teams

Plain-English summary

Wasmtime hosts running untrusted WebAssembly with WASI may let a guest consume excessive host resources, causing service disruption. The issue affects multiple pre-fixed Wasmtime branches. Fixes exist, but some fixed versions require explicit configuration to enforce protective limits; Wasmtime 42.0.0 and later tunes these by default.

Executive priority

Treat as a timely availability-risk update for platforms using Wasmtime with untrusted WebAssembly. It is not currently evidenced as actively exploited, but affected multi-tenant or customer-facing execution environments should be prioritized because a guest may disrupt host service availability.

Technical view

CVE-2026-27204 is a resource exhaustion flaw in Wasmtime WASI host interfaces. Guest-controlled requests were not sufficiently bounded, enabling denial of service against host availability. Affected ranges include versions before 24.0.6, 25.x before 36.0.6, 37.x before 40.0.4, and 41.x before 41.0.4. Related controls include random-size limits, resource table capacity, and hostcall fuel.

Likely exposure

Exposure is most relevant for applications embedding Wasmtime and allowing potentially malicious or tenant-controlled WebAssembly guests using WASI. Internal-only, trusted-module deployments have lower practical risk. The source bundle does not indicate broad internet scanning or automatic exploitation.

Exploitation context

The advisory describes a denial-of-service condition, not code execution or data theft. CVSS lists low attack complexity but requires privileges, user interaction, and a present attack requirement. CISA KEV status is false in the provided data, and no cited source claims active exploitation.

Researcher notes

The fix is released across maintained branches, but the advisory notes default behavior in fixed versions may not fully prevent the issue until 42.0.0 and later. Validation should focus on embedding configuration, WASI exposure, and guest trust boundaries. Evidence is insufficient to claim exploitation in the wild.

Mitigation direction

  • Upgrade Wasmtime to 24.0.6, 36.0.6, 40.0.4, 41.0.4, or 42.0.0 or later.
  • For fixed versions before 42.0.0, configure resource-limiting knobs as appropriate for your embedding.
  • Review WASI limits including random size, resource table capacity, and hostcall fuel settings.
  • Prioritize systems executing untrusted, third-party, or multi-tenant WebAssembly guests.
  • If unable to upgrade, check Bytecode Alliance guidance; sources state no known workaround without upgrading.

Validation and detection

  • Inventory services embedding Wasmtime and identify the linked runtime version.
  • Confirm whether the application enables WASI host interfaces for guest modules.
  • Determine whether guests are trusted, third-party, user-supplied, or multi-tenant.
  • Verify fixed versions are deployed in build manifests, lockfiles, containers, and runtime artifacts.
  • Review embedding code for configured resource limits after upgrading.
Prepared
Confidence
high
Sources
9

Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.

Potential ATT&CK relevance

Conservative CVE-to-ATT&CK context

These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.

ATT&CK lookup starting points

Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.

cwe · low confidence lookup

CWE-400: Exact CWE lookup

Use the exact CWE identifier as the starting point before reviewing related ATT&CK behavior. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.

Open ATT&CK lookup
cwe · low confidence lookup

CWE-770: Exact CWE lookup

Use the exact CWE identifier as the starting point before reviewing related ATT&CK behavior. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.

Open ATT&CK lookup
cwe · low confidence lookup

CWE-774: Exact CWE lookup

Use the exact CWE identifier as the starting point before reviewing related ATT&CK behavior. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.

Open ATT&CK lookup
cwe · low confidence lookup

CWE-789: Exact CWE lookup

Use the exact CWE identifier as the starting point before reviewing related ATT&CK behavior. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.

Open ATT&CK lookup
cve · low confidence lookup

CVE-2026-27204 mapping review

Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.

Open ATT&CK lookup
Vulnerability profileCVE Program record
Severity
Medium
CVSS
6.9 (4.0)
Known Exploited
No
Published

Vector: CVSS:4.0/AV:N/AC:L/AT:P/PR:L/UI:P/VC:N/VI:N/VA:H/SC:N/SI:N/SA:H

Official CVE source material

CNA and ADP enrichment extracted from CVE v5

These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.

1CVSS vectors
0Timeline events
0ADP providers
8Source links

CVSS vector scores

1 official score

We collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.

ScoreVersionSeverityVectorExploitImpactSource
6.9CVSS 4.0MediumCVSS:4.0/AV:N/AC:L/AT:P/PR:L/UI:P/VC:N/VI:N/VA:H/SC:N/SI:N/SA:H——Primary CVE score

Vulnerability scoring details

Base CVSS 4.0 score

6.9Medium
CVSS 4.0 vector shape for CVE-2026-27204Attack VectorAttack ComplexityAttack RequirementsPrivileges RequiredUser InteractionVS ConfidentialityVS IntegrityVS AvailabilitySS ConfidentialitySS IntegritySS Availability

Vector: CVSS:4.0/AV:N/AC:L/AT:P/PR:L/UI:P/VC:N/VI:N/VA:H/SC:N/SI:N/SA:H

Attack Vector
NetworkAdjacentLocalPhysical
Attack Complexity
LowHigh
Attack Requirements
NonePresent
Privileges Required
NoneLowHigh
User Interaction
NonePassiveActive
VS Confidentiality
HighLowNone
VS Integrity
HighLowNone
VS Availability
HighLowNone
SS Confidentiality
HighLowNone
SS Integrity
HighLowNone
SS Availability
HighLowNone
Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
bytecodealliancewasmtime< 24.0.6, >= 25.0.0, < 36.0.6, >= 37.0.0, < 40.0.4, >= 41.0.0, < 41.0.4Listed
Weakness

CWE details

CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.