[Nic-dorman]

Linear issue

Closes V2-1737

Part of V2-1733, which tracks the same move across every affected WithAutonomi lockfile.

Risk tier

• T0 — docs / tooling / CI / pure UX-output. Repo CI only.
• T1 — client-only, no network-facing behavior change. CI + prod compat smoke.
• T2 — node/client logic with behavioral surface, no protocol/format/economics change. Dev testnet + ADR.
• T3 — protocol / storage format / payments / routing. T2 evidence + adversarial testing.

This tier is proposed rather than asserted, and matches the earlier lockfile advisory moves (V2-1659). The change is lockfile only: tokio moves from 1.52.3 to 1.53.3, and only its version and checksum change. RUSTSEC-2026-0386 is informational ("unsound"). The safe AsyncFd constructors violate I/O safety, so closing a duplicated fd can lead to a use-after-free. It is Unix-only. The patched versions are 1.51.6 and 1.53.3 or later. No Autonomi protocol message changes.

Compatibility

• Wire: none.
• Storage: none.
• API: none. No manifest or source file is touched.

Semver impact

• breaking
• feature
• fix

Test evidence

cargo update --precise on cargo 1.97 also rewrote unrelated windows-sys edges, so the tokio version and checksum were edited by hand. The checksum is the one cargo itself resolved.

• cargo metadata --locked: pass
• cargo check --locked --all-targets: pass
• cargo audit: RUSTSEC-2026-0386 is present before the change and gone after. No new advisories.

New dependency

none

ADR

n/a

Mitigation / rollback

Revert the single Cargo.lock commit. tokio goes back to 1.52.3.

🤖 Generated with Claude Code

[grumbach]

Checked at f6ae551.

• The diff only changes tokio's version and checksum in Cargo.lock. Every other file is the same as main (f388aca).
• The new checksum is the crates.io one for tokio 1.53.3. 1.52.3 is affected by RUSTSEC-2026-0386, and 1.53.3 is in the patched range (>= 1.53.3).
• tokio 1.53.3 declares the same dependencies as 1.52.3 (its feature list only adds the empty schedule-latency feature), so the unchanged dependency list is right. cargo metadata --locked passes, and cargo tree -i tokio shows a single tokio, 1.53.3.
• cargo update -p tokio --precise 1.53.3 on main writes the same tokio entry, but it also rewrites 7 unrelated windows-sys dependency lines. The hand edit avoids that drift.
• cargo audit no longer reports RUSTSEC-2026-0386 and reports nothing new. RUSTSEC-2026-0387 (crypto-bigint 0.5.5) is also on main, so it does not come from this PR.
• Nothing in this repo or its dependency graph calls the AsyncFd constructors that 1.53.3 deprecates.
• Between 1.52.3 and 1.53.3, tokio ships small changes and upstream bug fixes (mpsc, timers, runtime shutdown, io::Chain, DuplexStream) plus the new AsyncFd::register API. I am fine with T1 for this lockfile-only advisory fix.
• CI on this head: 12/12 passing.