CVE-2026-115390: Wasmtime 47.0.0 before 48.0.3 and 49.0.0 before 49.0.1 Fuel Accounting Bypass DoS

Published Oct 22, 2026
·
Updated

Wasmtime 47.0.0 before 48.0.3 and 49.0.0 before 49.0.1 contains a fuel accounting flaw in Cranelift-compiled callref and trytable catch paths. Malicious guests can reset consumed fuel after calls to run exponentially long on linear fuel, evading timeouts and periodic yields for denial of service.

Affected Software

5 affected componentsFixes available
Bytecode Alliance Wasmtime>=47.0.0<48.0.3, >=49.0.0<49.0.1
ubuntu/rust-wasmtime*
ubuntu/rust-wasmtime*
ubuntu/rust-wasmtime*
debian/rust-wasmtime
26.0.1+dfsg-336.0.13+dfsg-1

Remediation

Recommended actions to resolve this vulnerability, in priority order.

  1. Upgrade

    Upgrade debian/rust-wasmtime to a version that resolves this vulnerability.

    Fixed in 26.0.1+dfsg-3Fixed in 36.0.13+dfsg-1

Event History

Oct 22, 2026
CVE Published
via Ubuntu·12:00 AM
Data Sourced
via Ubuntu·12:00 AM
RemedyDescriptionSeverityAffected Software
CVE Published
via MITRE·07:13 PM
Data Sourced
via MITRE·07:13 PM
DescriptionSeverityWeakness
Data Sourced
via OSV·07:17 PM
DescriptionSeverityAffected Software
Data Sourced
via NVD·07:17 PM
DescriptionSeverityWeakness

Frequently Asked Questions

1

Which deployments are most exposed to this issue?

Deployments that execute malicious or otherwise untrusted Wasmtime guests are most exposed. A malicious guest can use the affected Cranelift-compiled call_ref and try_table catch paths to bypass intended fuel-based execution limits.

2

What does an attacker need to do to trigger the denial of service?

The attacker needs the ability to run a malicious guest in the affected Wasmtime environment. The guest must exercise the affected call_ref or try_table catch paths to reset consumed fuel after calls.

3

Which releases should be used to remediate the issue?

Upgrade affected 47.0.0 releases to 48.0.3 or later, or upgrade affected 49.0.0 releases to 49.0.1 or later. Versions before those fixed releases in the stated branches are affected.

4

How can teams identify potentially vulnerable instances?

Inventory Wasmtime versions and identify instances running 47.0.0 before 48.0.3 or 49.0.0 before 49.0.1. Prioritize instances that execute untrusted guests or rely on fuel limits, timeouts, or periodic yields to constrain guest execution.

Contact

SecAlerts Pty Ltd.
132 Wickham Terrace
Fortitude Valley,
QLD 4006, Australia
info@secalerts.co
By using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.
© 2026 SecAlerts Pty Ltd.
ABN: 70 645 966 203, ACN: 645 966 203