Wasmtime 46.0.0 before 48.0.7 and 49.0.0 before 49.0.4 fails to check forwarded trailers against the
Affects wasmtimeSource GCVE Database
Not known to be exploited · CVSS 6.3 Medium : upgrade to 49.0.4 or 48.0.7 when convenient.
Data as of 3 Nov 2026, 16:15 UTC
Thin evidence
One scorer or none| CNA (VulnCheck) | CVSS 4.0 | 6.3 |
|---|---|---|
| CNA (VulnCheck) | CVSS 3.1 | 3.7 |
- Patch
- Available – fixed in 49.0.4, 48.0.7
CVSS:4.0/AV:N/AC:H/AT:P/PR:N/UI:N/VC:N/VI:L/VA:N/SC:N/SI:N/SA:NExploitation evidence
Disclosed: evidence found.
CVE published 3 Nov 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponized: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors
A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 3 Nov 2026.
What to do
Upgrade bytecodealliance/wasmtime to 49.0.4 or 48.0.7.
Affected software
| Product | Affected | Fixed in |
|---|---|---|
crates.iobytecodealliance/wasmtimepkg:cargo/bytecodealliance/wasmtimeOther threats | Affected
| Fixed in
|
Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.
AI-suggested
A fix is available in Wasmtime versions 48.0.7 and 49.0.4 and later. Users should upgrade to these or newer versions to ensure that forwarded trailers are properly checked against the forbidden header hook. No additional mitigation steps are indicated.
Description
Wasmtime versions 46.0.0 before 48.0.7 and 49.0.0 before 49.0.4 contain a vulnerability where forwarded trailers in HTTP requests or responses are not properly checked against the WasiHttpHooks::is_forbidden_header hook in wasi-http p3. This allows WASIp3 guests to bypass embedder-customized forbidden header filtering, potentially undermining intended header restrictions.