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 yawc

Dependencies

(29 total, 4 outdated, 2 possibly insecure)

CrateRequiredLatestStatus
 axum-core^0.50.5.6up to date
 base64^0.220.23.1out of date
 bytes ⚠️^1.111.12.1maybe insecure
 flate2^11.1.10up to date
 futures^0.30.3.34up to date
 getrandom^0.20.4.3out of date
 http^11.5.0up to date
 http-body-util^0.10.1.5up to date
 hyper^11.11.1up to date
 hyper-util^0.10.1.20up to date
 js-sys^0.30.3.105up to date
 log^0.40.4.34up to date
 nom^88.0.0up to date
 pin-project^11.1.13up to date
 rand^0.80.10.2out of date
 reqwest^0.130.13.5up to date
 serde^11.0.229up to date
 sha1^0.100.11.0out of date
 simdutf8^0.10.1.5up to date
 smol^2.0.22.0.2up to date
 thiserror^22.0.20up to date
 tokio ⚠️^11.53.1maybe insecure
 tokio-rustls^0.260.26.5up to date
 tokio-util^0.70.7.19up to date
 url^22.5.8up to date
 wasm-bindgen^0.20.2.128up to date
 wasm-bindgen-futures^0.40.4.78up to date
 web-sys^0.30.3.105up to date
 webpki-roots^11.0.9up to date

Dev dependencies

(20 total, 2 outdated, 2 possibly insecure)

CrateRequiredLatestStatus
 anyhow^11.0.104up to date
 axum^0.80.8.9up to date
 console-subscriber^0.5.00.5.0up to date
 criterion^0.50.8.2out of date
 futures-rustls^0.260.26.0up to date
 hyper^1.71.11.1up to date
 log^0.40.4.34up to date
 rand^0.80.10.2out of date
 reqwest^0.130.13.5up to date
 rustls ⚠️^0.230.23.44maybe insecure
 rustls-native-certs^0.80.8.4up to date
 rustls-pki-types^1.01.15.1up to date
 serde^11.0.229up to date
 serde_json^11.0.151up to date
 simple_logger^55.2.0up to date
 smol^2.0.22.0.2up to date
 tokio ⚠️^11.53.1maybe insecure
 tokio-stream^0.10.1.19up to date
 wasm-bindgen-test^0.30.3.78up to date
 webpki-roots^11.0.9up to date

Security Vulnerabilities

tokio: reject_remote_clients Configuration corruption

RUSTSEC-2023-0001

On Windows, configuring a named pipe server with pipe_mode will force ServerOptions::reject_remote_clients as false.

This drops any intended explicit configuration for the reject_remote_clients that may have been set as true previously.

The default setting of reject_remote_clients is normally true meaning the default is also overridden as false.

Workarounds

Ensure that pipe_mode is set first after initializing a ServerOptions. For example:

let mut opts = ServerOptions::new();
opts.pipe_mode(PipeMode::Message);
opts.reject_remote_clients(true);

rustls: rustls network-reachable panic in `Acceptor::accept`

RUSTSEC-2024-0399

A bug introduced in rustls 0.23.13 leads to a panic if the received TLS ClientHello is fragmented. Only servers that use rustls::server::Acceptor::accept() are affected.

Servers that use tokio-rustls's LazyConfigAcceptor API are affected.

Servers that use tokio-rustls's TlsAcceptor API are not affected.

Servers that use rustls-ffi's rustls_acceptor_accept API are affected.

bytes: Integer overflow in `BytesMut::reserve`

RUSTSEC-2026-0007

In the unique reclaim path of BytesMut::reserve, the condition

if v_capacity >= new_cap + offset

uses an unchecked addition. When new_cap + offset overflows usize in release builds, this condition may incorrectly pass, causing self.cap to be set to a value that exceeds the actual allocated capacity. Subsequent APIs such as spare_capacity_mut() then trust this corrupted cap value and may create out-of-bounds slices, leading to UB.

This behavior is observable in release builds (integer overflow wraps), whereas debug builds panic due to overflow checks.

PoC

use bytes::*;

fn main() {
    let mut a = BytesMut::from(&b"hello world"[..]);
    let mut b = a.split_off(5);

    // Ensure b becomes the unique owner of the backing storage
    drop(a);

    // Trigger overflow in new_cap + offset inside reserve
    b.reserve(usize::MAX - 6);

    // This call relies on the corrupted cap and may cause UB & HBO
    b.put_u8(b'h');
}

Workarounds

Users of BytesMut::reserve are only affected if integer overflow checks are configured to wrap. When integer overflow is configured to panic, this issue does not apply.