OSV-2026-603
UNKNOWN READ in <wasmtime::runtime::func::Func>::call_unchecked_raw::<
No scoreFix available
OSS-Fuzz report: https://bugs.chromium.org/p/oss-fuzz/issues/detail?id=504268343
Crash type: UNKNOWN READ
Crash state:
<wasmtime::runtime::func::Func>::call_unchecked_raw::<
<wasmtime::runtime::func::Func>::call_impl_do_call::<
wasmtime_internal_fiber::stackswitch::x86_64::wasmtime_fiber_start
What each source reports
OSV No score
UNKNOWN READ in <wasmtime::runtime::func::Func>::call_unchecked_raw::<
OSS-Fuzz report: https://bugs.chromium.org/p/oss-fuzz/issues/detail?id=504268343
Crash type: UNKNOWN READ
Crash state:
<wasmtime::runtime::func::Func>::call_unchecked_raw::<
<wasmtime::runtime::func::Func>::call_impl_do_call::<
wasmtime_internal_fiber::stackswitch::x86_64::wasmtime_fiber_start
- Record
OSV-2026-603- Updated
- 2026-11-02
Affected packages
| Package | Affected | Fixed |
|---|---|---|
wasmtimeOSS-Fuzz |
Commit ranges | Not evaluated |
Not evaluated means the source gave git commits or a range we can't read, so we can't tell which releases are affected. A fixed version beside it is the source’s own claim.
History
| Recorded | Changed | Sources |
|---|---|---|
| first indexed | OSV |
Dates are when Every CVE recorded each change. Upstream dates may differ.
In short
OSV-2026-603 is a vulnerability with no CVSS score yet in wasmtime, published April 21, 2026. No source lists public exploit code. A source reports a fix.