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 reveal-yaml

Dependencies

(12 total, 5 outdated, 1 possibly insecure)

CrateRequiredLatestStatus
 actix^0.130.13.5up to date
 actix-files^0.60.7.0out of date
 actix-web^44.15.0up to date
 actix-web-actors^44.3.1+deprecatedup to date
 binstall-zip^0.60.6.4up to date
 clap^44.6.7up to date
 pulldown-cmark^0.90.13.4out of date
 reqwest^0.110.13.5out of date
 serde^11.0.229up to date
 temp-dir^0.10.2.0out of date
 webbrowser ⚠️^0.81.2.4out of date
 yaml-peg^11.0.9up 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.