Vulnerability · CVE-2026-119136
Wasmtime may not properly enforce async-entrypoint requirement
Published Oct 14, 2026 · catalog updated Oct 30, 2026 · Wasmtime may not properly
Last checked Nov 5, 2026. A connected source was read within the last 7 days.
Check if you run it
No confirmed exploitation is on record for CVE-2026-119136. EPSS is 0.21%. Act only if a listed version of Wasmtime may not properly is installed.
Gaps on this record
- The stored product name is a package slug. The name on this page is taken from the title (Wasmtime may not properly).
- No vendor fix or required action is stored. Compare the linked advisory before you change production.
- Severity
- Unknown—
- Known exploitation
- Not in CISA/VulnCheck KEV
- EPSS
- 0.21%
- Remediation
- Advisory link
- Affected products
- crates.io wasmtime
This is an entry in the RustSec database for the Wasmtime security advisory located at https://github.com/bytecodealliance/wasmtime/security/advisories/GHSA-vcg5-q8m5-8379 For more information see the GitHub-hosted security advisory.
Are you affected?
Enter the version you run. The result uses only the ranges stored on this record.
The check returns affected, not affected, or incomplete. It does not guess a version that is missing from the record.
- crates.io wasmtime42.0.0 → 48.0.6
How to fix CVE-2026-119136
Upgrade
CVE-2026-119136 lists a fix boundary at 48.0.6. Compare the installed build with that boundary before you change production.
Version check
Seen in 42.0.0 → 48.0.6
Advisory
Open the cve_org record and follow its fix.
Official advisories
What to do
Three questions, each answered from this record only. Confirm the vendor advisory before you patch.
Should you patch?
No confirmed exploitation is on record for CVE-2026-119136. EPSS is 0.21%. Act only if a listed version of Wasmtime may not properly is installed.
Which versions are affected?
Compare what you have installed with 42.0.0 → 48.0.6. Compare the installed version with the linked vendor advisory before you change production.
What should an analyst verify?
No weakness class is stored. EPSS 0.21%. There is no CISA KEV listing. No Exploit-DB or Metasploit reference is linked. Use the source links for the original advisory.
Code
The project this record applies to. Exploit listings stay in References.
Timeline
Detection, updates, and resolution for this record.
Oct 14, 2026 · GitHub Advisory Database
Detected
This is an entry in the RustSec database for the Wasmtime security advisory located at https://github.com/bytecodealliance/wasmtime/security/advisories/GHSA-vcg5-q8m5-8379 For more information see the GitHub-hosted security advisory.
Oct 30, 2026 · GitHub Advisory Database
Fix available
wasmtime fixed in 48.0.6
Oct 30, 2026 · GitHub Advisory Database
Fix available
wasmtime fixed in 48.0.6
Oct 30, 2026 · GitHub Advisory Database
Updated
This is an entry in the RustSec database for the Wasmtime security advisory located at https://github.com/bytecodealliance/wasmtime/security/advisories/GHSA-vcg5-q8m5-8379 For more information see the GitHub-hosted security advisory.
Sources
- CVE.orgVulnerability recordCVE-2026-119136
Official CVE identifier
cve.org - FIRST EPSSExploitation probabilityCVE-2026-119136
30-day exploitation probability 0.21%
first.org - GitHub Advisory DatabasePackage advisoryGHSA-vcg5-q8m5-8379
GitHub Advisory Database record mirrored by OSV.
github.com - OpenSSF OSV / OSV ScannerPackage advisoryRUSTSEC-2026-0362
Wasmtime may not properly enforce async-entrypoint requirement
osv.dev
References
Freshness
Last verified in this catalog Nov 5, 2026. Significant claims (KEV, EPSS, CVSS, affected ranges) come from the source rows above — open the original publisher for the authoritative advisory.
- FIRST EPSSNov 5, 2026
- CVE.orgOct 30, 2026
- GitHub Advisory DatabaseOct 30, 2026
- OpenSSF OSV / OSV ScannerOct 30, 2026