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 xet-runtime

Dependencies

(33 total, 4 outdated, 3 possibly insecure)

CrateRequiredLatestStatus
 anyhow^11.0.102up to date
 async-trait^0.10.1.89up to date
 bytes ⚠️^1.111.11.1maybe insecure
 chrono ⚠️^0.40.4.44maybe insecure
 colored^33.1.1up to date
 console-subscriber^0.50.5.0up to date
 const-str^1.11.1.0up to date
 ctor^0.61.0.5out of date
 dirs^6.06.0.0up to date
 futures^0.30.3.32up to date
 git-version^0.30.3.9up to date
 humantime^2.12.3.0up to date
 konst^0.40.4.3up to date
 lazy_static^1.51.5.0up to date
 libc^0.20.2.186up to date
 more-asserts^0.30.3.1up to date
 oneshot^0.10.2.1out of date
 pin-project^11.1.13up to date
 pyo3^0.260.28.3out of date
 rand^0.100.10.1up to date
 reqwest^0.13.10.13.3up to date
 serde^11.0.228up to date
 serde_json^11.0.149up to date
 shellexpand^3.13.1.2up to date
 sysinfo^0.380.39.2out of date
 thiserror^2.02.0.18up to date
 tokio^1.491.52.3up to date
 tokio-util^0.70.7.18up to date
 tracing^0.10.1.44up to date
 tracing-appender^0.20.2.5up to date
 tracing-subscriber ⚠️^0.30.3.23maybe insecure
 whoami^22.1.2up to date
 winapi^0.30.3.9up to date

Dev dependencies

(5 total, all up-to-date)

CrateRequiredLatestStatus
 futures-util^0.30.3.32up to date
 rand^0.100.10.1up to date
 serial_test^33.4.0up to date
 tempfile^3.253.27.0up to date
 tracing-test^0.20.2.6up to date

Security Vulnerabilities

chrono: Potential segfault in `localtime_r` invocations

RUSTSEC-2020-0159

Impact

Unix-like operating systems may segfault due to dereferencing a dangling pointer in specific circumstances. This requires an environment variable to be set in a different thread than the affected functions. This may occur without the user's knowledge, notably in a third-party library.

Workarounds

No workarounds are known.

References

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.

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.