NetSight

Security Dashboard

A live picture of new vulnerabilities, flaws exploited in the wild and malicious packages.

Reset
72 matching advisories · page 2 of 3Index updated 2 minutes ago · Subscribe · RSS
SeverityIDTitleAffectedAge
high7.5 CVE-2026-34943 Wasmtime has a possible panic when lifting `flags` component value rust · wasmtime 2026-04-09 medium6.5 CVE-2026-34942 Wasmtime: Panic when transcoding misaligned utf-16 strings rust · wasmtime 2026-04-09 high8.1 CVE-2026-34941 Wasmtime: Heap OOB read in component model UTF-16 to latin1+utf16 string transcoding rust · wasmtime 2026-04-09 high7.5 CVE-2026-27572 Wasmtime can panic when adding excessive fields to a `wasi:http/types.fields` instance rust · wasmtime 2026-02-24 medium5.9 CVE-2026-27204 Wasmtime WASI implementations are vulnerable to guest-controlled resource exhaustion rust · wasmtime 2026-02-24 high7.5 CVE-2026-27195 Wasmtime is vulnerable to panic when dropping a `[Typed]Func::call_async` future rust · wasmtime 2026-02-24 medium4.1 CVE-2026-24116 Wasmtime segfault or unused out-of-sandbox load with f64.copysign operator on x86-64 rust · wasmtime 2026-01-27 medium5.1 CVE-2025-64713 WebAssembly Micro Runtime (WAMR) is a lightweight standalone WebAssembly (Wasm) runtime. bytecodealliance · webassembly_micro_runtime 2025-11-25 medium4.7 CVE-2025-64704 WebAssembly Micro Runtime (WAMR) is a lightweight standalone WebAssembly (Wasm) runtime. bytecodealliance · webassembly_micro_runtime 2025-11-25 low2.1 CVE-2025-62711 Wasmtime vulnerable to segfault when using component resources rust · wasmtime 2025-10-24 low3.3 CVE-2025-61670 Wasmtime: Memory leak in C API with `externref` and `anyref` types rust · wasmtime-c-api-impl, pip · wasmtime-bin 2025-10-07 medium5.3 CVE-2025-58749 WebAssembly Micro Runtime (WAMR) is a lightweight standalone WebAssembly (Wasm) runtime. bytecodealliance · webassembly_micro_runtime 2025-09-16 medium5.3 CVE-2025-54126 The WebAssembly Micro Runtime's (WAMR) iwasm package is the executable binary built with WAMR VMcore which supports WebAssembly System Interface (WASI) and com… bytecodealliance · webassembly_micro_runtime 2025-07-29 low3.5 CVE-2025-53901 Wasmtime CLI is vulnerable to host panic through its fd_renumber function rust · wasmtime-wasi, rust · wasmtime 2025-07-18 medium5.5 CVE-2025-43853 The WebAssembly Micro Runtime's (WAMR) iwasm package is the executable binary built with WAMR VMcore which supports WebAssembly System Interface (WASI) and com… bytecodealliance · webassembly_micro_runtime 2025-05-15 high7.5 CVE-2024-27532 wasm-micro-runtime (aka WebAssembly Micro Runtime or WAMR) 06df58f is vulnerable to NULL Pointer Dereference in function `block_type_get_result_types. bytecodealliance · webassembly_micro_runtime 2024-11-08 high7.8 CVE-2024-25431 An issue in bytecodealliance wasm-micro-runtime before v.b3f728c and fixed in commit 06df58f allows a remote attacker to escalate privileges via a crafted file… bytecodealliance · webassembly_micro_runtime 2024-11-08 critical10.0 CVE-2024-51745 Wasmtime doesn't fully sandbox all the Windows device filenames rust · wasmtime 2024-11-05 low2.9 CVE-2024-47813 Wasmtime race condition could lead to WebAssembly control-flow integrity and type safety violations rust · wasmtime 2024-10-09 medium5.5 CVE-2024-47763 wasmtime has a runtime crash when combining tail calls with trapping imports rust · wasmtime 2024-10-09 high7.5 CVE-2024-34251 An out-of-bound memory read vulnerability was discovered in Bytecode Alliance wasm-micro-runtime v2.0.0 which allows a remote attacker to cause a denial of ser… bytecodealliance · webassembly_micro_runtime 2024-05-06 medium6.2 CVE-2024-34250 A heap buffer overflow vulnerability was discovered in Bytecode Alliance wasm-micro-runtime v2.0.0 which allows a remote attacker to cause at least a denial of… bytecodealliance · webassembly_micro_runtime 2024-05-06 low3.3 CVE-2024-30266 Wasmtime vulnerable to panic when using a dropped extenref-typed element segment rust · wasmtime 2024-04-02 medium5.5 CVE-2023-52284 Bytecode Alliance wasm-micro-runtime (aka WebAssembly Micro Runtime or WAMR) before 1.3.0 can have an "double free or corruption" error for a valid WebAssembly… bytecodealliance · webassembly_micro_runtime 2023-12-31 high7.5 CVE-2023-48105 An heap overflow vulnerability was discovered in Bytecode alliance wasm-micro-runtime v.1.2.3 allows a remote attacker to cause a denial of service via the was… bytecodealliance · webassembly_micro_runtime 2023-11-22 low2.2 CVE-2023-41880 Miscompilation of wasm `i64x2.shr_s` instruction with constant input on x86_64 rust · wasmtime 2023-09-14 low3.9 CVE-2023-30624 Wasmtime is a standalone runtime for WebAssembly. rust · wasmtime 2023-04-27 low3.1 CVE-2023-27477 wasmtime vulnerable to miscompilation of `i8x16.select` with the same inputs on x86_64 rust · wasmtime, rust · cranelift-codegen 2023-03-08 critical9.9 CVE-2023-26489 wasmtime vulnerable to guest-controlled out-of-bounds read/write on x86_64 rust · wasmtime, rust · cranelift-codegen 2023-03-08 low3.8 CVE-2022-39394 wasmtime_trap_code C API function has out of bounds write vulnerability rust · wasmtime 2022-11-10

Get notifications

Subscribe to new vulnerabilities and early warnings from the last seven days. Pick what matters to your stack and copy the address into any feed reader. More filters appear when you pick a type.

Format:
Open feed

Early warnings are advisories that are published before or without a CVE number, for example malicious packages, advisories with a CVE still pending and reports that are not reviewed yet. Confidence says how well an entry is checked: high, medium or low.

About this dashboard

The dashboard keeps its own index of security advisories and refreshes it every 30 minutes. It merges the national vulnerability database, package advisories, malware reports and the catalog of vulnerabilities that are exploited in the wild into one record per issue. Reports about the same flaw are combined, so nothing is listed twice.

Open any entry for the full record: description, severity vector, affected packages and versions, fixed versions, weakness class, exploitation probability and references.

Sources: the GitHub Advisory Database (reviewed advisories, malware reports and unreviewed reports), the National Vulnerability Database, the CVE Program (cve.org) for brand-new records, the OpenSSF malicious packages list, the CISA catalog of Known Exploited Vulnerabilities and Microsoft's blocklist of malicious VS Code extensions. Every entry names its sources on its detail page.

This product uses the NVD API but is not endorsed or certified by the NVD.

Reading the figures

  • Threat level: a rating computed from three numbers shown next to it: critical advisories in the last 24 hours, vulnerabilities newly confirmed as exploited this week and malware reports this week. It is a quick orientation, not an official warning level.
  • Severity: scores from 9.0 are critical, 7.0 to 8.9 high, 4.0 to 6.9 medium and 0.1 to 3.9 low. Severity describes how bad a flaw is in general. It does not know whether the component is reachable in your environment.
  • Known exploited: exploitation has been observed in real attacks. These are the entries to patch first. Entries with a fix deadline show how many days are left.
  • Early warnings: advisories that appear before or without a CVE number, for example malicious packages, reviewed advisories with a CVE still pending and reports that are not reviewed yet.
  • Priority queue: critical and high advisories of the last 7 days and everything newly exploited, ordered by exploitation status, severity and score.

Questions

Where does the data come from?
From public vulnerability databases, package advisories and the catalog of exploited vulnerabilities. NetSight collects them into its own index every 30 minutes and merges duplicates.
How do I check whether I am affected?
Search for your product or package name, open the record and compare your installed version with the affected and fixed versions. A product name alone does not mean your version is affected.
What does known exploited mean?
Exploitation of this vulnerability has been observed in real attacks. Such entries carry a date they were confirmed and, where one exists, a deadline for applying the fix.
What is an early warning?
An advisory that is published before or without a CVE number, such as a malicious package or a reviewed advisory whose CVE is still pending. They give you a head start, but the details can change.
Is a high severity always more urgent than a low one?
No. Severity measures technical impact in general. Exposure of the affected system, observed exploitation and the exploitation probability matter as much.
Can I follow new advisories automatically?
Yes. Use the notification builder further down to create an RSS, Atom or JSON feed filtered by severity, technology, ecosystem or exploitation status.