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 sqlx-sqlite

Dependencies

(20 total, 2 outdated, 1 possibly insecure)

CrateRequiredLatestStatus
 atoi^2.02.0.0up to date
 chrono^0.4.340.4.44up to date
 flume^0.11.00.12.0out of date
 futures-channel^0.3.190.3.32up to date
 futures-core^0.3.190.3.32up to date
 futures-executor^0.3.190.3.32up to date
 futures-intrusive^0.5.00.5.0up to date
 futures-util^0.3.190.3.32up to date
 libsqlite3-sys^0.30.10.36.0out of date
 log^0.4.180.4.29up to date
 percent-encoding^2.1.02.3.2up to date
 regex^1.5.51.12.3up to date
 serde^1.0.1451.0.228up to date
 serde_urlencoded^0.70.7.1up to date
 sqlx-core=0.8.60.8.6up to date
 thiserror^2.0.02.0.18up to date
 time ⚠️^0.3.360.3.47maybe insecure
 tracing^0.1.370.1.44up to date
 url^2.2.22.5.8up to date
 uuid^1.1.21.21.0up to date

Dev dependencies

(1 total, all up-to-date)

CrateRequiredLatestStatus
 sqlx=0.8.60.8.6up 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.