Quick answers
- Is CVE-2026-45041 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-45041 being exploited in the wild.
- How severe is CVE-2026-45041?
- Informational severity, with a CVSS score of 8.7, published 28 May 2026.
- Which products and versions are affected?
- RustFS RustFS < 1.0.0-beta.2.
- Is there a fix for CVE-2026-45041?
- A patch was published on 2026-05-28: Fixed in version 1.0.0-beta.2 Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
- How is CVE-2026-45041 attacked?
- It is attacked over the network, in a software library.
- Am I affected by CVE-2026-45041?
- 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 includes a hard-coded 2048-bit RSA private key (TEST_PRIVATE_KEY) in 'crates/appauth/src/token.rs'. This key is used in production by the 'parse_license()' function to verify license tokens. The implementation incorrectly uses RSA PKCS#1 v1.5 decryption as a substitute for a digital signature scheme; because the private key is embedded in the source and binaries, any attacker can encrypt a crafted JSON payload to 'mint' a valid license. This bypasses the license-enforcement mechanism when the 'license' Cargo feature is enabled. The vulnerability is addressed in version 1.0.0-beta.2 by removing the embedded key and moving toward a proper signature-based verification model.
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
- 2026-05-28: patched: Fixed in version 1.0.0-beta.2