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

Crate rustimate

Dependencies

(30 total, 14 outdated, 2 insecure)

CrateRequiredLatestStatus
 actix-http ⚠️^1.0.13.22.0insecure
 actix-rt^1.0.02.16.0out of date
 actix-server^1.0.12.10.0out of date
 actix-service^1.0.12.0.3out of date
 actix-session^0.3.00.11.0out of date
 actix-utils^1.0.43.0.2out of date
 actix-web ⚠️^2.0.04.20.0insecure
 actix-web-codegen^0.2.04.6.0out of date
 anyhow^1.0.261.0.104up to date
 app_dirs2^2.0.42.5.5up to date
 arrayvec^0.5.10.7.8out of date
 bincode^1.2.13.0.0out of date
 bitflags^1.2.12.13.2out of date
 clap^2.33.04.6.9out of date
 failure^0.1.60.1.8up to date
 flate2^1.0.131.1.11up to date
 futures^0.3.10.3.34up to date
 http^0.2.01.5.0out of date
 iovec^0.1.40.1.4up to date
 libc^0.2.660.2.191up to date
 nodrop^0.1.140.1.14up to date
 ryu^1.0.21.0.23up to date
 serde_json^1.0.441.0.154up to date
 slog^2.5.22.8.2up to date
 slog-async^2.3.02.8.0up to date
 slog-json^2.3.02.6.1up to date
 slog-term^2.4.22.9.2up to date
 tokio-reactor^0.1.110.1.12up to date
 tokio-sync^0.1.70.1.8up to date
 jni^0.14.00.22.4out of date

Build dependencies

(1 total, all up-to-date)

CrateRequiredLatestStatus
 winres^0.10.1.12up to date

Crate rustimate-controllers

Dependencies

(18 total, 10 outdated, 2 insecure)

CrateRequiredLatestStatus
 actix^0.9.00.13.6out of date
 actix-http ⚠️^1.0.13.22.0insecure
 actix-service^1.0.12.0.3out of date
 actix-session^0.3.00.11.0out of date
 actix-web ⚠️^2.0.04.20.0insecure
 actix-web-actors^2.0.04.3.1+deprecatedout of date
 anyhow^1.0.261.0.104up to date
 bytes^0.5.31.12.2out of date
 chrono^0.4.100.4.45up to date
 derive_more^0.99.22.1.1out of date
 futures^0.3.10.3.34up to date
 maud^0.21.00.27.0out of date
 mime^0.3.140.3.18up to date
 mime_guess^2.0.12.0.5up to date
 serde^1.0.1041.0.229up to date
 serde_json^1.0.441.0.154up to date
 slog^2.5.22.8.2up to date
 uuid^0.8.11.29.3out of date

Crate rustimate-core

Dependencies

(6 total, 3 outdated)

CrateRequiredLatestStatus
 anyhow^1.0.261.0.104up to date
 bincode^1.2.13.0.0out of date
 derive_more^0.99.22.1.1out of date
 serde^1.0.1041.0.229up to date
 serde_json^1.0.441.0.154up to date
 uuid^0.8.11.29.3out of date

Build dependencies

(1 total, 1 outdated)

CrateRequiredLatestStatus
 built^0.3.20.9.0out of date

Crate rustimate-service

Dependencies

(6 total, 1 outdated)

CrateRequiredLatestStatus
 anyhow^1.0.261.0.104up to date
 chrono^0.4.90.4.45up to date
 serde^1.0.1041.0.229up to date
 serde_json^1.0.441.0.154up to date
 slog^2.5.22.8.2up to date
 uuid^0.8.11.29.3out of date

Crate rustimate-templates

Dependencies

(5 total, 2 outdated)

CrateRequiredLatestStatus
 anyhow^1.0.261.0.104up to date
 maud^0.21.00.27.0out of date
 num_cpus^1.11.11.17.0up to date
 serde^1.0.1041.0.229up to date
 uuid^0.8.11.29.3out of date

Crate rustimate-assets

Dependencies

(1 total, 1 outdated, 1 insecure)

CrateRequiredLatestStatus
 rust-embed ⚠️^5.2.08.14.0insecure

Crate rustimate-client

Dependencies

(9 total, 2 outdated)

CrateRequiredLatestStatus
 anyhow^1.0.261.0.104up to date
 console_error_panic_hook^0.1.60.1.7up to date
 instant^0.1.20.1.13up to date
 js-sys^0.3.330.3.107up to date
 maud^0.21.00.27.0out of date
 uuid^0.8.11.29.3out of date
 wasm-bindgen^0.2.560.2.130up to date
 wasm-bindgen-futures^0.4.60.4.80up to date
 web-sys^0.3.330.3.107up to date

Dev dependencies

(1 total, all up-to-date)

CrateRequiredLatestStatus
 wasm-bindgen-test^0.3.60.3.80up to date

Security Vulnerabilities

actix-http: Use-after-free in BodyStream due to lack of pinning

RUSTSEC-2020-0048

Affected versions of this crate did not require the buffer wrapped in BodyStream to be pinned, but treated it as if it had a fixed location in memory. This may result in a use-after-free.

The flaw was corrected by making the trait MessageBody require Unpin and making poll_next() function accept Pin<&mut Self> instead of &mut self.

actix-http: Potential request smuggling capabilities due to lack of input validation

RUSTSEC-2021-0081

Affected versions of this crate did not properly detect invalid requests that could allow HTTP/1 request smuggling (HRS) attacks when running alongside a vulnerable front-end proxy server. This can result in leaked internal and/or user data, including credentials, when the front-end proxy is also vulnerable.

Popular front-end proxies and load balancers already mitigate HRS attacks so it is recommended that they are also kept up to date; check your specific set up. You should upgrade even if the front-end proxy receives exclusively HTTP/2 traffic and connects to the back-end using HTTP/1; several downgrade attacks are known that can also expose HRS vulnerabilities.

rust-embed: RustEmbed generated `get` method allows for directory traversal when reading files from disk

RUSTSEC-2021-0126

When running in debug mode and the debug-embed (off by default) feature is not enabled, the generated get method does not check that the input path is a child of the folder given.

This allows attackers to read arbitrary files in the file system if they have control over the filename given. The following code will print the contents of your /etc/passwd if adjusted with a correct number of ../s depending on where it is run from.

#[derive(rust_embed::RustEmbed)]
#[folder = "src/"]
pub struct Asset;

fn main() {
    let d = Asset::get("../../../etc/passwd").unwrap().data;
    println!("{}", String::from_utf8_lossy(&d));
}

The flaw was corrected by canonicalizing the input filename and ensuring that it starts with the canonicalized folder path.

actix-http: Request smuggling through malformed chunked request trailers

RUSTSEC-2026-0446

The HTTP/1 chunked decoder accepts a bare line feed after the final chunk as the start of a trailer instead of rejecting the malformed request.

When an upstream proxy reuses a connection and either pipelines the requests or does not take steps to validate the chunked stream, the decoder can consume the next request's headers as trailer data. It can then parse that request's body as a new request. An attacker can use this difference in request parsing to bypass access controls enforced by a proxy or web application firewall.

Upgrade to actix-http 3.20.2 or later.

actix-web: Compressed request bodies can exhaust memory before extractor limits apply

RUSTSEC-2026-0447

Body extractors do not pass their size limits to the decompression layer. A small compressed request can therefore cause a large allocation before the extractor rejects the decoded body. A remote attacker can use this to exhaust memory or CPU resources and cause denial of service.

This affects applications that read compressed request bodies with the corresponding compression feature enabled.

Upgrade to actix-web 4.18.2 or later with actix-http 3.20.1 or later. As a workaround, reject compressed request bodies at a reverse proxy or in middleware before body extraction.

actix-http: Unbounded decompression can exhaust memory and CPU resources

RUSTSEC-2026-0448

The encoding::Decoder stream can expand compressed input into a large output buffer before a caller can enforce its body size limit. An attacker who controls a compressed request or response can cause excessive memory allocation and CPU use, resulting in denial of service.

This affects applications that decode untrusted gzip, deflate, Brotli, or Zstandard bodies with the corresponding compression feature enabled.

Upgrade to actix-http 3.20.1 or later and configure Decoder::limit() when using the decoder directly. Actix Web users must also upgrade to actix-web 4.18.2 or later so that extractors pass their limits to the decoder.

actix-http: Large-window Brotli bodies bypass decompression memory limits

RUSTSEC-2026-0455

With the compress-brotli feature enabled, the decoder accepts the non-standard large-window Brotli format. A crafted stream can cause its internal buffer to grow to about 1 GiB before the decoded output reaches the configured size limit. An 850-byte request can cause this allocation, and concurrent requests can exhaust process or host memory.

Actix Web enables Brotli support by default. Applications that read request bodies through Bytes, String, Json, or Form can be affected even when extractor size limits are configured. The allocation occurs before the handler runs, so authentication performed in the handler does not prevent it.

Upgrade to actix-http 3.20.3 or later. As a workaround, reject requests with Content-Encoding: br at a reverse proxy or in middleware before body extraction, or disable the compress-brotli feature throughout the dependency graph.

actix-http: Bare LF in chunked trailers can consume pipelined requests or stall body decoding

RUSTSEC-2026-0552

Affected versions of actix-http skip a bare line feed (LF) inside an HTTP/1.1 chunked trailer instead of rejecting the invalid line ending. Trailer lines must end with a carriage return and line feed (CRLF).

For example, after 0\r\nX\n, the parser continues reading trailer data. If a request follows on the same connection, its head can be consumed as part of the trailer, so that request is never dispatched. If no more bytes arrive, body decoding waits for more input instead of reporting an error. A remote client can trigger these effects without authentication.

Request smuggling additionally requires an HTTP intermediary that forwards the malformed body but uses a different request boundary. The tested HTTP intermediaries either rejected the input or consumed and normalized it before forwarding. Proxy access-control bypass, cache poisoning, and effects on other users were not demonstrated.

Upgrade to actix-http 3.21.1 or later. The fix rejects bare LF and invalid control bytes in trailers before consuming the following request, while preserving partial reads and valid CRLF-terminated trailers.

actix-http: Malformed quoted chunk extensions can end HTTP/1.1 request bodies early

RUSTSEC-2026-0553

Affected versions of actix-http do not track quoted strings when parsing HTTP/1.1 chunk extensions. A carriage return inside a quoted extension value is treated as the end of the chunk-size line, even if the closing quote is missing. For example, 0;x="\r\n\r\n is accepted as the end of a chunked body, and a following pipelined request is dispatched on the same connection.

A remote client can trigger this without authentication. CR and LF are invalid inside HTTP quoted strings, including after a backslash; they must be rejected rather than interpreted as framing or accepted as quoted data.

Request smuggling requires an upstream intermediary that forwards the malformed input while using a different request boundary. Dispatching two requests on the sender's own connection does not by itself demonstrate an authorization bypass or an effect on another user. Proxy bypass, cache poisoning, and cross-user response mixing were not demonstrated by the reproduction.

Upgrade to actix-http 3.21.3 or later. The fix preserves quote and escape state across reads and rejects invalid control bytes inside quoted strings and quoted pairs before consuming the following body or request bytes.

actix-http: Partial requests on keep-alive connections can bypass the request header timeout

RUSTSEC-2026-0554

Affected versions of actix-http apply the request header timeout only to the first request on an HTTP/1 connection. When data arrives for a later request, the dispatcher clears the idle keep-alive timer without starting a request header timer.

A remote client without authentication can complete one request, send one byte of a second request, and leave the connection open indefinitely without sending more data. The same problem occurs when a complete pipelined request is followed by a partial request in the same read. Repeating this can exhaust connection or file-descriptor limits and prevent new connections from being accepted. The effect depends on the server's resource limits and upstream connection controls.

Upgrade to actix-http 3.21.2 or later. The fix applies the configured request header timeout to later partial requests, including those left in the buffer after a complete pipelined request. Additional bytes do not renew the deadline. The timeout covers request headers, not upload bodies.

If an upgrade is not possible, disable HTTP keep-alive, for example with HttpServer::keep_alive(KeepAlive::Disabled) in actix-web. Connection limits can reduce resource use but do not make stalled connections expire.