no cvss
—
- cvss
- —
- not scored
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- —
- no score, EPSS covers CVEs only
- public exploits
- 0
- none known
Summary
The tide crate is unmaintained, and all versions are affected.
The closest maintained alternative might be [trillium](https://crates.io/crates/trillium).
See [this issue](https://github.com/http-rs/tide/issues/922) for more context.
Is RUSTSEC-2026-0170 in your dependencies? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.
Check with FencerAffected packages
| ecosystem | package | affected | fixed in |
|---|---|---|---|
| crates.io | tide | >=0.0.0-0 |
no fix listed |
References
-
crates.io
/crates/tide
package
-
rustsec.org
/advisories/RUSTSEC-2026-0170.html
advisory
-
github.com
/http-rs/tide/issues/922
report
Sources
Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.