Deps.rs

cargo-release 1.1.1

[![dependency status](https://deps.rs/crate/cargo-release/1.1.1/status.svg)](https://deps.rs/crate/cargo-release/1.1.1)

This project might be open to known security vulnerabilities, which can be prevented by tightening the version range of affected dependencies. Find detailed information at the bottom.

Crate cargo-release

Dependencies

(26 total, 1 outdated, 1 possibly insecure)

CrateRequiredLatestStatus
 anstream^1.0.01.0.0up to date
 anyhow^1.0.1021.0.102up to date
 bstr^1.12.11.12.1up to date
 cargo_metadata^0.230.23.1up to date
 clap^4.5.604.5.60up to date
 clap-cargo^0.18.30.18.3up to date
 dirs-next^2.02.0.0up to date
 dunce^1.0.51.0.5up to date
 env_logger^0.110.11.9up to date
 git-conventional^1.0.01.0.0up to date
 git2^0.20.40.20.4up to date
 globset^0.4.180.4.18up to date
 ignore^0.40.4.25up to date
 indexmap^2.132.13.0up to date
 itertools^0.140.14.0up to date
 log^0.40.4.29up to date
 maplit^1.01.0.2up to date
 quick-error^2.02.0.1up to date
 regex^1.121.12.3up to date
 semver^1.01.0.27up to date
 serde^1.01.0.228up to date
 similar^2.72.7.0up to date
 tame-index^0.250.26.0out of date
 time ⚠️^0.30.3.47maybe insecure
 toml^1.0.31.0.3+spec-1.1.0up to date
 toml_edit^0.25.30.25.3+spec-1.1.0up to date

Dev dependencies

(5 total, 1 outdated)

CrateRequiredLatestStatus
 assert_fs^1.11.1.3up to date
 cargo-test-support^0.9.00.9.1up to date
 predicates^3.13.1.4up to date
 snapbox^0.6.241.0.0out of date
 trycmd^1.0.01.0.0up to date

Security Vulnerabilities

time: Denial of Service via Stack Exhaustion

RUSTSEC-2026-0009

Impact

When user-provided input is provided to any type that parses with the RFC 2822 format, a denial of service attack via stack exhaustion is possible. The attack relies on formally deprecated and rarely-used features that are part of the RFC 2822 format used in a malicious manner. Ordinary, non-malicious input will never encounter this scenario.

Patches

A limit to the depth of recursion was added in v0.3.47. From this version, an error will be returned rather than exhausting the stack.

Workarounds

Limiting the length of user input is the simplest way to avoid stack exhaustion, as the amount of the stack consumed would be at most a factor of the length of the input.