# CVE-2026-73288: Business logic in rustfs

> Attackers can delete retained objects by triggering metadata read failures, bypassing Object Lock protections in RustFS.

- **Severity:** Medium 6.1 (`CVSS:4.0/AV:N/AC:H/AT:P/PR:L/UI:N/VC:N/VI:H/VA:H/SC:N/SI:N/SA:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 12 Aug 2026
- **Updated:** 12 Aug 2026
- **Also known as:** GHSA-j548-9grx-fh4f

## What is CVE-2026-73288?

CVE-2026-73288 is a medium-severity vulnerability in rustfs, published on 12 Aug 2026. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

RustFS is a distributed object storage system built in Rust. Prior to 1.0.0-rc.1, RustFS Object Lock enforcement in crates/ecstore/src/bucket/object_lock/objectlock_sys.rs lets check_object_lock_for_deletion, delete_prefix, and lifecycle and scanner sweeps treat ConfigNotFound, unreadable .metadata.bin data, or unparseable metadata as no lock configuration, allowing objects under COMPLIANCE retention to be deleted or expired. This issue is fixed in version 1.0.0-rc.1.

Weakness: CWE-754 (Improper Check for Unusual or Exceptional Conditions), CWE-693 (Protection Mechanism Failure)

## Which versions are affected by CVE-2026-73288?


## How do I fix CVE-2026-73288?

No fix has been published for CVE-2026-73288 yet. Limit exposure of the affected software until one is available.

## Is CVE-2026-73288 being exploited?

There is no known exploitation of CVE-2026-73288 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-73288 and fix it if it is affected.

What it is: CVE-2026-73288 is a medium-severity vulnerability in rustfs, published on 12 Aug 2026. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-73288 in the wild and no public exploit code.

Affected product: rustfs. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-73288/ (Markdown: https://insights.sbomify.com/CVE-2026-73288/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-73288
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-73288
- OSV: https://osv.dev/vulnerability/CVE-2026-73288

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-73288/
Summaries are generated and may contain mistakes; the official description above is the record.