# CVE-2026-73285: Missing authorization in rustfs

> Authenticated users can bypass tag-based policy restrictions in RustFS when OPA authorization is enabled, due to omitted object tag conditions.

- **Severity:** High 7.5 (`CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:U/C:H/I:H/A:H`)
- **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-5w8r-p896-6vq2

## What is CVE-2026-73285?

CVE-2026-73285 is a high-severity missing authorization 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. From 1.0.0-alpha.64 until 1.0.0-rc.1, RustFS external OPA authorization enabled by RUSTFS_POLICY_PLUGIN_URL in crates/iam/src/sys.rs sets PreparedIamAuth.needs_existing_object_tag incorrectly for PreparedIamMode::Opa, causing maybe_merge_object_tag_conditions to omit s3:ExistingObjectTag/* values and allowing authenticated users to bypass tag-based policy restrictions. This issue is fixed in version 1.0.0-rc.1.

Weakness: CWE-863 (Incorrect Authorization)

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


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

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

## Is CVE-2026-73285 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-73285 is a high-severity missing authorization 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-73285 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-73285/ (Markdown: https://insights.sbomify.com/CVE-2026-73285/index.md)
```

## Sources

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

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