RUSTSEC-2026-0331 Panic on Decoding Short Hybrid Keys

The deserialization functions X25519MlKem768Draft00PrivateKey::decode X25519MlKem768Draft00PublicKey::decode and XWingKemDraft06PublicKey::decode would panic during an indexing operation when provided an input slice that is shorter than the length of the given key type, i.e. shorter than 2400 byt...

RUSTSEC-2026-0018 `rpc-check` was removed from crates.io for malicious code

This is part of an ongoing campaign to attempt to typosquat crates in the polymarket-client-sdk ecosystem to exfiltrate user credentials. The malicious crate had 6 versions published from 2026-02-20 onwards and had no evidence of actual usage. There were no crates depending on this crate on...

RUSTSEC-2025-0147 `evm-units` was removed from crates.io for malicious code

It appeared to be attempting to steal cryptocurrency...

RUSTSEC-2025-0106 Undefined behavior in index_of_ptr with empty slices

The safe function indexofptr causes undefined behavior when called with an empty slice. The issue occurs in the line ptr.addslice.len - 1 which underflows when slice.len is 0, creating a pointer with a massive offset. According to Rust's safety rules, creating such a pointer causes immediate...

RUSTSEC-2025-0171 soundness issue

mod3dbase::BufferData::asptr lack of sufficient checks to its public self field byteoffset and used unsafely to do the pointer calculation...

RUSTSEC-2025-0170 `hugepage_rs::dealloc` may allow invalid memory deallocation from safe code

hugepagers::dealloc was a publicly accessible safe function. It accepted an arbitrary raw pointer and Layout, then forwarded them to the hugepage allocator's GlobalAlloc::dealloc implementation. GlobalAlloc::dealloc requires callers to ensure that the pointer denotes a block of memory currently...

RUSTSEC-2024-0391 Ambiguous challenge derivation

Challenge derivation in non-interactive ZK proofs was ambiguous and that could lead to security vulnerability however, it's unknown if it could be exploited...

RUSTSEC-2024-0405 op_panic in the base runtime can force a panic in the runtime's containing thread

Affected versions use denocore releases that expose Deno.core.ops.oppanic to the JS runtime in the base core This function when called triggers a manual panic in the thread containing the runtime. It can be fixed by stubbing out the exposed op: javascript Deno.core.ops.oppanic = msg = throw new...

RUSTSEC-2024-0442 Dump Undefined Memory by `JitDumpFile`

The unsound function dumpcodeloadrecord uses fromrawparts to directly convert the pointer addr and len into a slice without any validation and that memory block would be dumped. Thus, the 'safe' function dumpcodeloadrecord is actually 'unsafe' since it requires the caller to guarantee that the ad...

RUSTSEC-2023-0059 Unaligned read of `*const *const c_char` pointer

Affected versions dereference a potentially unaligned pointer. The pointer is commonly unaligned in practice, resulting in undefined behavior. In some build modes, this is observable as a panic followed by abort. In other build modes the UB may manifest in some other way, including the possibilit...

RUSTSEC-2023-0126 Aliasing violation in `OrdSet` insertion

Inserting into an im::OrdSet for example by collecting an iterator into one can violate Rust's aliasing rules: Miri reports a stacked borrows violation in sizedchunks::Chunk::forcecopy, which is called during insertion, where a shared borrow is invalidated by a unique borrow before the read throu...

RUSTSEC-2026-0323 fd_readdir copies uninitialized struct padding into guest memory

This is an entry in the RustSec database for the Wasmtime security advisory located at https://github.com/bytecodealliance/wasmtime/security/advisories/GHSA-96f6-r43r-8c24 For more information see the GitHub-hosted security advisory...

RUSTSEC-2026-0317 A 512-byte workbook can provoke a multi-gigabyte allocation and abort the process

Affected versions passed caller-supplied bytes to calamine's Xlsx::new without first checking that they were a ZIP archive. Xlsx::new tests for password protection on its first line, which parses the input as an OLE/CFB container, and a sector-count field read from the file's own header reaches...

RUSTSEC-2026-0314 Guest can panic host through filesystem datetime overflow

This is an entry in the RustSec database for the Wasmtime security advisory located at https://github.com/bytecodealliance/wasmtime/security/advisories/GHSA-j2g9-4prp-pf6h For more information see the GitHub-hosted security advisory...

RUSTSEC-2026-0028 `tracing_checks` was removed from crates.io for transitively including malicious code

This is part of an ongoing campaign to attempt to typosquat crates in an attempt to exfiltrate Polymarket credentials. The malicious crate had 1 version published on 2026-02-26 approximately 9 hours before removal and had no evidence of actual usage, both in terms of downloads and dependents. It...

RUSTSEC-2025-0005 Out of bounds write triggered by crafted coverage data

Function grcov::covdir::getcoverage uses the unsafe function getuncheckedmut without validating that the index is in bounds. This results in memory corruption, and could potentially allow arbitrary code execution provided that an attacker can feed the tool crafted coverage data...

RUSTSEC-2024-0443 webp crate may expose memory contents when encoding an image

Affected versions of this crate did not check that the input slice passed to "webp::Encoder::encode is large enough for the specified image dimensions. If the input slice is too short, the library will read out of bounds of the buffer and encode other memory contents as an image, resulting in...

RUSTSEC-2024-0392 Ambiguous challenge derivation

Challenge derivation in non-interactive ZK proofs was ambiguous and that could lead to security vulnerability however, it's unknown if it could be exploited...

RUSTSEC-2023-0094 `martin-mbtiles` has been renamed to `mbtiles`

Please use the mbtiles crate going forward...

RUSTSEC-2026-0353 Panic when invoking an async-lifted function via `call`

This is an entry in the RustSec database for the Wasmtime security advisory located at https://github.com/bytecodealliance/wasmtime/security/advisories/GHSA-m6w2-jwq2-cv2c For more information see the GitHub-hosted security advisory...

RUSTSEC-2026-0335 Pre-shared key mode transmits the TGK in cleartext, exposing the SRTP master key

mykey implements MIKEY RFC 3830 for SRTP key exchange. Pre-shared key mode transmitted the TEK Generation Key TGK in the clear. MikeyMessage::newpskinit built its KEMAC payload with EncAlg::Null and placed the TGK in encdata verbatim. Anyone able to read a PSK-Init message therefore recovers the...

RUSTSEC-2026-0337 Poly1305 panics or computes a wrong tag on attacker-chosen messages of 64 bytes or more

Poly1305 in ic-cipher absorbs messages of 64 bytes or more four blocks at a time, summing four products before one reduction. From 0.2.5 to 0.2.19 the reduction kept its carries in 32-bit integers, which four summed products can overflow when the message's bytes are large. This affects Poly1305 a...

RUSTSEC-2026-0315 `call_ref` and exception `catch` can drop some fuel accounting, leading to exponential fuel amplification

This is an entry in the RustSec database for the Wasmtime security advisory located at https://github.com/bytecodealliance/wasmtime/security/advisories/GHSA-m63x-6p34-q65x For more information see the GitHub-hosted security advisory...

RUSTSEC-2026-0316 Dynamic record lifting can allocate beyond the hostcall fuel limit

This is an entry in the RustSec database for the Wasmtime security advisory located at https://github.com/bytecodealliance/wasmtime/security/advisories/GHSA-jqpg-j7w6-42pr For more information see the GitHub-hosted security advisory...

RUSTSEC-2025-0150 `finch-rst` was removed from crates.io for malicious code

This attempts to typosquat the existing crate finch to steal credentials from local files. The malicious crate had 1 version published on 2025-12-08 and had been downloaded 21 times. There were no crates depending on this crate on crates.io. Thanks to Matthias Zepper of NGI Sweden for reporting...

RUSTSEC-2025-0052 async-std has been discontinued

The async-std has been discontinued. Alternatives: - smol...

RUSTSEC-2025-0042 Uninitialized read after allocating MemBump

The affected function, MemBump::new, would allocate memory without initializing it. Subsequently calling the created value's various alloc methods would then read and write the start of that memory as a Cell which is undefined behavior. Instead, it should zero initialize the start of the allocate...

RUSTSEC-2023-0037 crate has been renamed to `crypto_secretbox`

This crate has been forked/renamed from xsalsa20poly1305 to cryptosecretbox. The new repository location is at:...

RUSTSEC-2026-0363 Component-model handle tables are capped only per instance and charged to no limit

This is an entry in the RustSec database for the Wasmtime security advisory located at https://github.com/bytecodealliance/wasmtime/security/advisories/GHSA-q554-3cjc-rx7p For more information see the GitHub-hosted security advisory...

RUSTSEC-2026-0347 Buffered application data sent to outer server after ECH rejection

When a server rejects Encrypted Client Hello ECH, the client completes the handshake using the outer ClientHello and authenticates the server against the ECH config's publicname. At the end of that handshake, rustls encrypted and queued any application data buffered via ClientConnection::writer...

RUSTSEC-2026-0360 Overlapping string transcode in a fused adapter can panic

This is an entry in the RustSec database for the Wasmtime security advisory located at https://github.com/bytecodealliance/wasmtime/security/advisories/GHSA-54p9-vhhq-8f7q For more information see the GitHub-hosted security advisory...

RUSTSEC-2026-0349 Unauthenticated ServerHello can downgrade later connections to classical key exchange

The client recorded the server-selected key exchange group for each server name when processing the ServerHello, before the server was authenticated. This record is used to predict which key share to send in future ClientHellos to that server name. A network attacker can answer one connection...

RUSTSEC-2026-0350 Guests can send absolute-form HTTP requests to different hosts

This is an entry in the RustSec database for the Wasmtime security advisory located at https://github.com/bytecodealliance/wasmtime/security/advisories/GHSA-5qpp-g3j2-8frx For more information see the GitHub-hosted security advisory...

RUSTSEC-2026-0345 Untrusted labels can inject SVG attributes, CSS values, and terminal escape sequences

Affected versions of kuva wrote data-derived strings straight into rendered output without escaping them for the target format. Applications that plot untrusted input column headers, category and group names, series labels were affected in three places. 1. SVG attribute injection / stored XSS...

RUSTSEC-2026-0039 `chrono_anchor` was removed from crates.io due to malicious code

The chronoanchor crate attempted to exfiltrate .env files to a server that was in turn impersonating the legitimate timeapi.io service. The malicious crate had 1 version published on 2026-03-04 approximately 6 days before removal and had no evidence of actual downloads. There were no crates...

RUSTSEC-2025-0034 soundness issue and unmaintained

FastMap::get lacks sufficient checks to its parameter index and is used to unsafely get a Vec element. fastidmap is unmaintained...

RUSTSEC-2026-0358 Yielding in a component start function can lead to a host panic

This is an entry in the RustSec database for the Wasmtime security advisory located at https://github.com/bytecodealliance/wasmtime/security/advisories/GHSA-5hhx-4wrr-3j9g For more information see the GitHub-hosted security advisory...

RUSTSEC-2026-0356 Panic on erroneous call-to-host from guest realloc call

This is an entry in the RustSec database for the Wasmtime security advisory located at https://github.com/bytecodealliance/wasmtime/security/advisories/GHSA-7v24-42x9-pxf7 For more information see the GitHub-hosted security advisory...

RUSTSEC-2026-0352 Filesystem sandbox escape when renaming symlinks with trailing slashes

This is an entry in the RustSec database for the Wasmtime security advisory located at https://github.com/bytecodealliance/wasmtime/security/advisories/GHSA-m9f7-9w4p-gv38 For more information see the GitHub-hosted security advisory...

RUSTSEC-2026-0361 Panic when pending calls are run after a trap

This is an entry in the RustSec database for the Wasmtime security advisory located at https://github.com/bytecodealliance/wasmtime/security/advisories/GHSA-hmwq-g22x-qjw5 For more information see the GitHub-hosted security advisory...

RUSTSEC-2026-0344 Decompression bomb in `ruzstd`: a tiny input can exhaust memory (OOM)

A crafted .zst input under 128 KB can force ruzstd to allocate several gigabytes at once, crashing the process with an out-of-memory condition. Since ruzstd is a decoder for untrusted input, a single small file is enough to take down anything decoding it. The compressed size of a block was capped...

RUSTSEC-2026-0343 Outgoing datagram buffer accounting can panic the sender in quinn-proto

The limit on memory used to buffer outgoing datagrams, introduced in 0.11.17, subtracted an evicted datagram's size from the buffered byte counter twice when Datagrams::send was called with drop = true as Connection::senddatagram in the quinn crate does while the buffer was full. Under sustained...

RUSTSEC-2026-0341 Stream reassembly memory-exhaustion guard in quinn-proto can be bypassed

The fix for RUSTSEC-2026-0185 in 0.11.15 added a cap on the number of chunks buffered by the Assembler that reassembles out-of-order stream data. However, the cap was only checked inside the branch that triggers defragmentation, which only runs when the estimated over-allocation exceeds a thresho...

RUSTSEC-2024-0448 `parse_arguments` reads a caller-supplied pointer as a slice

parsearguments is safe. It takes arguments: const AnyObject and argc, and calls slice::fromrawpartsarguments, argc as usize. It does not check that arguments is non-null and aligned, or that argc elements are initialized. Safe Rust can pass a null pointer or a length past the allocation. The...

RUSTSEC-2024-0449 unsafe-libyaml is unmaintained

The repository was archived by its owner on 2024-03-25 and is read-only. The last release is 0.2.11 March 2024. unsafe-libyaml is a machine translation of libyaml's C code into unsafe Rust c2rust. Bugs found in it will not be fixed upstream. It is used by serdeyaml itself deprecated and by forks...

RUSTSEC-2026-0364 Exception tags can cause host data structures to be unaligned

This is an entry in the RustSec database for the Wasmtime security advisory located at https://github.com/bytecodealliance/wasmtime/security/advisories/GHSA-p79w-pv2r-29qp For more information see the GitHub-hosted security advisory...

RUSTSEC-2026-0359 Stack overflow dropping a long chain of recursive types

This is an entry in the RustSec database for the Wasmtime security advisory located at https://github.com/bytecodealliance/wasmtime/security/advisories/GHSA-wjc8-633q-pwxr For more information see the GitHub-hosted security advisory...

RUSTSEC-2026-0362 Wasmtime may not properly enforce async-entrypoint requirement

This is an entry in the RustSec database for the Wasmtime security advisory located at https://github.com/bytecodealliance/wasmtime/security/advisories/GHSA-vcg5-q8m5-8379 For more information see the GitHub-hosted security advisory...

RUSTSEC-2026-0355 Panic viewing component model stream or future as the wrong type

This is an entry in the RustSec database for the Wasmtime security advisory located at https://github.com/bytecodealliance/wasmtime/security/advisories/GHSA-63h4-6cx9-pjfj For more information see the GitHub-hosted security advisory...

RUSTSEC-2026-0348 Brotli certificate decompression can allocate up to 1 GiB before authentication

The built-in Brotli certificate decompressor enabled by the non-default brotli crate feature bounded the size of the decompressed output, but accepted a peer-selected history window. Brotli's large-window extension was enabled, so a five-byte header could cause an allocation of 1 GiB. A peer can...