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 maturin

Dependencies

(73 total, 1 outdated, 2 possibly insecure)

CrateRequiredLatestStatus
 anyhow^1.0.801.0.102up to date
 arwen^0.0.50.0.5up to date
 arwen-codesign^0.0.1-alpha.1N/Aup to date
 base64^0.22.00.22.1up to date
 bytesize^2.2.02.3.1up to date
 cargo-config2^0.1.240.1.44up to date
 cargo-cyclonedx=0.5.90.5.9up to date
 cargo-options^0.7.20.7.6up to date
 cargo-xwin^0.22.00.22.0up to date
 cargo-zigbuild^0.22.20.22.3up to date
 cargo_metadata^0.23.10.23.1up to date
 cbindgen^0.29.00.29.2up to date
 cc^1.0.881.2.62up to date
 clap^4.0.04.6.1up to date
 clap_complete_command^0.6.10.6.1up to date
 configparser^3.0.33.1.0up to date
 console^0.16.00.16.3up to date
 dialoguer^0.12.00.12.0up to date
 dirs^6.0.06.0.0up to date
 dunce^1.0.21.0.5up to date
 fat-macho^0.4.100.4.10up to date
 flate2^1.0.181.1.9up to date
 fs-err^3.0.03.3.0up to date
 glob^0.3.00.3.3up to date
 goblin^0.10.00.10.5up to date
 ignore^0.4.200.4.25up to date
 indexmap^2.2.32.14.0up to date
 itertools^0.14.00.14.0up to date
 keyring^3.6.34.0.1out of date
 lddtree^0.5.00.5.0up to date
 memmap2^0.9.90.9.10up to date
 minijinja^2.5.02.19.0up to date
 native-tls^0.2.80.2.18up to date
 normpath^1.1.11.5.1up to date
 once_cell^1.7.21.21.4up to date
 path-slash^0.2.10.2.1up to date
 pep440_rs^0.7.30.7.3up to date
 pep508_rs^0.9.20.9.2up to date
 platform-info^2.0.22.1.0up to date
 pretty_assertions^1.3.01.4.1up to date
 pyo3-introspection^0.280.28.3up to date
 pyproject-toml^0.13.50.13.7up to date
 python-pkginfo^0.6.80.6.8up to date
 reflink-copy^0.1.290.1.29up to date
 regex^1.7.01.12.3up to date
 rustc_version^0.4.00.4.1up to date
 rustflags^0.1.60.1.7up to date
 rustls ⚠️^0.230.23.40maybe insecure
 rustls-pki-types^1.14.01.14.1up to date
 same-file^1.0.61.0.6up to date
 schemars^1.0.41.2.1up to date
 semver^1.0.221.0.28up to date
 serde^1.0.1971.0.228up to date
 serde_json^1.0.1141.0.149up to date
 sha2^0.11.00.11.0up to date
 tar^0.4.450.4.45up to date
 target-lexicon^0.13.30.13.5up to date
 tempfile^3.2.03.27.0up to date
 textwrap^0.16.10.16.2up to date
 thiserror^2.0.32.0.18up to date
 time ⚠️^0.3.170.3.47maybe insecure
 toml^1.1.21.1.2+spec-1.1.0up to date
 toml_edit^0.25.00.25.11+spec-1.1.0up to date
 tracing^0.1.360.1.44up to date
 tracing-subscriber^0.3.200.3.23up to date
 unicode-xid^0.2.40.2.6up to date
 ureq^3.2.03.3.0up to date
 url^2.5.02.5.8up to date
 walkdir^2.5.02.5.0up to date
 which^8.0.08.0.2up to date
 wild^2.1.02.2.1up to date
 xz2^0.10.1.7up to date
 zip^8.1.08.6.0up to date

Dev dependencies

(12 total, 1 outdated, 1 possibly insecure)

CrateRequiredLatestStatus
 expect-test^1.4.11.5.1up to date
 fs4^0.13.11.1.0out of date
 indoc^2.0.32.0.7up to date
 insta^1.34.01.47.2up to date
 nix^0.31.10.31.3up to date
 pretty_assertions^1.3.01.4.1up to date
 rstest^0.26.10.26.1up to date
 rustversion^1.0.91.0.22up to date
 serial_test^3.2.03.4.0up to date
 time ⚠️^0.3.340.3.47maybe insecure
 trycmd^1.2.01.2.0up to date
 which^8.0.08.0.2up to date

Security Vulnerabilities

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.

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.