Authenticated object disclosure via missing FTP authorization
Published Jun 26, 2026 · Updated Jun 26, 2026
Missing authorization in RustFS 1.0.0-alpha.1 through 1.0.0-beta.8 allows remote authenticated users to read arbitrary objects over FTP. The get() and metadata() handlers in the FTP driver call the storage backend without the authorize_operation() gate used by protected handlers. Exploitation requires valid IAM credentials and an enabled FTP or FTPS frontend, after which denied users can read and inspect objects but cannot modify them through the proven path.
Summary
What happened
Missing authorization in RustFS 1.0.0-alpha.1 through 1.0.0-beta.8 allows remote authenticated users to read arbitrary objects over FTP. The get() and metadata() handlers in the FTP driver call the storage backend without the authorize_operation() gate used by protected handlers. Exploitation requires valid IAM credentials and an enabled FTP or FTPS frontend, after which denied users can read and inspect objects but cannot modify them through the proven path.
The record
- CVE
- CVE-2026-55189
- Published
- Jun 26, 2026
- Updated
- Jun 26, 2026
- Vendor
- RustFS
- Product
- RustFS
- Classifications
- CWE-862, CWE-863, T1530
- Attack vector
- network
- Privileges
- authenticated
Timeline
How it unfolded
- Jun 26, 2026CVE publishedPublication date reported by the CVE source.
- Jun 26, 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-alpha.1, <= 1.0.0-beta.8
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
No public exploit references are available in this record.
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