Skip to main content
Mallory
← Back to News
package-repository-poisoning

Rust 1.100 Adds Opt-In Cargo Dependency Cooldowns to Reduce Supply-Chain Risk

Supply Chain Risk · 2 sources · Updated 1d ago · First seen Nov 16, 2026

Rust 1.100 Adds Opt-In Cargo Dependency Cooldowns to Reduce Supply-Chain Risk

The Rust Release Team released Rust 1.100.0 with an opt-in Cargo dependency cooldown designed to reduce exposure to newly published malicious or compromised package versions. The configurable min-publish-age setting delays selection of dependency releases until they reach a minimum publication age, while allowing exceptions for urgent updates. The safeguard has important gaps: it does not exclude versions already recorded in Cargo.lock, versions without publication timestamps, or packages and dependencies selected through Cargo’s package-installation workflow. Registry-side quarantine and suspicious-release detection remain planned features, not protections delivered in this release.

Cargo also adds unused-dependency linting and makes package installation use the packaged lockfile by default, improving dependency consistency separately from the cooldown control. Other changes include stabilization of the never type and core allocator APIs, a new unsafe API for constructing zero-sized types whose misuse can violate safety preconditions, and a revised build-directory layout intended to reduce cache collisions. Teams adopting the release should evaluate cooldown policies and exceptions, check lockfile and installation coverage, and review compatibility warnings and CI assumptions about build-artifact locations. The release provides preventive hardening; neither reference reports an associated compromise or CVE.

Does this reach your builds?Trace attribution and downstream blast radius.
Trace the chain
Event timeline

How this story unfolded

Events from the most recent confirmed update back to the earliest known activity.

1 event · Nov 12, 2026
  1. Nov 12, 20266d ago

    Rust 1.100.0 released with opt-in Cargo dependency cooldowns

    The Rust Release Team released Rust 1.100.0, stabilizing configurable Cargo dependency cooldowns that delay adoption of newly published package versions to reduce supply-chain risk. The control supports per-update overrides but does not restrict versions already in Cargo.lock, versions lacking registry publication timestamps, or cargo install operations.

    Announcing Rust 1.100.0 | Rust Blog
Do you run this?See attribution and downstream blast radius, and whether this package or vendor reaches your builds.
Trace the Supply Chain
Mallory platform

See the full picture, correlated to your attack surface.

This page covers what’s public. Mallory adds the parts that aren’t: which of your assets are affected, which threat actors are using it right now, and what to deploy next.

Exposure mappingMap indicators from this story to your assets and identify affected systems in minutes.
Threat actor evidenceEvery observed campaign, victim, and pivot linked to actors named in this story.
Associated malwareMalware, exploits, and IOCs connected to the activity described here.
Detection signaturesYARA, Sigma, and Snort rules deployed to your SIEM as soon as they’re published.
Scheduled alertsGet matching new stories delivered to your team as they break, not the next morning.
AI threadsAsk questions about this story and take action on the answers.