This project contains known security vulnerabilities. Find detailed information at the bottom.

Crate bollard

Dependencies

(30 total, 10 outdated, 2 insecure)

CrateRequiredLatestStatus
 base64^0.130.23.1out of date
 bollard-stubs=1.42.0-rc.31.41.0up to date
 bytes^11.12.1up to date
 chrono^0.40.4.45up to date
 ct-logs^0.9.00.9.0up to date
 dirs-next^2.02.0.0up to date
 futures-core^0.30.3.34up to date
 futures-util^0.30.3.34up to date
 hex^0.4.20.4.3up to date
 http^0.21.5.0out of date
 hyper^0.141.12.0out of date
 hyper-rustls^0.230.27.10out of date
 hyperlocal^0.8.00.9.1out of date
 log^0.40.4.35up to date
 pin-project-lite^0.2.80.2.17up to date
 rustls ⚠️^0.200.23.46insecure
 rustls-native-certs^0.6.00.8.5out of date
 rustls-pemfile^1.02.2.0out of date
 serde^1.01.0.229up to date
 serde_derive^1.01.0.229up to date
 serde_json^1.01.0.154up to date
 serde_urlencoded^0.70.7.1up to date
 thiserror^1.02.0.21out of date
 time^0.30.3.55up to date
 tokio^1.71.54.1up to date
 tokio-util^0.70.7.20up to date
 url^2.22.5.8up to date
 webpki^0.220.22.4up to date
 webpki-roots ⚠️^0.221.0.12insecure
 winapi^0.3.90.3.9up to date

Dev dependencies

(5 total, 2 outdated)

CrateRequiredLatestStatus
 env_logger^0.90.11.11out of date
 flate2^1.01.1.11up to date
 tar^0.40.4.46up to date
 termion^1.54.0.6out of date
 tokio^1.71.54.1up to date

Security Vulnerabilities

rustls: `rustls::ConnectionCommon::complete_io` could fall into an infinite loop based on network input

RUSTSEC-2024-0336

If a close_notify alert is received during a handshake, complete_io does not terminate.

Callers which do not call complete_io are not affected.

rustls-tokio and rustls-ffi do not call complete_io and are not affected.

rustls::Stream and rustls::StreamOwned types use complete_io and are affected.

rustls: Unauthenticated ServerHello can downgrade later connections to classical key exchange

RUSTSEC-2026-0349

The client recorded the server-selected key exchange group for each server name when processing the ServerHello, before the server was authenticated. This record is used to predict which key share to send in future ClientHellos to that server name.

A network attacker can answer one connection attempt with a ServerHello selecting X25519, and then close the connection. Later ClientHellos for that name carry only an X25519 key share, while supported_groups still lists X25519MLKEM768 first. If the genuine server accepts that share rather than sending a HelloRetryRequest for its preferred hybrid group, the handshake completes with classical-only key exchange and no error. This persists for as long as the entry stays in the client's session store.

The impact is loss of post-quantum confidentiality for affected connections ("harvest now, decrypt later"). There is no key compromise and no authentication bypass.

The following are not affected:

  • connections to servers which send a HelloRetryRequest for their preferred group,
  • clients with resumption disabled (as nothing is stored), and
  • other server names.

This behaviour is discussed in draft-ietf-tls-key-share-prediction, so the practical impact depends largely on server policy.

webpki-roots: Bundled root certificates allow trust in distrusted emSign intermediates

RUSTSEC-2026-0381

Affected versions include emSign ECC Root CA - G3, which can allow certificate paths through distrusted emSign intermediates.

Affected versions may accept certificate paths containing distrusted emSign intermediate public keys. The private keys corresponding to these intermediates are now well known.

Version 1.0.10+ removes this root.

The webpki-roots 0.26.11 compatibility package contains no independent trust store and re-exports the roots from its separately resolved 1.x dependency. That parent dependency must resolve to 1.0.10 or newer; an older parent remains affected by this advisory.