How many CVEs have patched read_string?

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

What is the latest CVE that changed read_string?

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

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

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

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

Function

read_string

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

crates/wasi/src/p1.rs

Last patched February 24, 2026

2

CVEs

That changed this function

2

Distinct patches

Backports counted once

80

Lines changed

Added plus removed

2026

Years

By CVE publication date

Overview

read_string in bytecodealliance/wasmtime was changed by 2 published CVE fixes in 2026, in 2 distinct patches that added or removed 80 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 read_string, 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 1182–1189 · +4 −36
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 1200–1207 · +4 −36
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.

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 read_string.

How many CVEs have patched read_string?: 2 published CVEs changed read_string in bytecodealliance/wasmtime, in 2 distinct patches totalling 80 changed lines, between 2026 and 2026.
What is the latest CVE that changed read_string?: CVE-2026-27572 (Wasmtime can panic when adding excessive fields to a `wasi:http/types.fields` instance), published 2026-02-24, changed lines 1182 to 1189 of crates/wasi/src/p1.rs.
How does read_string compare to the rest of bytecodealliance/wasmtime?: bytecodealliance/wasmtime has 27 CVEs with a located fix in total; 2 of them changed read_string.
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