License enforcement bypass via embedded RSA private key
Published May 28, 2026 · Updated May 28, 2026
Hard-coded key use in the RustFS license verifier before 1.0.0-beta.2 allows attackers to forge arbitrary license tokens. parse_license() decrypts attacker-created token data with the embedded TEST_PRIVATE_KEY instead of authenticating a publisher signature. Exploitation affects license-feature builds and requires a forged token to be supplied through host access, the RUSTFS_LICENSE environment variable, or an administrative API.
Summary
What happened
Hard-coded key use in the RustFS license verifier before 1.0.0-beta.2 allows attackers to forge arbitrary license tokens. parse_license() decrypts attacker-created token data with the embedded TEST_PRIVATE_KEY instead of authenticating a publisher signature. Exploitation affects license-feature builds and requires a forged token to be supplied through host access, the RUSTFS_LICENSE environment variable, or an administrative API.
The record
- CVE
- CVE-2026-45041
- Published
- May 28, 2026
- Updated
- May 28, 2026
- Vendor
- RustFS
- Product
- RustFS
- Classifications
- CWE-321, T1552.004
- Attack vector
- network
- Privileges
- admin
Timeline
How it unfolded
- May 28, 2026CVE publishedPublication date reported by the CVE source.
- May 28, 2026Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=< 1.0.0-beta.2
What conditions does exploitation require?
What is affected?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
- GHSA-923g-jp7v-f97f license-token forging reproductionproof of concept · demonstrated
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo