NetSight

Security Dashboard

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

Reset
39 matching advisories · page 1 of 2Index updated just now · Subscribe · RSS
SeverityIDTitleAffectedAge
medium6.3 CVE-2026-126406 The wasmtime-wasi-http p2 implementation in Wasmtime before 36.0.20, 37.0.0 before 48.0.8, 49.0.0 before 49.0.5, and 50.0.0 before 50.0.1 can send conflicting … bytecodealliance · wasmtime 8 days ago medium4.8 CVE-2026-126407 Wasmtime before 36.0.20, 37.0.0 before 48.0.8, 49.0.0 before 49.0.5, and 50.0.0 before 50.0.1 allocates untracked host memory when a component receives a borro… bytecodealliance · wasmtime 8 days ago medium5.3 CVE-2026-126410 Wasmtime's wasmtime-wasi crate 48.0.0 before 48.0.8, 49.0.0 before 49.0.5, and 50.0.0 before 50.0.1 contains a time-of-check/time-of-use race in the wasip3 was… bytecodealliance · wasmtime 8 days ago medium6.9 CVE-2026-54913 WebAssembly Micro Runtime (WAMR) is a lightweight standalone WebAssembly (Wasm) runtime. bytecodealliance · wasm-micro-runtime 16 days ago medium6.3 CVE-2026-121440 Wasmtime 46.0.0 before 48.0.7 and 49.0.0 before 49.0.4 fails to check forwarded trailers against the WasiHttpHooks::is_forbidden_header hook in wasi-http p3. bytecodealliance · wasmtime 18 days ago medium6.3 CVE-2026-121441 Wasmtime before 36.0.19, 37.0.0 before 48.0.7, and 49.0.0 before 49.0.4 contains a request smuggling vulnerability in wasi-http that allows guests to set multi… bytecodealliance · wasmtime 18 days ago medium6.9 CVE-2026-121439 Wasmtime 46.0.0 before 48.0.7 and 49.0.0 before 49.0.4 contains a response splitting vulnerability in wasi-http p3 that allows guests to set unvalidated conten… bytecodealliance · wasmtime 18 days ago medium5.9 CVE-2026-119143 Wasmtime 46.0.0 before 48.0.6 and 49.0.0 before 49.0.3 contains a denial of service vulnerability that allows guest code to trigger a host panic through out-of… bytecodealliance · wasmtime 23 days ago medium5.9 CVE-2026-119140 Wasmtime 46.0.0 before 48.0.6 and 49.0.0 before 49.0.3 contains a denial of service vulnerability that allows malicious components to panic the host via thread… bytecodealliance · wasmtime 23 days ago medium5.9 CVE-2026-119139 Wasmtime 46.0.0 before 48.0.6 and 49.0.0 before 49.0.3 contains a leftover assertion in component::Func::call that rejects guest exports using the async ABI op… bytecodealliance · wasmtime 23 days ago medium5.9 CVE-2026-119136 Wasmtime 42.0.0 before 48.0.6 and 49.0.0 before 49.0.3 contains insufficient checks in Store when mixing async-style and sync-style WebAssembly calls. bytecodealliance · wasmtime 23 days ago medium5.9 CVE-2026-119135 Wasmtime 46.0.0 before 48.0.6 and 49.0.0 before 49.0.3 panics when the host reads a component model stream as a different Rust item type than it was created wi… bytecodealliance · wasmtime 23 days ago medium5.9 CVE-2026-119132 Wasmtime from 49.0.0 before 49.0.3 contains a denial-of-service vulnerability that allows a WebAssembly guest to trigger a host panic by transcoding overlappin… bytecodealliance · wasmtime 23 days ago medium6.9 CVE-2026-119131 Wasmtime 46.0.0 before 48.0.6 and 49.0.0 before 49.0.3 contains a denial of service vulnerability in wasmtime-wasi-http that lets guests crash the host by send… bytecodealliance · wasmtime 23 days ago medium5.0 CVE-2026-54786 Wasmtime has a leak in WASIp1 `fd_renumber` implementation rust · wasmtime-wasi 2026-07-01 medium5.4 CVE-2026-35195 Wasmtime has out-of-bounds write or crash when transcoding component model strings rust · wasmtime 2026-04-09 medium6.3 CVE-2026-34988 Wasmtime has data leakage between pooling allocator instances rust · wasmtime 2026-04-09 medium5.0 CVE-2026-34983 Wasmtime has use-after-free bug after cloning `wasmtime::Linker` rust · wasmtime 2026-04-09 medium6.5 CVE-2026-34945 Wasmtime has host data leakage with 64-bit tables and Winch rust · wasmtime 2026-04-09 medium5.7 CVE-2026-34944 Wasmtime segfault or unused out-of-sandbox load with `f64x2.splat` operator on x86-64 rust · wasmtime 2026-04-09 medium6.5 CVE-2026-34942 Wasmtime: Panic when transcoding misaligned utf-16 strings rust · wasmtime 2026-04-09 medium5.9 CVE-2026-27204 Wasmtime WASI implementations are vulnerable to guest-controlled resource exhaustion 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 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 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 medium5.5 CVE-2024-47763 wasmtime has a runtime crash when combining tail calls with trapping imports rust · wasmtime 2024-10-09 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

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.