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 zola

Dependencies

(10 total, 1 outdated, 1 possibly insecure)

CrateRequiredLatestStatus
 clap^44.6.0up to date
 clap_complete^44.6.0up to date
 axum^0.80.8.8up to date
 tokio ⚠️^1.0.11.51.0maybe insecure
 notify-debouncer-full^0.60.7.0out of date
 ctrlc^33.5.2up to date
 open^55.3.3up to date
 mime_guess^2.02.0.5up to date
 mime^0.3.160.3.17up to date
 env_logger^0.110.11.10up to date

Dev dependencies

(1 total, all up-to-date)

CrateRequiredLatestStatus
 same-file^11.0.6up to date

Build dependencies

(5 total, 1 outdated, 1 possibly insecure)

CrateRequiredLatestStatus
 clap^44.6.0up to date
 clap_complete^44.6.0up to date
 clap_mangen^0.2.310.3.0out of date
 tauri-winres^0.30.3.5up to date
 time ⚠️^0.30.3.47maybe insecure

Security Vulnerabilities

tokio: reject_remote_clients Configuration corruption

RUSTSEC-2023-0001

On Windows, configuring a named pipe server with pipe_mode will force ServerOptions::reject_remote_clients as false.

This drops any intended explicit configuration for the reject_remote_clients that may have been set as true previously.

The default setting of reject_remote_clients is normally true meaning the default is also overridden as false.

Workarounds

Ensure that pipe_mode is set first after initializing a ServerOptions. For example:

let mut opts = ServerOptions::new();
opts.pipe_mode(PipeMode::Message);
opts.reject_remote_clients(true);

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.