RUSTSEC-2026-0257
Unix `BROWSER` handling allows browser argument injection
Details
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](https://github.com/dywzju09-blip).
Are you affected?
Enter the version of the package you're using.
Affected packages
0.0.0-0 Fixed in: 1.2.2 Upgrade webbrowser to 1.2.2 or newer (ecosystem crates.io).
References
- https://crates.io/crates/webbrowser [PACKAGE]
- https://rustsec.org/advisories/RUSTSEC-2026-0257.html [ADVISORY]
- https://github.com/amodm/webbrowser-rs/security/advisories/GHSA-2ph8-5cr8-hr33 [ADVISORY]
- https://github.com/amodm/webbrowser-rs/commit/31d1b924885551c0e553909d27c738ca6958a0f3 [WEB]
- https://github.com/amodm/webbrowser-rs/releases/tag/v1.2.2 [WEB]