CVE-2026-115385: Wasmtime 46.0.0 before 48.0.4 and 49.0.0 before 49.0.2 Host Panic via WASIp3 Timestamps

Published Oct 22, 2026
·
Updated

Wasmtime 46.0.0 before 48.0.4 and 49.0.0 before 49.0.2 contains a denial of service vulnerability in the wasmtime-wasi WASIp3 implementation that allows guests to abort the Unix host process. Guests with mutable preopened directory access can call set-times or set-times-at with negative seconds timestamps before the epoch, triggering an assertion failure that crashes the host.

Affected Software

5 affected componentsFixes available
Bytecode Alliance Wasmtime>=46.0.0<48.0.4, >=49.0.0<49.0.2
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 exposed to this denial of service?

Unix hosts running affected Wasmtime versions are exposed when they use the wasmtime-wasi WASIp3 implementation and provide a guest with mutable access to a preopened directory.

2

What does an attacker need to trigger the crash?

An attacker needs the ability to execute or control a WASI guest that has mutable preopened-directory access. The guest can invoke set-times or set-times-at with a negative timestamp expressed as seconds before the Unix epoch.

3

Is a default Wasmtime configuration known to be affected?

The available information does not establish whether default configuration is affected. Exploitation specifically requires mutable preopened directory access for the guest.

4

What is the impact of successful exploitation?

Successful exploitation triggers an assertion failure in the WASIp3 implementation and aborts the Unix host process, causing denial of service. No confidentiality or integrity impact is identified in the supplied severity vector.

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