CVE-2026-73265 rustfs CVE debrief

Who should care

Defenders responsible for RustFS deployments should assess exposure and prioritize upgrading to version 1.0.0-beta.11 if affected. This includes operators, platform administrators, vulnerability management teams, and security teams. They should verify affected versions, assess exposure, and plan for upgrades or mitigations.

Why it matters

CVE-2026-73265 allows unauthorized disclosure of historical object content in RustFS distributed object storage system. Defenders should prioritize verifying exposure and upgrading to version 1.0.0-beta.11 if affected.

• Disclosure of historical object content may lead to unauthorized access to sensitive data.
• Defenders need to verify exposure and upgrade to version 1.0.0-beta.11 if affected.
• The vulnerability requires verification of affected versions and exploitation.

Technical summary

The RustFS distributed object storage system authorizes explicit versionId reads in GetObject, CopyObject sources, and UploadPartCopy sources with s3:GetObject instead of s3:GetObjectVersion. This allows principals without historical-version permission to disclose known historical object content. The vulnerability is fixed in version 1.0.0-beta.11. Affected deployments should assess exposure and prioritize upgrading to the fixed version. The issue requires verification of affected versions and exploitation. Defenders should prioritize verifying exposure and upgrading to version 1.0.0-beta.11 if affected.

Defensive priority

Defenders should prioritize verifying exposure and upgrading to version 1.0.0-beta.11 if affected.

Recommended defensive actions

• Verify if the system uses RustFS and assess exposure to the vulnerability.
• Upgrade to version 1.0.0-beta.11 if affected.
• Monitor for any suspicious activity related to historical object content disclosure.
• Review compensating controls for exposed systems while remediation is scheduled and verified.
• Check relevant monitoring, detection, and logs for exposed assets that need extra review.
• Track exceptions, retest remediated assets, and close the item only after evidence is documented.
• Confirm whether affected product deployments exist in managed environments and assign an owner for follow-up.

Evidence notes

The CVE Program and NVD records provide details on the vulnerability, but do not specify which versions are affected or if exploitation has occurred. Defenders should verify affected versions and assess exposure. The vulnerability is fixed in version 1.0.0-beta.11. There is no evidence of exploitation, but defenders should monitor for suspicious activity related to historical object content disclosure.

Sources and references

Methodology and review provenance

AI-assisted synthesis based on stored public vulnerability evidence. System validation, approval state, and publication status do not by themselves establish human review of this revision. PatchSiren helps prioritize defensive review and does not prove exposure or remediation on any system.