Repository navigation
zstd, zstd-safe: add the backported fixes in 0.13.4 and 7.4.0 - #3479
Merged
Merged
Conversation
The fix was backported to the previous release line, in zstd 0.13.4.
The fix was backported to the previous release line, in zstd-safe 7.4.0.
The fix was backported to the previous release line, in zstd-safe 7.4.0.
The fix was backported to the previous release line, in zstd-safe 7.4.0.
The fix was backported to the previous release line, in zstd-safe 7.4.0.
The fix was backported to the previous release line, in zstd-safe 7.4.0.
The fix was backported to the previous release line, in zstd-safe 7.4.0.
The fix was backported to the previous release line, in zstd-safe 7.4.0.
The fix was backported to the previous release line, in zstd-safe 7.4.0.
The fix was backported to the previous release line, in zstd-safe 7.4.0.
The fix was backported to the previous release line, in zstd-safe 7.4.0.
The fix was backported to the previous release line, in zstd-safe 7.4.0.
The fix was backported to the previous release line, in zstd-safe 7.4.0.
There was a problem hiding this comment.
🟢 Approval recommended
No active review issues block the advisory updates recognizing backported zstd and zstd-safe security fixes.
No open issues 🎉
What changed in this PR
Updates 13 RustSec advisories to recognize backported security fixes, allowing downstream users to stay on the previous zstd and zstd-safe release lines.
Changes:
- Adds zstd
^0.13.4and zstd-safe^7.4.0to the respective patched ranges. - Splits affected-function ranges to exclude the backports while preserving coverage of vulnerable newer releases.
| File | Description |
|---|---|
crates/zstd/RUSTSEC-2026-0391.md |
Records the context-reuse fix in zstd 0.13.4. |
crates/zstd-safe/RUSTSEC-2026-0406.md |
Records the multithreaded context use-after-free backport. |
crates/zstd-safe/RUSTSEC-2026-0405.md |
Records the seekable compression bounds-checking backport. |
crates/zstd-safe/RUSTSEC-2026-0404.md |
Records the decoder cloning double-free backport. |
crates/zstd-safe/RUSTSEC-2026-0403.md |
Records the streaming decompression uninitialized-memory backport. |
crates/zstd-safe/RUSTSEC-2026-0402.md |
Records the encoder cloning buffer-overflow backport. |
crates/zstd-safe/RUSTSEC-2026-0401.md |
Records the dictionary training out-of-bounds read backport. |
crates/zstd-safe/RUSTSEC-2026-0400.md |
Records the dictionary decompression use-after-free backport. |
crates/zstd-safe/RUSTSEC-2026-0399.md |
Records the dictionary initialization lifetime backport. |
crates/zstd-safe/RUSTSEC-2026-0398.md |
Records the seekable decompression bounds-checking backport. |
crates/zstd-safe/RUSTSEC-2026-0397.md |
Records the output-buffer uninitialized-memory backport. |
crates/zstd-safe/RUSTSEC-2026-0396.md |
Records the seekable null-pointer backport. |
crates/zstd-safe/RUSTSEC-2026-0395.md |
Records the context parameter use-after-free backport. |
Review effort: Balanced
This was referenced Nov 1, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Affected crate(s)
Links to upstream issue(s) or PR(s)
Severity
Unchanged. This PR only updates existing advisories: I maintain zstd-rs, and the fixes behind RUSTSEC-2026-0391 and RUSTSEC-2026-0395 through 0406 were backported to the previous release lines, since several large downstream crates can't move to zstd 0.14 / zstd-safe 8 yet:
Each advisory gets its own commit, which adds the backport to
patchedand splits theaffected.functionsranges around it. For example,[">= 4.1.0, < 8.2.0"]becomes[">= 4.1.0, < 7.4.0", ">= 8.0.0, < 8.2.0"].rustsec-admin lintpasses at the revision CI pins.Checklist
RUSTSEC-0000-0000as the ID (n/a: existing advisories keep their assigned IDs)datefield is set to the public disclosure date (unchanged)