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.
ofm(34 total, 6 outdated, 5 possibly insecure)
| Crate | Required | Latest | Status |
|---|---|---|---|
| tokio ⚠️ | ^1 | 1.53.1 | maybe insecure |
| futures-util | ^0.3 | 0.3.33 | up to date |
| axum | ^0.8 | 0.8.9 | up to date |
| hiqlite | ^0.13 | 0.14.0 | out of date |
| serde | ^1 | 1.0.229 | up to date |
| serde_json | ^1 | 1.0.151 | up to date |
| uuid | ^1 | 1.24.0 | up to date |
| chrono ⚠️ | ^0.4 | 0.4.45 | maybe insecure |
| tracing | ^0.1 | 0.1.44 | up to date |
| tracing-subscriber ⚠️ | ^0.3 | 0.3.23 | maybe insecure |
| tower-http | ^0.7 | 0.7.0 | up to date |
| clap | ^4 | 4.6.4 | up to date |
| reqwest | ^0.12 | 0.13.4 | out of date |
| async-trait | ^0.1 | 0.1.91 | up to date |
| serde_yaml | ^0.9 | 0.9.34+deprecated | up to date |
| tempfile | ^3 | 3.27.0 | up to date |
| thiserror | ^2 | 2.0.19 | up to date |
| tokio-stream | ^0.1 | 0.1.19 | up to date |
| jsonwebtoken | ^9 | 10.4.0 | out of date |
| sha2 | ^0.10 | 0.11.0 | out of date |
| base64 | ^0.22 | 0.22.1 | up to date |
| url | ^2 | 2.5.8 | up to date |
| tower | ^0.5 | 0.5.3 | up to date |
| rand | ^0.8 | 0.10.2 | out of date |
| cookie | ^0.18 | 0.18.1 | up to date |
| hex | ^0.4 | 0.4.3 | up to date |
| axum-extra | ^0.10 | 0.12.6 | out of date |
| leptos | ^0.8 | 0.8.20 | up to date |
| leptos_styling | ^0.3 | 0.3.1 | up to date |
| bytes ⚠️ | ^1 | 1.12.1 | maybe insecure |
| http-body-util | ^0.1 | 0.1.4 | up to date |
| pulldown-cmark | ^0.13 | 0.13.4 | up to date |
| ammonia ⚠️ | ^4 | 4.1.4 | maybe insecure |
| html-escape | ^0.2 | 0.2.14 | up to date |
chrono: Potential segfault in `localtime_r` invocationsUnix-like operating systems may segfault due to dereferencing a dangling pointer in specific circumstances. This requires an environment variable to be set in a different thread than the affected functions. This may occur without the user's knowledge, notably in a third-party library.
No workarounds are known.
tokio: reject_remote_clients Configuration corruptionOn 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.
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);
tracing-subscriber: Logging user input may result in poisoning logs with ANSI escape sequencesPrevious versions of tracing-subscriber were vulnerable to ANSI escape sequence injection attacks. Untrusted user input containing ANSI escape sequences could be injected into terminal output when logged, potentially allowing attackers to:
In isolation, impact is minimal, however security issues have been found in terminal emulators that enabled an attacker to use ANSI escape sequences via logs to exploit vulnerabilities in the terminal emulator.
This was patched in PR #3368 to escape ANSI control characters from user input.
bytes: Integer overflow in `BytesMut::reserve`In the unique reclaim path of BytesMut::reserve, the condition
if v_capacity >= new_cap + offset
uses an unchecked addition. When new_cap + offset overflows usize in release builds, this condition may incorrectly pass, causing self.cap to be set to a value that exceeds the actual allocated capacity. Subsequent APIs such as spare_capacity_mut() then trust this corrupted cap value and may create out-of-bounds slices, leading to UB.
This behavior is observable in release builds (integer overflow wraps), whereas debug builds panic due to overflow checks.
use bytes::*;
fn main() {
let mut a = BytesMut::from(&b"hello world"[..]);
let mut b = a.split_off(5);
// Ensure b becomes the unique owner of the backing storage
drop(a);
// Trigger overflow in new_cap + offset inside reserve
b.reserve(usize::MAX - 6);
// This call relies on the corrupted cap and may cause UB & HBO
b.put_u8(b'h');
}
Users of BytesMut::reserve are only affected if integer overflow checks are configured to wrap. When integer overflow is configured to panic, this issue does not apply.
ammonia: mXSS in ammonia via MathML `annotation-xml` encoding stripIf a certain set of MathML tags are enabled, an attacker can inject arbitrary JavaScript code into the user's browser.
The annotation-xml tag has slightly different behavior than the other "integration point"
tags in MathML and SVG, but ammonia didn't handle it, so it didn't correctly
strip the namespace-incompatible tags.
This vulnerability only has an effect when the math and annotation-xml tags
are both enabled, but the encoding attribute is disabled, because it relies
on the following sequence of steps:
<math><annotation-xml encoding="text/html"><gadget></annotation-xml></math>.<gadget> is parsed as HTML.<math><annotation-xml><gadget></annotation-xml></math>. Because the encoding attribute is gone, <gadget> is now parsed as MathML.Additionally, the gadget can only be written using a tag that is parsed as raw text in HTML. These elements are:
Applications that do not explicitly allow any of these tags should not be affected, since none are allowed by default.
Discovered by: ivan0912 (YesWeHack) · Date: 2026-06-29 · Found via local differential analysis and source review of ammonia's sanitisation pipeline; no third-party systems were tested.