Repository navigation
Add advisory: zip unbounded symlink-target allocation (CVE-2026-115909) - #3451
Open
li-jin-quan wants to merge 1 commit into
Open
li-jin-quan wants to merge 1 commit into
li-jin-quan wants to merge 1 commit into
Conversation
GHSA-q7v9-x93c-xqv3, published 2026-10-22, patched in 9.0.0.
Member
|
Please use the pull request template. |
This branch has not been deployed
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.
Adds
crates/zip/RUSTSEC-0000-0000.mdfor CVE-2026-115909 / GHSA-q7v9-x93c-xqv3.What the bug is:
ZipArchive::extract()sized the symlink-target buffer fromuncompressed_sizedeclared in the central directory, before reading any entry data.Vec::with_capacityis infallible, so a refused reservation callshandle_alloc_error()and aborts the process. Not a panic:catch_unwinddoes not catch it.2^62is enough to getAborted (core dumped)(exit 134). The declared size only has to exceed the address space, not the RAM.Status upstream: the advisory was published 2026-10-22 and the CVE assigned 2026-10-26. The fix shipped in 9.0.0 via zip-rs/zip2#984; crates.io currently has 9.1.2. So
patched = [">= 9.0.0"]and the embargo question does not apply here.aliasescarries both the CVE and the GHSA id. Doesdenial-of-servicelook like the right category, or would you rather file this under something else?