Deps.rs

ratatui 0.26.3

[![dependency status](https://deps.rs/crate/ratatui/0.26.3/status.svg)](https://deps.rs/crate/ratatui/0.26.3)

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 ratatui

Dependencies

(17 total, 9 outdated, 1 possibly insecure)

CrateRequiredLatestStatus
 bitflags^2.32.13.0up to date
 cassowary^0.30.3.0up to date
 compact_str^0.7.10.9.1out of date
 crossterm^0.270.29.0out of date
 document-features^0.2.70.2.12up to date
 itertools^0.120.14.0out of date
 lru^0.12.00.18.0out of date
 paste^1.0.21.0.15up to date
 serde^11.0.228up to date
 stability^0.2.00.2.1up to date
 strum^0.260.28.0out of date
 termion^3.04.0.6out of date
 termwiz^0.22.00.23.3out of date
 time ⚠️^0.3.110.3.49maybe insecure
 unicode-segmentation^1.101.13.3up to date
 unicode-truncate^12.0.1out of date
 unicode-width^0.10.2.2out of date

Dev dependencies

(15 total, 4 outdated)

CrateRequiredLatestStatus
 anyhow^1.0.711.0.102up to date
 argh^0.1.120.1.19up to date
 better-panic^0.3.00.3.0up to date
 color-eyre^0.6.20.6.5up to date
 criterion^0.5.10.8.2out of date
 derive_builder^0.20.00.20.2up to date
 fakeit^1.11.4.1up to date
 font8x8^0.3.10.3.1up to date
 indoc^22.0.7up to date
 palette^0.7.30.7.6up to date
 pretty_assertions^1.4.01.4.1up to date
 rand^0.8.50.10.1out of date
 rand_chacha^0.3.10.10.0out of date
 rstest^0.19.00.26.1out of date
 serde_json^1.0.1091.0.150up 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.