Deps.rs

roadster 0.8.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 roadster

Dependencies

(70 total, 28 outdated, 3 possibly insecure)

CrateRequiredLatestStatus
 aide^0.15.00.15.1up to date
 anyhow^1.0.861.0.103up to date
 async-trait^0.1.810.1.89up to date
 axum^0.8.10.8.9up to date
 axum-core^0.5.00.5.6up to date
 axum-extra^0.10.00.12.6out of date
 bb8^0.9.00.9.1up to date
 bon^3.1.03.9.3up to date
 byte-unit^5.0.05.2.5up to date
 cfg-if^1.0.01.0.4up to date
 chrono^0.4.340.4.45up to date
 clap^4.3.04.6.1up to date
 config^0.15.80.15.25up to date
 const_format^0.2.330.2.36up to date
 convert_case^0.8.00.11.0out of date
 cron^0.15.00.17.0out of date
 derive_more^2.0.02.1.1up to date
 diesel ⚠️^2.2.32.3.11maybe insecure
 diesel-async^0.6.00.9.2out of date
 diesel_migrations^2.2.02.3.2up to date
 dotenvy^0.15.70.15.7up to date
 futures^0.3.310.3.32up to date
 http-body-util^0.1.20.1.4up to date
 insta^1.39.01.48.0up to date
 itertools^0.14.00.15.0out of date
 jsonwebtoken^9.0.010.4.0out of date
 lettre ⚠️^0.11.00.11.22maybe insecure
 log^0.4.270.4.33up to date
 mime^0.3.170.3.17up to date
 mockall^0.13.00.15.0out of date
 num-traits^0.2.180.2.19up to date
 num_cpus^1.13.01.17.0up to date
 opentelemetry^0.30.00.32.0out of date
 opentelemetry-otlp^0.30.00.32.0out of date
 opentelemetry-semantic-conventions^0.30.00.32.1out of date
 opentelemetry_sdk^0.30.00.32.1out of date
 pgmq^0.30.10.33.7out of date
 prost^0.13.20.14.4out of date
 r2d2^0.8.40.8.10up to date
 rand^0.9.00.10.2out of date
 regex^1.11.11.13.0up to date
 reqwest^0.12.80.13.4out of date
 rstest^0.25.00.26.1out of date
 rusty-sidekiq^0.13.10.14.2out of date
 schemars^0.9.01.2.1out of date
 sea-orm^1.1.111.1.20up to date
 sea-orm-migration^1.1.111.1.20up to date
 sendgrid^0.24.00.27.1out of date
 serde^1.0.1941.0.228up to date
 serde_derive^1.0.1941.0.228up to date
 serde_json^1.0.1271.0.150up to date
 serde_with^3.7.03.21.0up to date
 sqlx^0.8.50.9.0out of date
 strum^0.27.00.28.0out of date
 strum_macros^0.27.00.28.0out of date
 testcontainers-modules^0.12.00.15.0out of date
 thiserror^2.0.92.0.18up to date
 tokio^1.43.01.52.3up to date
 tokio-util^0.7.100.7.18up to date
 toml^0.9.21.1.3+spec-1.1.0out of date
 tonic^0.13.00.14.6out of date
 tonic-reflection^0.13.00.14.6out of date
 tower^0.5.20.5.3up to date
 tower-http^0.6.20.7.0out of date
 tracing^0.1.400.1.44up to date
 tracing-opentelemetry^0.31.00.33.0out of date
 tracing-subscriber ⚠️^0.3.170.3.23maybe insecure
 url^2.5.02.5.8up to date
 uuid^1.11.01.23.5up to date
 validator^0.20.00.20.0up to date

Dev dependencies

(6 total, 2 outdated)

CrateRequiredLatestStatus
 cargo-husky^1.5.01.5.0up to date
 insta^1.39.01.48.0up to date
 mockall^0.13.00.15.0out of date
 mockall_double^0.3.10.3.1up to date
 rstest^0.25.00.26.1out of date
 tokio-test^0.4.40.4.5up to date

Security Vulnerabilities

tracing-subscriber: Logging user input may result in poisoning logs with ANSI escape sequences

RUSTSEC-2025-0055

Previous versions of tracing-subscriber were vulnerable to ANSI escape sequence injection attacks. Untrusted user input containing ANSI escape sequences could be injected into terminal output when logged, potentially allowing attackers to:

  • Manipulate terminal title bars
  • Clear screens or modify terminal display
  • Potentially mislead users through terminal manipulation

In isolation, impact is minimal, however security issues have been found in terminal emulators that enabled an attacker to use ANSI escape sequences via logs to exploit vulnerabilities in the terminal emulator.

This was patched in PR #3368 to escape ANSI control characters from user input.

diesel: Command injection in Diesel's implementation of `COPY FROM`/`COPY TO`

RUSTSEC-2026-0136

Diesel allows users to configure various options for PostgreSQL's COPY FROM and COPY TO statements. These configurations are partially provided as strings or characters.

Diesel did not check if any these user-provided options contain a quote character ', which can lead to the injection of additional options in the current COPY FROM/COPY TO statement.

This vulnerability affects any user of COPY FROM/COPY TO that passes user-provided input to any of the affected functions. It can result in modifications of options in the current statement, but it is not possible inject additional statements.

Mitigation

The preferred mitigation to the outlined problem is to update to Diesel version 2.3.8 or newer, which includes fixes for the problem.

Resolution

Diesel now correctly escapes any quotes contained in the provided arguments.

diesel: Possible unaligned data access for implementations of `SqliteAggregate`

RUSTSEC-2026-0137

Diesel allows to register custom aggregate SQL functions for SQLite via the SqliteAggregate interface.

To store an instance of the custom aggregate processor Diesel relied on the sqlite3_aggregate_context function provided by sqlite. This function doesn't provide any guarantees about alignment of the returned allocation, which in turn can lead to problems if the type implementing requires a special alignment, e.g. via a custom #[align(x)] attribute on the type implementing this trait. This affects any user of SqliteAggregate that registers the custom aggregate function with an SQLite connection, while using a non-standard alignment on the type implementing this trait.

Mitigation

The preferred mitigation to the outlined problem is to update to a Diesel version 2.3.8 or newer, which includes fixes for the problem.

Resolution

Diesel now allocates the corresponding memory on Rust side to get a correctly aligned allocation.

lettre: TLS hostname verification disabled when using Boring TLS backend

RUSTSEC-2026-0141

An inverted-boolean bug in lettre's boring-tls integration silently disables TLS hostname verification for callers using the default (strict) configuration. An on-path attacker presenting any chain-valid certificate for any domain can intercept SMTP submission, including PLAIN/LOGIN credentials and message contents, against any lettre user built with the boring-tls feature. Other TLS backends (native-tls, rustls) are unaffected.

The bug was introduced in v0.10.1 and persists through v0.11.21 (latest).