# RustFS: Missing Post Policy Validation leads to Arbitrary Object Write

Advisory record · `GHSA-w5fh-f8xh-5x3p`

- **Identifiers:** `GHSA-w5fh-f8xh-5x3p` · `CVE-2026-27607`
- **State:** Confirmed
- **Severity:** CVSS 8.1 High
- **Critical:** No
- **Weakness (CWE):** [CWE-20](https://cwe.mitre.org/data/definitions/20.html) · [CWE-863](https://cwe.mitre.org/data/definitions/863.html)
- **Tags:** [Broken access control](https://agentprime.io/advisories/tag/access-control.md) · [CWE-20](https://agentprime.io/advisories/tag/cwe-20.md)
- **Published:** 25 Feb 2026
- **Updated:** 25 Feb 2026
- **Reviewed by a person:** No

Published by the GitHub Advisory Database at 25 Feb 2026, 22:38 UTC. agentprime has not analysed this yet, so whether it affects any app is not known.

## Affected packages

- `rustfs` (crates.io): affected `>=1.0.0-alpha.56, <1.0.0-alpha.83`; fixed in `1.0.0-alpha.83`

## Machine-written summary

Summary written by Claude Haiku from the source advisory. Not reviewed by a person.

> RustFS versions from 1.0.0-alpha.56 before 1.0.0-alpha.83 do not validate presigned POST policy conditions, so content-length-range, starts-with, and Content-Type constraints are not enforced on uploads. An attacker who holds a presigned POST request can upload oversized files, write to arbitrary object keys, and spoof content types. Upgrade rustfs to 1.0.0-alpha.83 or later. The source gives no workaround.

Written 8 Nov 2026.

## Not analysed yet

We haven’t published our analysis of this Advisory yet. Once a person has reviewed it, this page will say what’s vulnerable, what has to be true for your app to be affected, and how to check.

## Severity and exploitation

- 8.1 High, CVSS 3.1: `CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:H/A:H`, from CNA (GitHub_M)

- **CISA KEV:** Not listed.
- **EPSS:** 0.0037, the 31st percentile, on 19 Nov 2026: FIRST’s estimate of the chance of exploitation in the next 30 days.

## Timeline

- 31 Oct 2026, 15:19 UTC: First seen by agentprime
- 31 Oct 2026, 15:19 UTC: [Confirmed by OSV](https://osv.dev/vulnerability/GHSA-w5fh-f8xh-5x3p)

## Sources

- [GitHub Advisory Database: GHSA-w5fh-f8xh-5x3p](https://github.com/advisories/GHSA-w5fh-f8xh-5x3p)
- [OSV: GHSA-w5fh-f8xh-5x3p](https://osv.dev/vulnerability/GHSA-w5fh-f8xh-5x3p)
- <https://github.com/rustfs/rustfs/security/advisories/GHSA-w5fh-f8xh-5x3p>
- <https://nvd.nist.gov/vuln/detail/CVE-2026-27607>
- <https://github.com/rustfs/rustfs>
- <https://github.com/rustfs/rustfs/releases/tag/1.0.0-alpha.83>

Facts on this page come from the GitHub Advisory Database (CC-BY 4.0), OSV and the other sources listed, as published. We don’t reproduce full advisory descriptions, which can contain exploit code.

## Check whether this affects you

A Match means an installed version is in the affected range above. Most don’t affect the app; agentprime hasn’t analysed this one yet.

- With the agentprime MCP server (<https://api.agentprime.io/mcp>), ask your agent to check the project: `check_lockfile` sends a lockfile, `check_packages` a list of installed packages, and both return the Matches and the upgrades that clear them. `get_advisory` returns this record. Setup: <https://agentprime.io/mcp.md>
- In a browser: <https://agentprime.io/check/> reads your lockfile in the browser, never uploading it.
- Whether it touches your code, with file and line: the Claude Code plugin, <https://agentprime.io/plugin.md>
- As JSON: <https://api.agentprime.io/v1/advisories/GHSA-w5fh-f8xh-5x3p>, or `POST https://api.agentprime.io/v1/match` with your packages (<https://agentprime.io/api.md>)

---

The web page: <https://agentprime.io/advisories/GHSA-w5fh-f8xh-5x3p/>. Everything for agents: <https://agentprime.io/llms.txt>.
