<?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-03T22:23:00.767252+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/euvd-2026-233874</id>
    <title>EUVD-2026-233874</title>
    <updated>2026-10-03T22:23:00.901469+00:00</updated>
    <content>EUVD-2026-233874</content>
    <link href="https://cve.radiocsirt.org/vuln/euvd-2026-233874"/>
  </entry>
  <entry>
    <id>https://cve.radiocsirt.org/vuln/fkie_cve-2022-31146</id>
    <title>fkie_cve-2022-31146</title>
    <updated>2026-10-03T22:23:00.901509+00:00</updated>
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml">
        <p>Wasmtime is a standalone runtime for WebAssembly. There is a bug in the Wasmtime's code generator, Cranelift, where functions using reference types may be incorrectly missing metadata required for runtime garbage collection. This means that if a GC happens at runtime then the GC pass will mistakenly think these functions do not have live references to GC'd values, reclaiming them and deallocating them. The function will then subsequently continue to use the values assuming they had not been GC'd, leading later to a use-after-free. This bug was introduced in the migration to the `regalloc2` register allocator that occurred in the Wasmtime 0.37.0 release on 2022-05-20. This bug has been patched and users should upgrade to Wasmtime version 0.38.2. Mitigations for this issue can be achieved by disabling the reference types proposal by passing `false` to `wasmtime::Config::wasm_reference_types` or downgrading to Wasmtime 0.36.0 or prior.</p>
      </div>
    </content>
    <link href="https://cve.radiocsirt.org/vuln/fkie_cve-2022-31146"/>
  </entry>
  <entry>
    <id>https://cve.radiocsirt.org/vuln/ghsa-5fhj-g3p3-pq9g</id>
    <title>GHSA-5fhj-g3p3-pq9g — Wasmtime vulnerable to Use After Free with `externref`s</title>
    <updated>2026-10-03T22:23:00.901549+00:00</updated>
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml"><p><strong>Affected:</strong> crates.io: wasmtime, crates.io: cranelift-codegen</p>
<p>There is a bug in Wasmtime's code generator, Cranelift, where functions using reference types may be incorrectly missing metadata required for runtime garbage collection (GC). This means that if a GC happens at runtime then the collector will mistakenly think some Wasm stack frames do not have live references to garbage collected values and therefore reclaim and deallocate them. The function can then subsequently continue to use the values, leading later to use-after-free bugs. This bug was introduced in Cranelift's migration to the `regalloc2` register allocator in the Wasmtime 0.37.0 release on 2022-05-20. This bug has been patched and users should upgrade to Wasmtime version 0.38.2.</p>
<p>Mitigations for this issue can be achieved by doing one of:</p>
<p>* Disabling the reference types proposal by passing `false` to [`wasmtime::Config::wasm_reference_types`](https://docs.rs/wasmtime/0.38.0/wasmtime/struct.Config.html#method.wasm_reference_types).
* Downgrading to Wasmtime 0.36.0 or prior.</p></div>
    </content>
    <link href="https://cve.radiocsirt.org/vuln/ghsa-5fhj-g3p3-pq9g"/>
  </entry>
  <entry>
    <id>https://cve.radiocsirt.org/vuln/gsd-2022-31146</id>
    <title>gsd-2022-31146</title>
    <updated>2026-10-03T22:23:00.901586+00:00</updated>
    <content>gsd-2022-31146</content>
    <link href="https://cve.radiocsirt.org/vuln/gsd-2022-31146"/>
  </entry>
  <entry>
    <id>https://cve.radiocsirt.org/vuln/msrc_cve-2022-31146</id>
    <title>msrc_CVE-2022-31146 — Use after free in Wasmtime</title>
    <updated>2026-10-03T22:23:00.901600+00:00</updated>
    <content>msrc_CVE-2022-31146</content>
    <link href="https://cve.radiocsirt.org/vuln/msrc_cve-2022-31146"/>
  </entry>
  <entry>
    <id>https://cve.radiocsirt.org/vuln/rustsec-2022-0100</id>
    <title>RUSTSEC-2022-0100 — Use After Free with `externref`s in Wasmtime</title>
    <updated>2026-10-03T22:23:00.901618+00:00</updated>
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml"><p><strong>Affected:</strong> crates.io: wasmtime</p>
<p>This is an entry in the RustSec database for the Wasmtime security advisory
located at
https://github.com/bytecodealliance/wasmtime/security/advisories/GHSA-5fhj-g3p3-pq9g.
For more information see the GitHub-hosted security advisory.</p></div>
    </content>
    <link href="https://cve.radiocsirt.org/vuln/rustsec-2022-0100"/>
  </entry>
  <entry>
    <id>https://cve.radiocsirt.org/vuln/ubuntu-cve-2022-31146</id>
    <title>UBUNTU-CVE-2022-31146</title>
    <updated>2026-10-03T22:23:00.901638+00:00</updated>
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml"><p><strong>Affected:</strong> Ubuntu:18.04:LTS: mozjs52, Ubuntu:18.04:LTS: mozjs38, Ubuntu:20.04:LTS: mozjs68, Ubuntu:20.04:LTS: mozjs52, Ubuntu:22.04:LTS: mozjs78, Ubuntu:22.04:LTS: mozjs91, Ubuntu:22.04:LTS: thunderbird, Ubuntu:24.04:LTS: thunderbird</p>
<p>Wasmtime is a standalone runtime for WebAssembly. There is a bug in the Wasmtime's code generator, Cranelift, where functions using reference types may be incorrectly missing metadata required for runtime garbage collection. This means that if a GC happens at runtime then the GC pass will mistakenly think these functions do not have live references to GC'd values, reclaiming them and deallocating them. The function will then subsequently continue to use the values assuming they had not been GC'd, leading later to a use-after-free. This bug was introduced in the migration to the `regalloc2` register allocator that occurred in the Wasmtime 0.37.0 release on 2022-05-20. This bug has been patched and users should upgrade to Wasmtime version 0.38.2. Mitigations for this issue can be achieved by disabling the reference types proposal by passing `false` to `wasmtime::Config::wasm_reference_types` or downgrading to Wasmtime 0.36.0 or prior.</p></div>
    </content>
    <link href="https://cve.radiocsirt.org/vuln/ubuntu-cve-2022-31146"/>
  </entry>
</feed>
