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 schemars

Dependencies

(18 total, 1 outdated, 2 possibly insecure)

CrateRequiredLatestStatus
 arrayvec^0.70.7.6up to date
 bigdecimal^0.40.4.10up to date
 bytes ⚠️^1.01.11.1maybe insecure
 chrono^0.4.390.4.43up to date
 dyn-clone^1.0.171.0.20up to date
 either^1.31.15.0up to date
 indexmap^2.2.32.13.0up to date
 jiff^0.20.2.19up to date
 ref-cast^1.0.221.0.25up to date
 rust_decimal^1.131.40.0up to date
 schemars_derive=1.2.01.2.1out of date
 semver^1.0.91.0.27up to date
 serde^1.0.1941.0.228up to date
 serde_json^1.0.1271.0.149up to date
 smallvec ⚠️^1.01.15.1maybe insecure
 smol_str^0.3.20.3.5up to date
 url^2.02.5.8up to date
 uuid^1.01.20.0up to date

Dev dependencies

(22 total, 1 outdated, 3 possibly insecure)

CrateRequiredLatestStatus
 arrayvec^0.70.7.6up to date
 bigdecimal^0.40.4.10up to date
 bytes ⚠️^1.01.11.1maybe insecure
 chrono ⚠️^0.40.4.43maybe insecure
 either^1.31.15.0up to date
 garde^0.220.22.1up to date
 indexmap^2.02.13.0up to date
 jiff^0.20.2.19up to date
 jsonschema^0.300.41.0out of date
 pretty_assertions^1.2.11.4.1up to date
 regex^1.10.61.12.3up to date
 rust_decimal^11.40.0up to date
 semver^1.0.91.0.27up to date
 serde^1.01.0.228up to date
 serde_repr^0.1.190.1.20up to date
 smallvec ⚠️^1.01.15.1maybe insecure
 smol_str^0.3.20.3.5up to date
 snapbox^0.6.170.6.24up to date
 trybuild^1.01.0.115up to date
 url^2.02.5.8up to date
 uuid^1.01.20.0up to date
 validator^0.200.20.0up 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

smallvec: Buffer overflow in SmallVec::insert_many

RUSTSEC-2021-0003

A bug in the SmallVec::insert_many method caused it to allocate a buffer that was smaller than needed. It then wrote past the end of the buffer, causing a buffer overflow and memory corruption on the heap.

This bug was only triggered if the iterator passed to insert_many yielded more items than the lower bound returned from its size_hint method.

The flaw was corrected in smallvec 0.6.14 and 1.6.1, by ensuring that additional space is always reserved for each item inserted. The fix also simplified the implementation of insert_many to use less unsafe code, so it is easier to verify its correctness.

Thank you to Yechan Bae (@Qwaz) and the Rust group at Georgia Tech’s SSLab for finding and reporting this bug.

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.