<?xml version='1.0' encoding='UTF-8'?>
<?xml-stylesheet href="/static/style.xsl" type="text/xsl"?>
<feed xmlns="http://www.w3.org/2005/Atom" xml:lang="en">
  <id>https://cve.radiocsirt.org/rss/recent/all/10</id>
  <title>Most recent entries from all</title>
  <updated>2026-10-12T22:15:40.918101+00:00</updated>
  <author>
    <name>Vulnerability-Lookup</name>
    <email>csirt@opendfir.org</email>
  </author>
  <link href="https://cve.radiocsirt.org" rel="alternate"/>
  <generator uri="https://lkiesow.github.io/python-feedgen" version="1.0.0">python-feedgen</generator>
  <subtitle>Contains only the most 10 recent entries.</subtitle>
  <entry>
    <id>https://cve.radiocsirt.org/vuln/cve-2026-27572</id>
    <title>CVE-2026-27572 — Wasmtime can panic when adding excessive fields to a `wasi:http/types.fields` instance</title>
    <updated>2026-10-12T22:15:40.935765+00:00</updated>
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml"><p><strong>Affected:</strong> bytecodealliance wasmtime</p>
<p>Wasmtime is a runtime for WebAssembly. Prior to versions 24.0.6, 36.0.6, 4.0.04, 41.0.4, and 42.0.0, Wasmtime's implementation of the `wasi:http/types.fields` resource is susceptible to panics when too many fields are added to the set of headers. Wasmtime's implementation in the `wasmtime-wasi-http` crate is backed by a data structure which panics when it reaches excessive capacity and this condition was not handled gracefully in Wasmtime. Panicking in a WASI implementation is a Denial of Service vector for embedders and is treated as a security vulnerability in Wasmtime. Wasmtime 24.0.6, 36.0.6, 40.0.4, 41.0.4, and 42.0.0 patch this vulnerability and return a trap to the guest instead of panicking. There are no known workarounds at this time. Embedders are encouraged to update to a patched version of Wasmtime.</p></div>
    </content>
    <link href="https://cve.radiocsirt.org/vuln/cve-2026-27572"/>
  </entry>
  <entry>
    <id>https://cve.radiocsirt.org/vuln/ghsa-243v-98vx-264h</id>
    <title>GHSA-243v-98vx-264h — Wasmtime can panic when adding excessive fields to a `wasi:http/types.fields` instance</title>
    <updated>2026-10-12T22:15:40.935830+00:00</updated>
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml"><p><strong>Affected:</strong> crates.io: wasmtime</p>
<p>### Impact</p>
<p>Wasmtime's implementation of the `wasi:http/types.fields` resource is susceptible to panics when too many fields are added to the set of headers. Wasmtime's implementation in the `wasmtime-wasi-http` crate is backed by a data structure which panics when it reaches excessive capacity and this condition was not handled gracefully in Wasmtime. Panicking in a WASI implementation is a Denial of Service vector for embedders and is treated as a security vulnerability in Wasmtime.</p>
<p>### Patches</p>
<p>Wasmtime 24.0.6, 36.0.6, 40.0.4, 41.0.4, and 42.0.0 patch this vulnerability and return a trap to the guest instead of panicking.</p>
<p>### Workarounds</p>
<p>There are no known workarounds at this time, embedders are encouraged to update to a patched version of Wasmtime.</p>
<p>### Resources</p>
<p>* [Limitations of `http::HeaderMap`](https://docs.rs/http/1.4.0/http/header/#limitations)</p></div>
    </content>
    <link href="https://cve.radiocsirt.org/vuln/ghsa-243v-98vx-264h"/>
  </entry>
</feed>
