How many CVEs have patched FieldMap?

2 published CVEs changed FieldMap in bytecodealliance/wasmtime, in 2 distinct patches totalling 252 changed lines, between 2026 and 2026.

What is the latest CVE that changed FieldMap?

CVE-2026-27572 (Wasmtime can panic when adding excessive fields to a `wasi:http/types.fields` instance), published 2026-02-24, changed lines 702 to 825 of crates/wasi-http/src/types.rs.

How does FieldMap compare to the rest of bytecodealliance/wasmtime?

bytecodealliance/wasmtime has 27 CVEs with a located fix in total; 2 of them changed FieldMap.

What do the line numbers refer to?

Line numbers are in the fixed version of the file, as the upstream patch left it. A CVE whose fix was backported to several branches is listed once, with the lines from the upstream commit.

RadicalNotion.AI

Log in Create an account

bytecodealliance/wasmtime

Type

FieldMap

Name: FieldMap in bytecodealliance/wasmtime: CVE fixes
Creator: RadicalNotion.AI
License: https://creativecommons.org/licenses/by-nc/4.0/

crates/wasi-http/src/types.rs

Last patched February 24, 2026

2

CVEs

That changed this function

2

Distinct patches

Backports counted once

252

Lines changed

Added plus removed

2026

Years

By CVE publication date

Overview

FieldMap in bytecodealliance/wasmtime was changed by 2 published CVE fixes in 2026, in 2 distinct patches that added or removed 252 lines in total.

bytecodealliance/wasmtime has 27 CVEs with a located fix in total, so 7% of them touched this function.

CVEs that patched it

Every published CVE whose fix changed FieldMap, newest first, with the lines each fix touched.

Wasmtime can panic when adding excessive fields to a `wasi:http/types.fields` instance
CVE-2026-27572 · lines 702–825 · +124 −2
Medium · CVSS 6.9
EPSS 0.7%2026-02-24
Wasmtime is vulnerable to panic when dropping a `[Typed]Func::call_async` future
CVE-2026-27195 · lines 702–825 · +124 −2
Medium · CVSS 6.9
EPSS 0.6%2026-02-24

Get an alert when the next CVE fix lands in bytecodealliance/wasmtime, with the patched functions.

Monitor wasmtime CVEs

Other functions in these files

Functions in the same file that CVE fixes also changed.

1newcrates/wasi-http/src/types.rs2 CVEs · 2 patches2026

Other hotspots in the repository

Functions in bytecodealliance/wasmtime changed by the most CVE fixes.

and_then2 CVEs · crates/wasmtime/src/runtime/component/values.rs hostcall_fuel2 CVEs · crates/wasmtime/src/runtime/component/store.rs Done2 CVEs · crates/wasi-http/src/types_impl.rs Err2 CVEs · crates/wasi-http/src/body.rs Some2 CVEs · crates/wasi-http/src/body.rs as_ref2 CVEs · crates/wasi-http/src/types_impl.rs

All patched functions in bytecodealliance/wasmtime

Frequently asked questions

Common questions about CVE fixes to FieldMap.

How many CVEs have patched FieldMap?: 2 published CVEs changed FieldMap in bytecodealliance/wasmtime, in 2 distinct patches totalling 252 changed lines, between 2026 and 2026.
What is the latest CVE that changed FieldMap?: CVE-2026-27572 (Wasmtime can panic when adding excessive fields to a `wasi:http/types.fields` instance), published 2026-02-24, changed lines 702 to 825 of crates/wasi-http/src/types.rs.
How does FieldMap compare to the rest of bytecodealliance/wasmtime?: bytecodealliance/wasmtime has 27 CVEs with a located fix in total; 2 of them changed FieldMap.
What do the line numbers refer to?: Line numbers are in the fixed version of the file, as the upstream patch left it. A CVE whose fix was backported to several branches is listed once, with the lines from the upstream commit.

References

Fix locations are computed by RadicalNotion.AI from the upstream patch diff of each CVE. CVE data is sourced from the CVE Program.

Track bytecodealliance/wasmtime CVEs

Get an alert when a new CVE lands in this repository, with the patched functions and AI-written remediation guidance.

Create an account See pricing