Deps.rs

tantivy 0.19.2

[![dependency status](https://deps.rs/crate/tantivy/0.19.2/status.svg)](https://deps.rs/crate/tantivy/0.19.2)

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 tantivy

Dependencies

(48 total, 20 outdated, 2 possibly insecure)

CrateRequiredLatestStatus
 aho-corasick^0.71.1.5out of date
 arc-swap^1.5.01.9.2up to date
 async-trait^0.1.530.1.92up to date
 base64^0.13.00.23.1out of date
 bitpacking^0.8.40.9.3out of date
 brotli^3.3.49.0.0out of date
 byteorder^1.4.31.5.0up to date
 census^0.4.00.4.2up to date
 ciborium^0.20.2.2up to date
 tantivy-common^0.40.11.0out of date
 crc32fast^1.3.21.5.2up to date
 crossbeam-channel^0.5.40.5.17up to date
 downcast-rs^1.2.02.0.2out of date
 fail^0.5.00.5.1up to date
 fastdivide^0.4.00.4.2up to date
 fastfield_codecs^0.3.10.3.1up to date
 fs2^0.4.30.4.3up to date
 htmlescape^0.3.10.3.1up to date
 itertools^0.10.30.15.0out of date
 levenshtein_automata^0.2.10.2.1up to date
 log^0.4.160.4.34up to date
 lru^0.7.50.18.4out of date
 lz4_flex ⚠️^0.9.20.14.0out of date
 measure_time^0.8.20.9.0out of date
 memmap2^0.5.30.9.11out of date
 murmurhash32^0.2.00.4.0out of date
 num_cpus^1.13.11.17.0up to date
 once_cell^1.10.01.21.4up to date
 oneshot^0.1.50.2.1out of date
 ownedbytes^0.40.9.0out of date
 rayon^1.5.21.12.0up to date
 regex^1.5.51.13.1up to date
 rust-stemmers^1.2.01.2.0up to date
 rustc-hash^1.1.02.1.3out of date
 serde^1.0.1361.0.229up to date
 serde_json^1.0.791.0.151up to date
 smallvec^1.8.01.16.1up to date
 snap^1.0.51.1.2up to date
 stable_deref_trait^1.2.01.2.1up to date
 tantivy-bitpacker^0.30.10.0out of date
 tantivy-fst^0.4.00.5.0out of date
 tantivy-query-grammar^0.19.00.26.0out of date
 tempfile^3.3.03.27.0up to date
 thiserror^1.0.302.0.20out of date
 time ⚠️^0.3.100.3.55maybe insecure
 uuid^1.0.01.26.1up to date
 winapi^0.3.90.3.9up to date
 zstd^0.120.14.0out of date

Dev dependencies

(11 total, 4 outdated)

CrateRequiredLatestStatus
 criterion^0.40.8.2out of date
 env_logger^0.10.00.11.11out of date
 fail^0.5.00.5.1up to date
 futures^0.3.210.3.34up to date
 maplit^1.0.21.0.2up to date
 matches^0.1.90.1.10up to date
 pprof^0.11.00.15.0out of date
 pretty_assertions^1.2.11.4.1up to date
 proptest^1.0.01.11.0up to date
 rand^0.8.50.10.2out of date
 test-log^0.2.100.2.21up to date

Security Vulnerabilities

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.

lz4_flex: Decompressing invalid data can leak information from uninitialized memory or reused output buffer

RUSTSEC-2026-0041

Decompressing invalid LZ4 data with the block API can leak data from uninitialized memory, or leak content from previous decompression operations when reusing an output buffer.

The LZ4 block format defines a "match copy operation" which duplicates previously written data or data from a user-supplied dict. The position of that data is defined by an offset. lz4_flex did not properly validate offset values, causing it to copy data from outside the initialized portion of the output buffer.

Two scenarios are affected:

  • Decompressing with the unsafe implementation (safe-decode feature flag disabled, which is the default): can leak content of uninitialized memory as part of the decompressed result.
  • Decompressing into a reused, user-supplied output buffer (also affects safe-decode): can leak the previous contents of the output buffer as part of the decompressed result.

Only the block-based APIs are affected. All frame APIs are unaffected.

The flaw was corrected in versions 0.11.6 and 0.12.1 by properly validating offset values during decompression.

If upgrading is not possible, the issue can be mitigated by zeroing the output buffer before each call to the affected functions and enabling the safe-decode feature flag.