Deps.rs

rustsec 0.32.0

[![dependency status](https://deps.rs/crate/rustsec/0.32.0/status.svg)](https://deps.rs/crate/rustsec/0.32.0)

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 rustsec

Dependencies

(18 total, 2 outdated, 1 possibly insecure)

CrateRequiredLatestStatus
 auditable-info^0.100.10.0up to date
 auditable-serde^0.90.9.0up to date
 binfarce^0.20.2.1up to date
 cargo-lock^1111.0.1up to date
 cvss^2.22.2.0up to date
 fs-err^33.3.0up to date
 gix^0.780.79.0out of date
 home^0.50.5.12up to date
 once_cell^1.15.01.21.3up to date
 platforms^33.8.0up to date
 quitters^0.1.00.1.0up to date
 semver^1.0.231.0.27up to date
 serde^11.0.228up to date
 tame-index^0.260.26.0up to date
 thiserror^22.0.18up to date
 time ⚠️^0.30.3.47maybe insecure
 toml^0.91.0.2+spec-1.1.0out of date
 url^22.5.8up to date

Dev dependencies

(3 total, all up-to-date)

CrateRequiredLatestStatus
 once_cell^1.15.01.21.3up to date
 serde_json^11.0.149up to date
 tempfile^33.25.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.