https://cve.radiocsirt.org/rss/recent/all/10 Most recent entries from all 2026-10-14T23:57:26.005178+00:00 Vulnerability-Lookup csirt@opendfir.org python-feedgen Contains only the most 10 recent entries. https://cve.radiocsirt.org/vuln/bdu:2026-05083 bdu:2026-05083 2026-10-14T23:57:26.081544+00:00 bdu:2026-05083 https://cve.radiocsirt.org/vuln/euvd-2026-270720 EUVD-2026-270720 2026-10-14T23:57:26.081585+00:00 EUVD-2026-270720 https://cve.radiocsirt.org/vuln/fkie_cve-2026-27607 fkie_cve-2026-27607 2026-10-14T23:57:26.081599+00:00

RustFS is a distributed object storage system built in Rust. In versions 1.0.0-alpha.56 through 1.0.0-alpha.82, RustFS does not validate policy conditions in presigned POST uploads (PostObject), allowing attackers to bypass content-length-range, starts-with, and Content-Type constraints. This enables unauthorized file uploads exceeding size limits, uploads to arbitrary object keys, and content-type spoofing, potentially leading to storage exhaustion, unauthorized data access, and security bypasses. Version 1.0.0-alpha.83 fixes the issue.

 https://cve.radiocsirt.org/vuln/ghsa-w5fh-f8xh-5x3p GHSA-w5fh-f8xh-5x3p — RustFS: Missing Post Policy Validation leads to Arbitrary Object Write 2026-10-14T23:57:26.081632+00:00

Affected: crates.io: rustfs

### Summary RustFS does not validate policy conditions in presigned POST uploads (PostObject), allowing attackers to bypass content-length-range, starts-with, and Content-Type constraints. This enables unauthorized file uploads exceeding size limits, uploads to arbitrary object keys, and content-type spoofing, potentially leading to storage exhaustion, unauthorized data access, and security bypasses.

### Details When generating presigned POST URLs via the AWS SDK, applications can specify policy conditions to restrict uploads. RustFS accepts these presigned requests but fails to validate the following conditions server-side:

1. `content-length-range` not enforced: The server does not verify that the uploaded file size falls within the specified minimum and maximum bounds. An attacker can upload arbitrarily large files despite restrictions. 2. `starts-with` not enforced: The server does not validate that the object key matches the required prefix. An attacker can modify the key field to upload files to any path in the bucket. 3. `Content-Type` (exact match) not enforced: The server does not verify that the uploaded file's content type matches the policy constraint. An attacker can upload files with any content type.

The vulnerability exists in the PostObject endpoint implementation, where the signed policy conditions are not parsed and validated against the actual upload request.

### Impact Vulnerability Type: Improper Input Validation / Authorization Bypass ##### Who is…