Quick answers
- Is CVE-2026-45044 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-45044 being exploited in the wild.
- How severe is CVE-2026-45044?
- Informational severity, with a CVSS score of 8.8, published 28 May 2026.
- Which products and versions are affected?
- RustFS RustFS < 1.0.0-beta.2.
- Is there a fix for CVE-2026-45044?
- 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-45044 attacked?
- It is attacked over the network, in a hosted service.
- Am I affected by CVE-2026-45044?
- 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
A missing authentication check (CWE-306) in 'rustfs/src/admin/router.rs' explicitly whitelists the '/profile/cpu' and '/profile/memory' endpoints from the authentication layer. On glibc-based systems, invoking the CPU profiling handler triggers a fixed 60-second profiling operation via 'dump_cpu_pprof_for', which can be abused by unauthenticated network attackers to cause a Denial of Service (DoS) through CPU exhaustion. Furthermore, the handler in 'rustfs/src/admin/handlers/profile.rs' returns the server's absolute filesystem path in the HTTP response body, leading to information disclosure. The vulnerability is confirmed to bypass 401/403 checks even on builds where the profiling fails (returning 500 instead). The issue is resolved in version 1.0.0-beta.2.
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