PatchSiren

PatchSiren cyber security CVE debrief

CVE-2026-119134 bytecodealliance CVE debrief

This CVE debrief is based on the supplied source corpus. The CVE record was published on 2026-10-14T12:00:00.000Z and has not been modified since then. The vulnerability affects the Wasmtime package and is related to component-model handle tables being capped only per instance and charged to no limit. Defenders should prioritize verifying the affected versions of the Wasmtime package and assessing exposure in their environments. The source corpus provides limited information about the vulnerability, including a description of the issue and affected versions.

Vendor
bytecodealliance
Product
wasmtime
CVSS
MEDIUM 6.9
CISA KEV
Not listed in stored evidence
Original CVE published
2026-10-14
Original CVE updated
2026-10-30
Advisory published
2026-10-14
Advisory updated
2026-10-30

Who should care

Defenders responsible for maintaining and securing systems that use the Wasmtime package should assess exposure to this vulnerability. This includes operators, platform administrators, vulnerability management teams, and security teams who need to verify affected versions and assess exposure in their environments.

Why it matters

Defenders should prioritize verifying the affected versions of the Wasmtime package and assessing exposure in their environments to prevent potential issues.

  • Verify affected versions of Wasmtime in your environment
  • Assess exposure to potential denial-of-service (DoS) attacks
  • Consider upgrading to a fixed version of Wasmtime to prevent potential issues

Technical summary

The vulnerability affects the Wasmtime package and is related to component-model handle tables being capped only per instance and charged to no limit. This could potentially lead to denial-of-service (DoS) attacks if not properly mitigated. Defenders should prioritize verifying the affected versions of the Wasmtime package and assessing exposure in their environments to prevent potential issues. The source corpus provides limited information about the vulnerability, including a description of the issue and affected versions.

Defensive priority

Defenders should prioritize verifying the affected versions of the Wasmtime package and assessing exposure in their environments.

Recommended defensive actions

  • Verify the affected versions of the Wasmtime package in your environment
  • Assess exposure to the vulnerability
  • Consider upgrading to a fixed version of Wasmtime
  • Review compensating controls for exposed systems while remediation is scheduled and verified
  • Check relevant monitoring, detection, and logs for exposed assets that need extra review
  • Track exceptions, retest remediated assets, and close the item only after evidence is documented
  • Confirm whether affected product deployments exist in managed environments and assign an owner for follow-up

Evidence notes

The source corpus provides limited information about the vulnerability, including a description of the issue and affected versions. Defenders should verify the affected versions of the Wasmtime package and assess exposure in their environments to prevent potential issues. The CVE record was published on 2026-10-14T12:00:00.000Z and has not been modified since then. The vulnerability is related to component-model handle tables being capped only per instance and charged to no limit.

Sources and references

Verified primary and authoritative sources

  • CVE-2026-119134 CVE Program record

    Publisher, destination, and source semantics verified

    URL: https://www.cve.org/CVERecord?id=CVE-2026-119134

    CVE Program - Official CVE Program record with source-provided CVE metadata.

  • CVE-2026-119134 NVD vulnerability detail

    Publisher, destination, and source semantics verified

    URL: https://nvd.nist.gov/vuln/detail/CVE-2026-119134

    NIST National Vulnerability Database - Official NIST NVD detail page and source-specific vulnerability assessment.

Supplemental references

Methodology and review provenance

AI-assisted synthesis based on stored public vulnerability evidence. System validation, approval state, and publication status do not by themselves establish human review of this revision. PatchSiren helps prioritize defensive review and does not prove exposure or remediation on any system.