zstd-sys
Low-level bindings for the zstd compression library.
Activity
- Latest release
- 1w ago
- Total releases
- 52
- Cadence
- ~43 days
- Last 12 months
- 3
Reach
- Downloads
- 394.3M
Details
- License
- BSD-3-Clause
- First release
- Mar 24, 2017
| Version | Released | |
|---|---|---|
2.1.2+zstd.1.5.7
patch
| ||
2.1.1+zstd.1.5.7
patch
1 CVE
RUSTSEC-2026-0410
Oct 16, 2026
WebAssembly allocator shim corrupts memory on allocation failure On wasm32, zstd-sys provides Whenever the instance cannot grow its memory by what a frame asks for, a small crafted frame (a 9-byte header declaring a 128 MiB window is enough) made decompression write decoded data over the bottom of the module's linear memory, instead of failing. The corruption stays within the wasm sandbox. The flaw was corrected by returning NULL on allocation failure or size
overflow, and by making Fixed in
2.1.2
References Updated Oct 26, 2026 · Source: OSV.dev | ||
2.1.0+zstd.1.5.7
minor
1 CVE
RUSTSEC-2026-0410
Oct 16, 2026
WebAssembly allocator shim corrupts memory on allocation failure On wasm32, zstd-sys provides Whenever the instance cannot grow its memory by what a frame asks for, a small crafted frame (a 9-byte header declaring a 128 MiB window is enough) made decompression write decoded data over the bottom of the module's linear memory, instead of failing. The corruption stays within the wasm sandbox. The flaw was corrected by returning NULL on allocation failure or size
overflow, and by making Fixed in
2.1.2
References Updated Oct 26, 2026 · Source: OSV.dev | ||
2.0.16+zstd.1.5.7
unknown
1 CVE
RUSTSEC-2026-0410
Oct 16, 2026
WebAssembly allocator shim corrupts memory on allocation failure On wasm32, zstd-sys provides Whenever the instance cannot grow its memory by what a frame asks for, a small crafted frame (a 9-byte header declaring a 128 MiB window is enough) made decompression write decoded data over the bottom of the module's linear memory, instead of failing. The corruption stays within the wasm sandbox. The flaw was corrected by returning NULL on allocation failure or size
overflow, and by making Fixed in
2.1.2
References Updated Oct 26, 2026 · Source: OSV.dev | ||
2.0.15+zstd.1.5.7
unknown
1 CVE
RUSTSEC-2026-0410
Oct 16, 2026
WebAssembly allocator shim corrupts memory on allocation failure On wasm32, zstd-sys provides Whenever the instance cannot grow its memory by what a frame asks for, a small crafted frame (a 9-byte header declaring a 128 MiB window is enough) made decompression write decoded data over the bottom of the module's linear memory, instead of failing. The corruption stays within the wasm sandbox. The flaw was corrected by returning NULL on allocation failure or size
overflow, and by making Fixed in
2.1.2
References Updated Oct 26, 2026 · Source: OSV.dev | ||
2.0.14+zstd.1.5.7
unknown
1 CVE
RUSTSEC-2026-0410
Oct 16, 2026
WebAssembly allocator shim corrupts memory on allocation failure On wasm32, zstd-sys provides Whenever the instance cannot grow its memory by what a frame asks for, a small crafted frame (a 9-byte header declaring a 128 MiB window is enough) made decompression write decoded data over the bottom of the module's linear memory, instead of failing. The corruption stays within the wasm sandbox. The flaw was corrected by returning NULL on allocation failure or size
overflow, and by making Fixed in
2.1.2
References Updated Oct 26, 2026 · Source: OSV.dev | ||
2.0.13+zstd.1.5.6
unknown
1 CVE
RUSTSEC-2026-0410
Oct 16, 2026
WebAssembly allocator shim corrupts memory on allocation failure On wasm32, zstd-sys provides Whenever the instance cannot grow its memory by what a frame asks for, a small crafted frame (a 9-byte header declaring a 128 MiB window is enough) made decompression write decoded data over the bottom of the module's linear memory, instead of failing. The corruption stays within the wasm sandbox. The flaw was corrected by returning NULL on allocation failure or size
overflow, and by making Fixed in
2.1.2
References Updated Oct 26, 2026 · Source: OSV.dev | ||
2.0.12+zstd.1.5.6
unknown
1 CVE
RUSTSEC-2026-0410
Oct 16, 2026
WebAssembly allocator shim corrupts memory on allocation failure On wasm32, zstd-sys provides Whenever the instance cannot grow its memory by what a frame asks for, a small crafted frame (a 9-byte header declaring a 128 MiB window is enough) made decompression write decoded data over the bottom of the module's linear memory, instead of failing. The corruption stays within the wasm sandbox. The flaw was corrected by returning NULL on allocation failure or size
overflow, and by making Fixed in
2.1.2
References Updated Oct 26, 2026 · Source: OSV.dev | ||
2.0.11+zstd.1.5.6
unknown
1 CVE
RUSTSEC-2026-0410
Oct 16, 2026
WebAssembly allocator shim corrupts memory on allocation failure On wasm32, zstd-sys provides Whenever the instance cannot grow its memory by what a frame asks for, a small crafted frame (a 9-byte header declaring a 128 MiB window is enough) made decompression write decoded data over the bottom of the module's linear memory, instead of failing. The corruption stays within the wasm sandbox. The flaw was corrected by returning NULL on allocation failure or size
overflow, and by making Fixed in
2.1.2
References Updated Oct 26, 2026 · Source: OSV.dev | ||
2.0.10+zstd.1.5.6
unknown
1 CVE
RUSTSEC-2026-0410
Oct 16, 2026
WebAssembly allocator shim corrupts memory on allocation failure On wasm32, zstd-sys provides Whenever the instance cannot grow its memory by what a frame asks for, a small crafted frame (a 9-byte header declaring a 128 MiB window is enough) made decompression write decoded data over the bottom of the module's linear memory, instead of failing. The corruption stays within the wasm sandbox. The flaw was corrected by returning NULL on allocation failure or size
overflow, and by making Fixed in
2.1.2
References Updated Oct 26, 2026 · Source: OSV.dev | ||
2.0.9+zstd.1.5.5
unknown
1 CVE
RUSTSEC-2026-0410
Oct 16, 2026
WebAssembly allocator shim corrupts memory on allocation failure On wasm32, zstd-sys provides Whenever the instance cannot grow its memory by what a frame asks for, a small crafted frame (a 9-byte header declaring a 128 MiB window is enough) made decompression write decoded data over the bottom of the module's linear memory, instead of failing. The corruption stays within the wasm sandbox. The flaw was corrected by returning NULL on allocation failure or size
overflow, and by making Fixed in
2.1.2
References Updated Oct 26, 2026 · Source: OSV.dev | ||
2.0.8+zstd.1.5.5
unknown
| ||
2.0.7+zstd.1.5.4
unknown
| ||
2.0.6+zstd.1.5.2
unknown
| ||
2.0.5+zstd.1.5.2
unknown
| ||
2.0.4+zstd.1.5.2
unknown
| ||
2.0.3+zstd.1.5.2
unknown
| ||
2.0.2+zstd.1.5.2
unknown
yanked
| ||
2.0.1+zstd.1.5.2
unknown
| ||
2.0.0+zstd.1.5.2
unknown
| ||
1.6.4+zstd.1.5.2
unknown
yanked
| ||
1.6.3+zstd.1.5.2
unknown
| ||
1.6.2+zstd.1.5.1
unknown
| ||
1.6.1+zstd.1.5.0
unknown
| ||
1.6.0+zstd.1.5.0
unknown
| ||
1.5.0+zstd.1.4.9
unknown
| ||
1.4.20+zstd.1.4.9
unknown
| ||
1.4.19+zstd.1.4.8
unknown
| ||
1.4.18+zstd.1.4.7
unknown
| ||
1.4.17+zstd.1.4.5
unknown
| ||
1.4.16+zstd.1.4.5
unknown
| ||
1.4.15+zstd.1.4.4
unknown
| ||
1.4.14+zstd.1.4.3
unknown
| ||
1.4.13+zstd.1.4.3
unknown
| ||
1.4.12+zstd.1.4.2
unknown
| ||
1.4.11+zstd.1.4.1
unknown
| ||
1.4.10+zstd.1.4.0
unknown
| ||
1.4.8+zstd.1.3.8
unknown
| ||
1.4.7+zstd.1.3.8
unknown
| ||
1.4.6+zstd.1.3.7
unknown
| ||
1.4.5+zstd.1.3.6
unknown
| ||
1.4.4+zstd.1.3.5
unknown
| ||
1.4.3+zstd.1.3.4
unknown
| ||
1.4.2+zstd.1.3.3
unknown
| ||
1.4.1+zstd.1.3.2
unknown
| ||
1.4.0+zstd.1.3.2
unknown
| ||
1.3.2
unknown
| ||
1.3.1
unknown
| ||
1.3.0
unknown
| ||
1.2.0
unknown
|