Quick answers
- Is CVE-2026-45040 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-45040 being exploited in the wild.
- How severe is CVE-2026-45040?
- Informational severity, with a CVSS score of 5.3, published 28 May 2026.
- Which products and versions are affected?
- rustfs RustFS < 1.0.0-beta.2.
- Is there a fix for CVE-2026-45040?
- 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 CVE-2026-45040 attacked?
- It is attacked over the network, in a software library.
- Am I affected by CVE-2026-45040?
- Check whether anything you run is named in the advisory. 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
RustFS prior to version 1.0.0-beta.2 contains two distinct logging vulnerabilities that leak credentials when RUST_LOG=debug is set. First, the STS (Security Token Service) handler prints the Credentials struct using the Debug trait, which fails to mask the session_token (JWT). Second, the s3s dependency logs the full HTTP response body for STS API calls, which includes the SecretAccessKey and SessionToken in plaintext XML. An attacker with access to the server logs could use these leaked credentials to perform unauthorized actions. The fix involves implementing a Masked wrapper for sensitive fields in the Credentials struct and redacting the response body content in the s3s service.
Affected products
- rustfs RustFS < 1.0.0-beta.2
Timeline
- 2026-05-09: advisory: GitHub Security Advisory published
- 2026-05-28: disclosed: CVE published to NVD