- 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 developer has indicated that the crate is unmaintained.
The last release is over three years old (from 2021), the crate depends on the deprecated `async-std` crate and on a very old version of `rustls` for TLS support.
## Possible alternatives
- [reqwest](https://crates.io/crates/reqwest) - [ureq](https://crates.io/crates/ureq)
Is RUSTSEC-2025-0036 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 | surf | >=0.0.0-0 |
no fix listed |
References
-
crates.io
/crates/surf
package
-
rustsec.org
/advisories/RUSTSEC-2025-0036.html
advisory
-
github.com
/http-rs/surf/issues/352
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.