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 tauri-utils


(30 total, 4 outdated, 1 possibly insecure)

 aes-gcm^ to date
 brotli^36.0.0out of date
 cargo_metadata^ to date
 ctor^ to date
 dunce^11.0.4up to date
 getrandom^ to date
 glob^ to date
 html5ever^ of date
 infer^ of date
 json-patch^ of date
 json5^ to date
 kuchikiki^ to date
 log^ to date
 memchr^22.7.4up to date
 phf^ to date
 proc-macro2^11.0.86up to date
 quote^11.0.36up to date
 regex ⚠️^11.10.5maybe insecure
 schemars^ to date
 semver^11.0.23up to date
 serde^11.0.204up to date
 serde_json^11.0.120up to date
 serde_with^33.9.0up to date
 serialize-to-javascript= to date
 swift-rs^ to date
 thiserror^11.0.63up to date
 toml^ to date
 url^22.5.2up to date
 urlpattern^ to date
 walkdir^22.5.0up to date

Security Vulnerabilities

regex: Regexes with large repetitions on empty sub-expressions take a very long time to parse


The Rust Security Response WG was notified that the regex crate did not properly limit the complexity of the regular expressions (regex) it parses. An attacker could use this security issue to perform a denial of service, by sending a specially crafted regex to a service accepting untrusted regexes. No known vulnerability is present when parsing untrusted input with trusted regexes.

This issue has been assigned CVE-2022-24713. The severity of this vulnerability is "high" when the regex crate is used to parse untrusted regexes. Other uses of the regex crate are not affected by this vulnerability.


The regex crate features built-in mitigations to prevent denial of service attacks caused by untrusted regexes, or untrusted input matched by trusted regexes. Those (tunable) mitigations already provide sane defaults to prevent attacks. This guarantee is documented and it's considered part of the crate's API.

Unfortunately a bug was discovered in the mitigations designed to prevent untrusted regexes to take an arbitrary amount of time during parsing, and it's possible to craft regexes that bypass such mitigations. This makes it possible to perform denial of service attacks by sending specially crafted regexes to services accepting user-controlled, untrusted regexes.

Affected versions

All versions of the regex crate before or equal to 1.5.4 are affected by this issue. The fix is include starting from regex 1.5.5.


We recommend everyone accepting user-controlled regexes to upgrade immediately to the latest version of the regex crate.

Unfortunately there is no fixed set of problematic regexes, as there are practically infinite regexes that could be crafted to exploit this vulnerability. Because of this, we do not recommend denying known problematic regexes.


We want to thank Addison Crump for responsibly disclosing this to us according to the Rust security policy, and for helping review the fix.

We also want to thank Andrew Gallant for developing the fix, and Pietro Albini for coordinating the disclosure and writing this advisory.