This project contains known security vulnerabilities. Find detailed information at the bottom.

Crate tolstack

Dependencies

(21 total, 12 outdated, 1 insecure)

CrateRequiredLatestStatus
 rand_distr^0.4.00.6.0out of date
 rand^0.8.10.10.3out of date
 statistical^1.0.01.0.0up to date
 num^0.3.10.4.3out of date
 serde^1.0.1061.0.229up to date
 serde_derive^1.0.1061.0.229up to date
 serde_json^1.0.511.0.151up to date
 toml^0.5.61.1.8+spec-1.1.0out of date
 csv^1.1.31.4.0up to date
 iced^0.2.00.14.0out of date
 iced_native^0.3.00.10.3out of date
 iced_graphics^0.1.00.14.0out of date
 async-std^1.01.13.2up to date
 directories-next^2.0.02.0.0up to date
 open^1.4.05.4.4out of date
 nfd^0.0.40.0.4up to date
 notify^5.0.0-pre.28.2.0out of date
 colored^2.0.03.1.1out of date
 chrono^0.40.4.45up to date
 webbrowser ⚠️^0.5.51.2.4insecure
 image^0.23.120.25.10out of date

Security Vulnerabilities

webbrowser: Unix `BROWSER` handling allows browser argument injection

RUSTSEC-2026-0257

On Unix platforms handled by src/unix.rs, affected versions substitute the caller-supplied URL into the BROWSER environment-variable template before tokenizing the resulting string with split_ascii_whitespace(). If an application passes an attacker-controlled non-HTTP(S) URL whose parsed form retains spaces and the effective BROWSER template contains %s, text that should remain within one URL argument becomes additional browser arguments.

The issue was reproduced with Chromium by injecting --remote-debugging-port, which exposed a local DevTools endpoint, and --proxy-server, which redirected browser traffic through an attacker-controlled proxy. The available arguments and resulting impact depend on the browser launched by the affected application.

Version 1.2.2 fixes the issue by tokenizing the BROWSER template before substituting the URL, preserving the URL as part of a single argument. Users should upgrade to version 1.2.2 or later. Applications that only need HTTP(S) URLs can also enable the crate's hardened feature as defense in depth.

This issue was reported by @dywzju09-blip.