Historical object disclosure via wrong IAM action
Published Aug 12, 2026 · Updated Aug 12, 2026
Incorrect authorization in RustFS before 1.0.0-beta.11 allows remote authenticated users to read known historical object content. The access layer authorizes explicit versionId reads in GetObject, CopyObject sources, and UploadPartCopy sources as s3:GetObject rather than s3:GetObjectVersion. Exploitation requires a known version identifier and a principal allowed to read the current object but not historical versions; the confirmed consequence is historical-content disclosure.
Summary
What happened
Incorrect authorization in RustFS before 1.0.0-beta.11 allows remote authenticated users to read known historical object content. The access layer authorizes explicit versionId reads in GetObject, CopyObject sources, and UploadPartCopy sources as s3:GetObject rather than s3:GetObjectVersion. Exploitation requires a known version identifier and a principal allowed to read the current object but not historical versions; the confirmed consequence is historical-content disclosure.
The record
- CVE
- CVE-2026-73265
- Published
- Aug 12, 2026
- Updated
- Aug 12, 2026
- Vendor
- RustFS
- Product
- RustFS
- Classifications
- CWE-863, CWE-862, T1213
- Attack vector
- network
- Privileges
- authenticated
Timeline
How it unfolded
- Aug 12, 2026CVE publishedPublication date reported by the CVE source.
- Aug 12, 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.11
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