Skip to content

fix(deps): clear all known CVEs from the dependency graph - #313

Merged
geekgonecrazy merged 5 commits into
devfrom
fix/cve-dependency-remediation
Nov 2, 2026
Merged

geekgonecrazy merged 5 commits into
devfrom
fix/cve-dependency-remediation

Conversation

@graywolf336

Copy link
Copy Markdown
Contributor

cargo audit reported 8 vulnerable crates (two CVE-backed) plus a HIGH npm advisory. It now reports 0 vulnerabilities.

Changes

  • zstd 0.13 → 0.14.3 (zstd-safe 8.2.0, zstd-sys 2.1.2): cross-stream plaintext leak (RUSTSEC-2026-0391), the 0395–0406 UAF/OOB family, wasm allocator corruption (0410).
  • git2 0.19 → 0.21 (libgit2 1.9.7): UB in Buf, Remote::list, blame signatures (RUSTSEC-2026-0008/0183/0184). 0.21 stops enabling ssh/https/cred by default — made explicit, else transports and credential helpers silently disappear. ~40 Result-returning accessor call sites migrated.
  • ed25519-dalek 3.0 + sha1/sha2 0.11: drops vulnerable block-buffer 0.10.4 (GHSA-qwgh-2vcv-g2f7). digest 0.11 lost LowerHex/io::Write, so fingerprints use an explicit hex encoder + hasher Write adapter; manifest bytes unchanged, covered by a regression test.
  • Patch bumps: rustls-webpki 0.103.16, webpki-roots 1.0.11, libz-sys 1.1.31, ctutils 0.4.7, inout 0.2.5 (CVE-2026-111943, RUSTSEC-2026-0381/0385/0418).
  • indicatif 0.18 / postcard without heapless: removes unmaintained number_prefix and atomic-polyfill.
  • opencode-atomic-hooks: overrides: zod ^4.6.7 (GHSA-mrhx-c7xc-m3w5, HIGH).

Verification

cargo audit exit 0 (workspace + shacl spike), OSV cross-check clean, cargo build / clippy -D warnings / doc / fmt green; core 3706, repository 1528+233, agent 1394, CLI 2194+152 integration tests pass. Remaining audit output is one unmaintained warning (unsafe-libyaml, via serde_yaml_ng, no fix available).

graywolf336 and others added 5 commits October 30, 2026 10:04
`cargo audit` reported 8 vulnerable crates (two CVE-backed) and one HIGH
npm advisory; `cargo audit` now reports 0 vulnerabilities.

- zstd 0.13.3 → 0.14.3, zstd-safe 8.2.0, zstd-sys 2.1.2
  (RUSTSEC-2026-0391 cross-stream plaintext leak, the 2026-0395..0406
  UAF/OOB family, RUSTSEC-2026-0410 wasm allocator corruption)
- git2 0.19 → 0.21, libgit2 1.9.7 (RUSTSEC-2026-0008/0183/0184 UB in
  Buf, Remote::list and blame signatures). 0.21 no longer enables the
  ssh/https/cred features by default, so they are now explicit — dropping
  them would silently remove transports and credential helpers. Accessors
  that became `Result`-returning were migrated at ~40 call sites.
- ed25519-dalek 2.2 → 3.0 with sha1/sha2 0.11, which drops the
  vulnerable block-buffer 0.10.4 (GHSA-qwgh-2vcv-g2f7). digest 0.11 no
  longer implements LowerHex/io::Write, so scope fingerprints get an
  explicit hex encoder plus a hasher Write adapter; the existing
  manifest format is byte-identical and covered by a regression test.
- rustls-webpki 0.103.16, webpki-roots 1.0.11, libz-sys 1.1.31,
  ctutils 0.4.7, inout 0.2.5 (CVE-2026-111943 distrusted-intermediate
  acceptance, RUSTSEC-2026-0381/0385/0418)
- indicatif 0.18 and postcard without its heapless feature, removing the
  unmaintained number_prefix and atomic-polyfill crates
- opencode-atomic-hooks: override zod ^4.6.7 (GHSA-mrhx-c7xc-m3w5, HIGH
  memory exhaustion)

Remaining audit output is one unmaintained warning (unsafe-libyaml, via
serde_yaml_ng 0.10, no fix available).

Verified: cargo audit exit 0 on the workspace and the shacl spike, OSV
cross-check clean, cargo build/clippy -D warnings/doc/fmt green, and the
core, repository, agent and CLI suites plus git import/shim/binding
integration suites pass.
Follow-up review of the git2 0.21 migration. `Reference::name()` now
returns `Result` where it used to return `Option`, and three enumeration
sites had been converted into hard errors: a single non-UTF-8 ref name
(git allows those) would have aborted binding publication, id lookup,
degraded-binding install and the WIP census. They skip again, as before;
only callers that need one specific name still propagate the error.

Also: hex encoding writes through `fmt::Write` instead of allocating a
`String` per byte, `is_ok_and` replaces an `Option` dance, redundant
`|x| x.to_string()` closures use `ToString::to_string`, a shadowed closure
parameter is renamed, and a test uses two `expect`s instead of
`unwrap().expect()`.

No pedantic-clean regression remains on the touched lines; workspace
`clippy -D warnings`, `fmt` and the agent/repository suites pass.
@geekgonecrazy
geekgonecrazy merged commit cf0b555 into dev Nov 2, 2026
8 checks passed
@geekgonecrazy
geekgonecrazy deleted the fix/cve-dependency-remediation branch November 2, 2026 19:44
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants