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

(70 total, 6 outdated, 3 possibly insecure)

CrateRequiredLatestStatus
 anyhow^1.0.801.0.102up 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.70.5.9up to date
 cargo-options^0.7.20.7.6up to date
 cargo-xwin^0.19.20.21.4out of date
 cargo-zigbuild^0.22.10.22.1up to date
 cargo_metadata^0.23.10.23.1up to date
 cbindgen^0.29.00.29.2up to date
 cc^1.0.881.2.58up to date
 clap^4.0.04.6.0up 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.13.0up to date
 itertools^0.14.00.14.0up to date
 keyring^2.3.23.6.3out of date
 lddtree^0.4.00.5.0out of date
 memmap2^0.9.90.9.10up to date
 minijinja^2.5.02.18.0up to date
 native-tls^0.2.80.2.18up to date
 normpath^1.1.11.5.0up 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.0.5up to date
 pretty_assertions^1.3.01.4.1up to date
 pyproject-toml^0.13.50.13.7up to date
 python-pkginfo^0.6.80.6.8up to date
 reflink-copy^0.1.280.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.37maybe insecure
 rustls-pki-types^1.14.01.14.0up to date
 same-file^1.0.61.0.6up to date
 schemars^1.0.41.2.1up to date
 semver^1.0.221.0.27up to date
 serde^1.0.1971.0.228up to date
 serde_json^1.0.1141.0.149up to date
 sha2^0.10.30.11.0out of date
 tar ⚠️^0.4.380.4.45maybe insecure
 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^0.9.111.1.0+spec-1.1.0out of date
 toml_edit^0.24.00.25.8+spec-1.1.0out of 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.4.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.10.13.1up to date
 indoc^2.0.32.0.7up to date
 insta^1.34.01.47.0up to date
 nix^0.31.10.31.2up 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^0.15.01.2.0out of 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.

tar: `unpack_in` can chmod arbitrary directories by following symlinks

RUSTSEC-2026-0067

In versions 0.4.44 and below of tar-rs, when unpacking a tar archive, the tar crate's unpack_dir function uses fs::metadata() to check whether a path that already exists is a directory. Because fs::metadata() follows symbolic links, a crafted tarball containing a symlink entry followed by a directory entry with the same name causes the crate to treat the symlink target as a valid existing directory — and subsequently apply chmod to it. This allows an attacker to modify the permissions of arbitrary directories outside the extraction root.

This issue has been fixed in version 0.4.45.

tar: tar-rs incorrectly ignores PAX size headers if header size is nonzero

RUSTSEC-2026-0068

Versions 0.4.44 and below of tar-rs have conditional logic that skips the PAX size header in cases where the base header size is nonzero.

As part of CVE-2025-62518, the astral-tokio-tar project was changed to correctly honor PAX size headers in the case where it was different from the base header. This is almost the inverse of the astral-tokio-tar issue.

Any discrepancy in how tar parsers honor file size can be used to create archives that appear differently when unpacked by different archivers. In this case, the tar-rs (Rust tar) crate is an outlier in checking for the header size — other tar parsers (including e.g. Go archive/tar) unconditionally use the PAX size override. This can affect anything that uses the tar crate to parse archives and expects to have a consistent view with other parsers.

This issue has been fixed in version 0.4.45.