# CVE-2026-73284: RustFS: AddServiceAccount Handler Allows Creation of Root-Parent Service Accounts

> An attacker with admin privileges can create root-parent service accounts, leading to privilege escalation and potential full system compromise.

- **Severity:** High 8.8 (`CVSS:3.1/AV:N/AC:L/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-5354-r3w2-34m8

## What is CVE-2026-73284?

CVE-2026-73284 is a high-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. RustFS AddServiceAccount in rustfs/src/admin/handlers/service_account.rs accepts an attacker-controlled target_user after only checking CreateServiceAccountAdminAction, passes it to new_service_account, and prepare_service_account_auth sets is_owner for the resulting root-parent service account. This issue is fixed in version 1.0.0-beta.11.

Weakness: CWE-269 (Improper Privilege Management)

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


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

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

## Is CVE-2026-73284 being exploited?

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

## Fix prompt for AI coding agents

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

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

## Sources

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

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