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 egui-winit

Dependencies

(17 total, 1 outdated, 1 possibly insecure)

CrateRequiredLatestStatus
 accesskit_winit^0.32.00.34.0out of date
 arboard^3.63.6.1up to date
 bytemuck^1.251.25.2up to date
 document-features^0.2.120.2.12up to date
 egui^0.36.20.36.2up to date
 log^0.4.330.4.34up to date
 objc2^0.6.40.6.4up to date
 objc2-foundation^0.3.20.3.2up to date
 objc2-ui-kit^0.3.20.3.2up to date
 profiling^1.01.0.18up to date
 raw-window-handle^0.6.20.6.2up to date
 serde^1.01.0.229up to date
 smithay-clipboard^0.7.20.7.3up to date
 wayland-cursor^0.31.140.31.14up to date
 web-time^1.11.1.0up to date
 webbrowser ⚠️^1.21.2.4maybe insecure
 winit^0.30.130.30.13up to 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.