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

Crate taxy

Dependencies

(71 total, 23 outdated, 1 insecure)

CrateRequiredLatestStatus
 anyhow^1.0.711.0.104up to date
 arc-swap^1.6.01.9.5up to date
 argon2^0.5.00.6.0out of date
 async-trait^0.1.710.1.92up to date
 axum^0.8.10.8.9up to date
 axum-extra^0.10.00.12.6out of date
 axum-server^0.7.10.9.2out of date
 backoff^0.4.00.4.0up to date
 base64^0.22.10.23.1out of date
 bytes^1.8.01.12.1up to date
 clap^4.3.114.6.7up to date
 dashmap^6.0.16.2.1up to date
 directories^6.0.06.0.0up to date
 flate2^1.0.261.1.11up to date
 fnv^1.0.71.0.7up to date
 futures^0.3.280.3.34up to date
 globwalk^0.9.10.9.1up to date
 h3^0.0.70.0.8out of date
 h3-quinn^0.0.90.0.10out of date
 hex^0.4.30.4.3up to date
 hickory-resolver ⚠️^0.24.10.26.3insecure
 http-body-util^0.1.20.1.5up to date
 humantime-serde^1.1.11.1.1up to date
 hyper^1.4.11.12.0up to date
 hyper-util^0.1.100.1.21up to date
 include_dir^0.7.30.7.4up to date
 indexmap^2.0.02.14.2up to date
 instant-acme^0.7.10.8.5out of date
 log^0.4.190.4.35up to date
 mime_guess^2.0.42.0.5up to date
 network-interface^2.0.02.0.5up to date
 once_cell^1.18.01.21.4up to date
 percent-encoding^2.3.02.3.2up to date
 phf^0.11.20.14.0out of date
 pin-project-lite^0.2.100.2.17up to date
 pkcs8^0.10.20.11.0out of date
 quinn^0.11.60.11.12up to date
 rand^0.8.50.10.4out of date
 rcgen^0.13.00.14.10out of date
 rpassword^7.2.07.5.5up to date
 rustls-native-certs^0.8.00.8.5up to date
 rustls-pemfile^2.0.02.2.0up to date
 sailfish^0.9.00.11.9out of date
 serde^1.0.1711.0.229up to date
 serde_default^0.2.00.2.0up to date
 serde_derive^1.0.1711.0.229up to date
 serde_json^1.0.1021.0.154up to date
 serde_qs^0.14.01.1.3out of date
 sha2^0.10.70.11.1out of date
 shellexpand^3.1.03.1.2up to date
 socket2^0.5.90.6.5out of date
 sqlx^0.8.20.9.0out of date
 tar^0.4.380.4.46up to date
 taxy-api^0.2.20.2.2up to date
 thiserror^2.0.02.0.21up to date
 time^0.3.360.3.55up to date
 tokio^1.29.11.54.1up to date
 tokio-rustls^0.26.00.26.6up to date
 tokio-stream^0.1.140.1.19up to date
 toml^0.8.81.2.1+spec-1.1.0out of date
 toml_edit^0.22.90.25.19+spec-1.1.0out of date
 totp-rs^5.1.06.0.0out of date
 tower-service^0.3.30.3.3up to date
 tower_governor^0.6.00.8.0out of date
 tracing^0.1.370.1.44up to date
 tracing-appender^0.2.20.2.5up to date
 tracing-subscriber^0.3.170.3.23up to date
 url^2.4.02.5.8up to date
 utoipa^5.2.06.0.0out of date
 webpki^0.22.40.22.4up to date
 x509-parser^0.17.00.18.1out of date

Dev dependencies

(4 total, 2 outdated)

CrateRequiredLatestStatus
 mockito^1.6.11.7.2up to date
 net2^0.2.390.2.39up to date
 reqwest^0.12.10.13.5out of date
 tokio-tungstenite^0.26.00.30.0out of date

Security Vulnerabilities

hickory-resolver: `Resolver::lookup` and `lookup_ip` returned records that failed DNSSEC validation

RUSTSEC-2026-0514

With DNSSEC validation enabled, Resolver::lookup() and Resolver::lookup_ip() returned Ok with the records even when validation found the response bogus. The result was only visible in each record's proof status, which callers had to inspect themselves.

Applications that enable validation and treat a successful lookup as validated data would therefore accept forged or tampered answers from anyone who can answer or modify their DNS traffic.

From 0.26.2 a lookup whose records are bogus fails with a "DNSSEC validation failed" error (DnsError::DnssecBogus), the error is not retried, and the hickory-server forwarder answers SERVFAIL for it.