CVE-2025-53901Network attack vector

Host crash via corrupted file descriptor state

Published Jul 18, 2025 · Updated Jul 18, 2025

Denial of service in Wasmtime before 24.0.4, 33.0.0 through 33.0.1, and 34.0.0 through 34.0.1 allows guest OS users to crash the host. The WASIp1 fd_renumber implementation corrupts descriptor-table state when source and destination are equal or the destination reuses a closed descriptor, so the next path_open panics. Exploitation requires a crafted WASIp1 guest and a preopened directory that permits another descriptor; WASIp2 components are unaffected, and the panic does not escape the sandbox or corrupt memory.

CVSS severity3.5
Low
EPSS probability0.32%
Next 30 days · Sep 16, 2026
Known exploitationUnconfirmed
Based on sourced intelligence
Hinoki checkNot available
Coverage for this vulnerability

See if you're affected

Explore vulnerability checks for your environment with Hinoki.

Book a demo

Summary

What happened

Denial of service in Wasmtime before 24.0.4, 33.0.0 through 33.0.1, and 34.0.0 through 34.0.1 allows guest OS users to crash the host. The WASIp1 fd_renumber implementation corrupts descriptor-table state when source and destination are equal or the destination reuses a closed descriptor, so the next path_open panics. Exploitation requires a crafted WASIp1 guest and a preopened directory that permits another descriptor; WASIp2 components are unaffected, and the panic does not escape the sandbox or corrupt memory.

The record

CVE
CVE-2025-53901
Published
Jul 18, 2025
Updated
Jul 18, 2025
Vendor
Bytecode Alliance
Product
Wasmtime
Classifications
CWE-672, T1499.004
Attack vector
network
Privileges
authenticated

Timeline

How it unfolded

  1. Jul 18, 2025CVE publishedPublication date reported by the CVE source.
  2. Jul 18, 2025Record updatedLatest update available in the CVE record.

Exploitability

Present is not the same as exploitable

Compare your product and version with the public record. A matching version still requires validation against your environment.

Is a vulnerable build present?

Compare these published version ranges with your installed build and any vendor patches.

  1. Affected versionversion=< 24.0.4
  2. Affected versionversion=>= 33.0.0, < 33.0.2
  3. Affected versionversion=>= 34.0.0, < 34.0.2

What conditions does exploitation require?

Attack vectornetwork
Required privilegesauthenticated

What is affected?

Bytecode Alliance · Wasmtimeversion=< 24.0.4; version=>= 33.0.0, < 33.0.2; version=>= 34.0.0, < 34.0.2

Published CVSS scores

3.5GitHubCVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:U/C:N/I:N/A:L

CVSS describes severity. EPSS estimates exploitation probability.

Attacks

What attackers are doing with it

Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.

Daily unique IPsNo honeypot observations are available for this CVE in the selected window.

No observations available

Sep 10, 2026Sep 16, 2026
Latest reporting daySep 16, 2026
Latest daily unique IPsUnavailable
Prior 30-day averageUnavailable
SourceShadowserver honeypots (KEV)
Vectornetwork
Privilegesauthenticated
Known exploitationUnconfirmed
Public exploitUnconfirmed

Weakness, pattern, technique

CWE-672Operation on a Resource after Expiration or Release
T1499.004Application or System Exploitation

Public exploit references

No public exploit references are available in this record.

Labels summarize the accepted research assessment. They do not indicate a test against your environment.

Technologies

Your stack

See the directory against your own environment.

Your stack

Check the software in your environment

Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.

Book a demo