CVE-2026-73265

RustFS: Version-specific object reads authorize the non-version action

Published Aug 12, 2026 CVSS 3.1 · 6.5 Medium EPSS < 1% KEV · Not listed
Description
RustFS is a distributed object storage system built in Rust. RustFS authorizes explicit versionId reads in GetObject, CopyObject sources, and UploadPartCopy sources with s3:GetObject instead of s3:GetObjectVersion, allowing principals without historical-version permission to disclose known historical object content. This issue is fixed in version 1.0.0-beta.11.

Analysis

AI-generated

Technical impact

RustFS permits users who have permission to read current objects to read historical object versions by using the standard GetObject, CopyObject, and UploadPartCopy operations. These operations are authorized with s3:GetObject instead of s3:GetObjectVersion, meaning that principals lacking explicit version-read rights can obtain known historical object content. The vulnerability therefore allows a confidentiality breach of any previously stored objects that a user can reference by version ID, exposing sensitive data that was not intended to be publicly accessible.

Affected Systems

The rustfs storage system is affected for all releases prior to version 1.0.0‑beta.11. The issue is fixed in that release and later versions, so any rustfs instance running an older version is vulnerable.

Risk and Exploitability

The CVSS score of 6.5 indicates a medium severity vulnerability, and the EPSS score is unavailable. RustFS is not listed in the CISA KEV catalog. Exploitation is straightforward: an attacker who can use the S3 API to provide a versionId (e.g., via a GetObject request) and has s3:GetObject permission can retrieve historical object data without needing separate version‑specific permissions. Because the attack vector is the normal S3 interface and does not require advanced privileges, the likelihood of exploitation is reasonably high compared to other medium‑severity issues. Monitoring for anomalous version reads or applying tighter IAM controls can reduce the risk until a fix is applied.

Remediation

No solution or workaround provided in the CVE record.

OpenCVE Recommended Actions

  • Upgrade rustfs to version 1.0.0‑beta.11 or later to apply the fix for the incorrect authorization logic.
  • After upgrading, review IAM policies to ensure that only users needing historical access are granted s3:GetObjectVersion, while those who require only current object reads are denied this permission on historical objects.
  • Audit existing policies or create a deny rule that blocks s3:GetObject on stored objects where the requester does not have s3:GetObjectVersion to prevent accidental exposure of historic data.

Generated by OpenCVE AI on August 13, 2026 at 00:40 UTC.

Tracking

Sign in to view the affected projects.

Advisories

No advisories available
History
Type Values Removed Values Added
Metrics ssvc

{'options': {'Automatable': 'no', 'Exploitation': 'none', 'Technical Impact': 'partial'}, 'version': '2.0.3'}

Type Values Removed Values Added
First Time appeared Rustfs
Rustfs rustfs
Vendors & Products Rustfs
Rustfs rustfs
Type Values Removed Values Added
Description RustFS is a distributed object storage system built in Rust. RustFS authorizes explicit versionId reads in GetObject, CopyObject sources, and UploadPartCopy sources with s3:GetObject instead of s3:GetObjectVersion, allowing principals without historical-version permission to disclose known historical object content. This issue is fixed in version 1.0.0-beta.11.
Title RustFS: Version-specific object reads authorize the non-version action
Weaknesses CWE-862
CWE-863
References
Metrics cvssV3_1

{'score': 6.5, 'vector': 'CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N'}

Weaknesses

Sources

Status
PUBLISHED
Assigner
GitHub_M
Published
Updated
Aug 13, 2026, 4:20 PM
Reserved
Aug 11, 2026, 5:18 PM
Status
Deferred
Published
Aug 12, 2026, 3:18 PM
Modified
Sep 9, 2026, 8:55 PM