OSV-2026-150 Null-dereference READ in wasm_runtime_invoke_native
Not scored
Published
Check this codebase for OSV-2026-150 and fix it if it is affected.
What it is: OSV-2026-150 is a vulnerability in wamr, published on 27 Jan 2026.
Exploitation: There is no known exploitation of OSV-2026-150 in the wild and no public exploit code.
Affected packages and fixed versions:
- wamr (OSS-Fuzz): affected all versions; no fix listed
Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.
Reference: https://insights.sbomify.com/OSV-2026-150/ (Markdown: https://insights.sbomify.com/OSV-2026-150/index.md)
A null pointer dereference in the WebAssembly runtime can cause a crash, leading to denial of service for applications using the library.
- Exploited in the wild
- Not known
- Login needed
- Not needed
- Attackable
- Not stated
- Victim action needed
- Not needed
- Fix
- None listed
What is OSV-2026-150?
OSV-2026-150 is a vulnerability in wamr, published on 27 Jan 2026.
Official description
OSS-Fuzz report: https://bugs.chromium.org/p/oss-fuzz/issues/detail?id=478557340
Crash type: Null-dereference READ
Crash state:
wasm_runtime_invoke_native
wasm_interp_call_wasm
wasm_call_function
Which versions are affected by OSV-2026-150?
1 open source package ship an affected version, including wamr.
| Package | Affected | Fixed in |
|---|---|---|
wamr OSS-Fuzz | All versions | None |
How do I fix OSV-2026-150?
No fix has been published for OSV-2026-150 yet. Limit exposure of the affected software until one is available.
Is OSV-2026-150 being exploited?
There is no known exploitation of OSV-2026-150 in the wild and no public exploit code.