Repository navigation
deps: ignore the heapless batch RUSTSEC-2026-0574..0582 (none reachable), revisit by 2026-12-31 - #110
Open
SovereignTechnology wants to merge 2 commits into
Open
SovereignTechnology wants to merge 2 commits into
SovereignTechnology wants to merge 2 commits into
Conversation
…r-hex), revisit by 2026-12-31 heapless 0.8.0 IndexMap::insert is unsound on a full map (u16::MAX). It enters only via nostr 0.45 > faster-hex 0.10.1, which uses heapless only for String and Vec, never IndexMap. No faster-hex release moves to heapless >= 0.9.4 (0.10.1 and 1.0.0 require ^0.8). Same dated-ignore shape as RUSTSEC-2026-0387 and -0543, in both deny.toml files.
…le), revisit by 2026-12-31 Nine heapless advisories published together, every one fixed only in heapless >= 0.9.4. heapless enters only via postcard 1.1.3 (0.7.17) and nostr > faster-hex 0.10.1 (0.8.0); both use only heapless Vec and String, and no nfx crate names a heapless type. The affected functions are IndexMap, Deque, SortedLinkedList, spsc, the pools, and Vec IntoIter drop with a panicking element Drop: none reachable. Replaces the single -0582 entry.
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.
cargo denyfails every nfxchecksince nine heapless advisories were published together on 2026-11-18. Main is affected too; #108, which changes only JavaScript, showed it.The advisories. RUSTSEC-2026-0574 to -0582 are all
unsound, not vulnerabilities, and every one is fixed only in heapless >= 0.9.4. The affected functions:IndexMap::insertand::truncate(-0582, -0576);Deque::try_fromand::make_contiguous(-0579, -0581);SortedLinkedListFindMutView::popand::zeroize(-0574, -0578);spsc::Spsc::peek(-0575);Deque/HistoryBuf/IndexMapclears and invec::IntoIter::drop(-0577).Why none is reachable here. heapless enters only through two crates, and no nfx crate names a heapless type:
postcard 1.1.3, which uses onlyheapless::Vecandheapless::String.nostr 0.45 > faster-hex 0.10.1, which uses onlyheapless::Stringandheapless::Vec(src/encode.rs:13).Both were read from the
.cratefiles whose sha256 equals the lock's checksum (postcard6764c3b5…, faster-hex04839bdf…). -0577'sVeccase needs an element whoseDroppanics. The elements here are bytes, or serde-visited values of crates that never name heapless.Why not upgrade. No release of postcard or faster-hex uses heapless >= 0.9.4: faster-hex 0.10.1 and 1.0.0 both require
^0.8, and nostr 0.45.x requiresfaster-hex ^0.10.Change. Dated ignores in
crates/deny.tomlandcrates/desktop/deny.toml, in the same shape as RUSTSEC-2026-0387 and -0543: reasons, paths, a removal condition, and revisit by 2026-12-31. Nothing else changes.deny.tomlis not undercrates/ci/locked.sha256.Summary by CodeRabbit