Deps.rs

re_ui 0.22.1

[![dependency status](https://deps.rs/crate/re_ui/0.22.1/status.svg)](https://deps.rs/crate/re_ui/0.22.1)

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 re_ui

Dependencies

(25 total, 16 outdated, 2 possibly insecure)

CrateRequiredLatestStatus
 ahash^0.80.8.12up to date
 arrow^53.458.1.0out of date
 eframe^0.31.00.34.1out of date
 egui^0.31.00.34.1out of date
 egui_commonmark^0.20.00.23.0out of date
 egui_extras^0.31.00.34.1out of date
 egui_tiles^0.12.00.15.0out of date
 getrandom^0.20.4.2out of date
 itertools^0.130.14.0out of date
 once_cell^1.171.21.4up to date
 parking_lot^0.120.12.5up to date
 re_arrow_util^0.22.10.31.1out of date
 re_entity_db^0.22.10.31.1out of date
 re_format^0.22.10.31.1out of date
 re_log^0.22.10.31.1out of date
 re_log_types^0.22.10.31.1out of date
 re_tracing^0.22.10.31.1out of date
 serde^11.0.228up to date
 serde_json^11.0.149up to date
 smallvec ⚠️^1.01.15.1maybe insecure
 strum^0.260.28.0out of date
 strum_macros^0.260.28.0out of date
 sublime_fuzzy^0.70.7.0up to date
 time ⚠️^0.3.360.3.47maybe insecure
 url^2.32.5.8up to date

Dev dependencies

(3 total, 3 outdated)

CrateRequiredLatestStatus
 egui_kittest^0.31.00.34.1out of date
 rand^0.80.10.0out of date
 re_types^0.22.10.27.3out of date

Security Vulnerabilities

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.

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.