CVE-2024-47813

Host type-safety violation via double unregistration

Published Oct 9, 2024 · Updated Oct 9, 2024

Race condition in Bytecode Alliance Wasmtime 19.0.0 and affected later releases allows local users to corrupt type safety via host API calls. The Engine type registry decrements a registration count before locking, allowing another thread to unregister the same reused slot and make a later indirect-call type check accept a mismatched function. Triggering requires host code to create and drop multiple types concurrently on one Engine; WebAssembly guests cannot trigger it, and the demonstrated result is panic or invalid registry state.

CVSS severity2.9
Low
EPSS probability0.15%
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

Race condition in Bytecode Alliance Wasmtime 19.0.0 and affected later releases allows local users to corrupt type safety via host API calls. The Engine type registry decrements a registration count before locking, allowing another thread to unregister the same reused slot and make a later indirect-call type check accept a mismatched function. Triggering requires host code to create and drop multiple types concurrently on one Engine; WebAssembly guests cannot trigger it, and the demonstrated result is panic or invalid registry state.

The record

CVE
CVE-2024-47813
Published
Oct 9, 2024
Updated
Oct 9, 2024
Vendor
Bytecode Alliance
Product
Wasmtime
Classifications
CWE-367
Attack vector
local
Privileges
admin

Timeline

How it unfolded

  1. Oct 9, 2024CVE publishedPublication date reported by the CVE source.
  2. Oct 9, 2024Record 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=>= 19.0.0, < 21.0.2
  2. Affected versionversion=>= 22.0.0, < 22.0.1
  3. Affected versionversion=>= 23.0.0, < 23.0.3
  4. Affected versionversion=>= 24.0.0, < 24.0.1
  5. Affected versionversion=>= 25.0.0, < 25.0.2

What conditions does exploitation require?

Attack vectorlocal
Required privilegesadmin

What is affected?

Bytecode Alliance · Wasmtimeversion=>= 19.0.0, < 21.0.2; version=>= 22.0.0, < 22.0.1; version=>= 23.0.0, < 23.0.3; version=>= 24.0.0, < 24.0.1; version=>= 25.0.0, < 25.0.2

Published CVSS scores

2.9GitHubCVSS:3.1/AV:L/AC:H/PR:H/UI:R/S:U/C:N/I:L/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 9, 2026Sep 15, 2026
Latest reporting daySep 15, 2026
Latest daily unique IPsUnavailable
Prior 30-day averageUnavailable
SourceShadowserver honeypots (KEV)
Vectorlocal
Privilegesadmin
Known exploitationUnconfirmed
Public exploitUnconfirmed

Weakness, pattern, technique

CWE-367Time-of-check Time-of-use (TOCTOU) Race Condition

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