cargo-audit-rust

Overview

cargo-audit scans a project's Cargo.lock against the RustSec Advisory Database (opens in new window) for vulnerable, unmaintained, unsound, and yanked crates.

Differentiation from npm-pip-maven-audit: that skill lists cargo audit as one line in a multi-ecosystem wrapper; this skill covers the Rust-specific depth (--deny semantics, audit.toml schema, cargo audit fix, SARIF, binary auditing, the rustsec/audit-check Action).

When to use

• Rust project has a Cargo.lock (binary or library with lockfile committed).
• CI must gate on new RustSec advisories in addition to compile checks.
• Team wants automated fix PRs for vulnerable transitive dependencies.
• Unmaintained or unsound crates must surface as hard failures, not just informational warnings.
• Layered SCA: pair with osv-scanner for cross-DB consensus (OSV.dev imports RustSec advisories, so divergence flags a DB-specific gap).

Step 1 - Install

Per cargo-audit README (opens in new window):

cargo install cargo-audit --locked

Minimum Rust version: 1.74 per rustsec-readme (opens in new window).

Platform package managers (consult rustsec-readme (opens in new window) for current availability):

# Alpine Linux
apk add cargo-audit

# Arch Linux
pacman -S cargo-audit

# macOS Homebrew
brew install cargo-audit

To enable the cargo audit fix subcommand, install with the fix feature (rustsec-readme (opens in new window)):

cargo install cargo-audit --features=fix --locked

Step 2 - Basic scan

Run at the workspace root where Cargo.lock lives (rustsec-readme (opens in new window)):

cargo audit

Scan a specific lockfile path (rustsec-readme (opens in new window)):

cargo audit -f path/to/Cargo.lock

cargo-audit fetches the RustSec Advisory Database on first run (a git clone into ~/.cargo/advisory-db). Pass --no-fetch to skip the fetch in air-gapped environments (rustsec-readme (opens in new window)).

Step 3 - Exit codes and --deny flags

Exit codes per cargo-audit source (opens in new window):

The --deny flag turns advisory categories into hard failures (cargo-audit source - audit.rs (opens in new window)):

# Fail on any vulnerability
cargo audit --deny warnings

# Fail on unmaintained crates specifically
cargo audit --deny unmaintained

# Fail on unsound (memory-unsafe) crates
cargo audit --deny unsound

# Fail on yanked crates in the lockfile
cargo audit --deny yanked

# Combine: fail on vulnerabilities AND unmaintained
cargo audit --deny warnings --deny unmaintained

--deny warnings is the special catch-all: it enables all denial categories simultaneously per audit.rs source (opens in new window).

Step 4 - Output formats

Per cargo-audit source (opens in new window), --format supports three values:

# JSON output for programmatic consumption
cargo audit --format json > cargo-audit.json

# SARIF output for GitHub Security tab
cargo audit --format sarif > cargo-audit.sarif

Step 5 - audit.toml suppression

Persistent suppression belongs in .cargo/audit.toml at the repo root, not CLI --ignore flags (not auditable in git). Every ignored advisory carries a mandatory reason and re-review date:

[advisories]
ignore = ["RUSTSEC-2024-0999"]
# RUSTSEC-2024-0999: serde_cbor unmaintained
# Reason: we use serde_cbor only in test fixtures, not in production paths.
# Approved-by: alice@example.com
# Re-review-date: 2026-09-30
# Tracking: JIRA-4567

Commit .cargo/audit.toml so suppressions are auditable in git history and code review. The full [advisories]/[output]/[database] config schema is in references/cargo-audit-config-and-ci.md.

Step 6 - cargo audit fix

cargo audit fix automatically updates Cargo.toml version constraints to pull in patched crate versions, then runs cargo update (rustsec-readme (opens in new window)):

# Preview changes without modifying files
cargo audit fix --dry-run

# Apply updates
cargo audit fix

Limitations: cargo audit fix is experimental per rustsec-readme (opens in new window); it updates version constraints but cannot resolve conflicts in the dependency graph - manual intervention is needed when the patched version is incompatible with other constraints. Always run cargo test after applying fixes.

Step 7 - CI and binary auditing

GitHub Actions integration (the official rustsec/audit-check action plus SARIF upload) and compiled-binary auditing (cargo auditable build + cargo audit bin) are in references/cargo-audit-config-and-ci.md.

Anti-patterns

Limitations

• Reachability analysis is not included: every CVE on a declared dependency counts even if the vulnerable function is not called. Pair with manual code review for high-severity suppressions.
• cargo audit fix is experimental per rustsec-readme (opens in new window) and cannot resolve conflicting version constraints automatically.
• The RustSec DB covers crates published on crates.io; vendored or path-dependency crates are not covered.
• Binary auditing requires cargo-auditable to have been used at compile time; binaries without embedded metadata cannot be audited (Step 7).

References

• rustsec-readme (opens in new window) - cargo-audit install, usage, flags, fix
• audit-check-action (opens in new window) - rustsec/audit-check GitHub Action
• rustsec-advisories (opens in new window) - RustSec advisory database browser
• Full audit.toml schema, binary auditing, and CI wiring: references/cargo-audit-config-and-ci.md
• rustsec.org - RustSec project home; ecosystem tools (cargo-deny, cargo-auditable)
• github.com/rustsec/rustsec - monorepo: cargo-audit, rustsec crate, advisory-db
• npm-pip-maven-audit - multi-ecosystem native audit wrapper (mentions cargo-audit as one of eight tools)
• osv-scanner - cross-DB pair; OSV.dev receives RustSec exports in real time