Quick answers
- Is This vulnerability exploited in the wild?
- No. Junglewise Threat Intelligence has no report of This vulnerability being exploited in the wild.
- How severe is This vulnerability?
- Informational severity, published 10 November 2026.
- Which products and versions are affected?
- lwd-uri-util (crates.io) 0.0.0-0 and higher; 8 versions published 2026-11-09, SEMVER:introduced=0.0.0-0.
- Is there a fix for This vulnerability?
- No fixed version is recorded yet. Check the vendor's advisory in the references below. If you run it, Junglewise drafts a mitigation that fits your setup and applies it once you approve, with senior security engineers behind it.
- How is This vulnerability attacked?
- It is attacked over the network, in a software library.
- Am I affected?
- Check whether you run lwd-uri-util (crates.io) at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.
Technical details
A malicious Rust crate was published to crates.io with functionality to exfiltrate SSH keys, AWS credentials, and other environmental metadata and secrets at build time. The attack requires a developer to include the compromised crate as a dependency in their project build. Eight versions of the crate were published on 2026-11-09 before being removed from the package registry; no evidence of actual exploitation in the wild was identified.
Affected products
- crates.io lwd-uri-util 0.0.0-0 and higher; 8 versions published 2026-11-09
Timeline
- 2026-11-10: disclosed: Vulnerability reported to RustSec
- 2026-11-09: other: 8 malicious versions published to crates.io
- 2026-11-09: other: Malicious crate removed from crates.io approximately 12 hours after publication