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 open62541

Dependencies

(14 total, 1 possibly insecure)

CrateRequiredLatestStatus
 futures-channel^0.3.300.3.32up to date
 futures-core^0.3.300.3.32up to date
 log^0.4.200.4.33up to date
 open62541-sys^0.5.40.5.5up to date
 parking_lot^0.12.40.12.5up to date
 paste^1.0.141.0.15up to date
 serde^1.0.1941.0.228up to date
 serde_json^1.0.1111.0.150up to date
 thiserror^2.0.32.0.18up to date
 time ⚠️^0.3.380.3.53maybe insecure
 tokio^1.38.21.52.3up to date
 uuid^1.16.01.23.4up to date
 x509-certificate^0.25.00.25.0up to date
 zeroize^1.8.11.9.0up to date

Dev dependencies

(7 total, 2 outdated, 1 possibly insecure)

CrateRequiredLatestStatus
 anyhow^1.0.791.0.103up to date
 env_logger^0.11.10.11.11up to date
 futures^0.3.300.3.32up to date
 itertools^0.14.00.15.0out of date
 rand^0.9.20.10.2out of date
 time ⚠️^0.3.380.3.53maybe insecure
 tokio^1.35.11.52.3up 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.