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 eventure

Dependencies

(12 total, 2 outdated)

CrateRequiredLatestStatus
 regex^1.10.41.12.3up to date
 uuid^1.8.01.22.0up to date
 colored^2.1.03.1.1out of date
 log^0.4.210.4.29up to date
 rdkafka^0.36.20.39.0out of date
 clap^4.5.44.6.0up to date
 serde_json^1.0.1161.0.149up to date
 serde^1.0.2001.0.228up to date
 smol^2.0.02.0.2up to date
 futures^0.3.300.3.32up to date
 typetag^0.2.160.2.21up to date
 mopa^0.2.20.2.2up to date

Crate examples

Dependencies

(10 total, 1 outdated, 1 possibly insecure)

CrateRequiredLatestStatus
 uuid^1.8.01.22.0up to date
 colored^2.1.03.1.1out of date
 simple_logger^5.0.05.2.0up to date
 log^0.4.210.4.29up to date
 serde^1.0.2001.0.228up to date
 serde_json^1.0.1161.0.149up to date
 time ⚠️^0.3.360.3.47maybe insecure
 typetag^0.2.160.2.21up to date
 mopa^0.2.20.2.2up to date
 mop^0.5.00.5.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.