High severity · published Apr 22, 2026
CVE-2026-40344
MinIO has an Unauthenticated Object Write via Missing Signature Verification in Unsigned-Trailer Uploads
8.2
CVSS
0.4%
EPSS
No
On KEV
Description
MinIO is a high-performance object storage system. Starting in RELEASE.2023-05-18T00-05-36Z and prior to RELEASE.2026-04-11T03-20-12Z, an authentication bypass vulnerability in MinIO's Snowball auto-extract handler (`PutObjectExtractHandler`) allows any user who knows a valid access key to write arbitrary objects to any bucket without knowing the secret key or providing a valid cryptographic signature. Any MinIO deployment is impacted. The attack requires only a valid access key (the well-known default `minioadmin`, or any key with WRITE permission on a bucket) and a target bucket name. When `authTypeStreamingUnsignedTrailer` support was added, the new auth type was handled in `PutObjectHandler` and `PutObjectPartHandler` but was never added to `PutObjectExtractHandler`. The snowball auto-extract handler's `switch rAuthType` block has no case for `authTypeStreamingUnsignedTrailer`, so execution falls through with zero signature verification. The `isPutActionAllowed` call before the switch extracts the access key and checks IAM permissions, but does not verify the cryptographic signature. An attacker sends a PUT request with `X-Amz-Content-Sha256: STREAMING-UNSIGNED-PAYLOAD-TRAILER`, `X-Amz-Meta-Snowball-Auto-Extract: true`, and an `Authorization` header containing a valid access key with a completely fabricated signature. The request is accepted and the tar payload is extracted into the bucket. Users of the open-source minio/minio project should upgrade to MinIO AIStor RELEASE.2026-04-11T03-20-12Z or later. If upgrading is not immediately possible, block unsigned-trailer requests at the load balancer. Reject any request containing X-Amz-Content-Sha256: STREAMING-UNSIGNED-PAYLOAD-TRAILER at the reverse proxy or WAF layer. Clients can use STREAMING-AWS4-HMAC-SHA256-PAYLOAD-TRAILER (the signed variant) instead. Alternatively, restrict WRITE permissions. Limit s3:PutObject grants to trusted principals. While this reduces the attack surface, it does not eliminate the vulnerability since any user with WRITE permission can exploit it with only their access key.
CVSS vector
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:L
Attack vector
Network
Complexity
Low
Privileges
None
User interaction
None
Confidentiality
None
Integrity
High
Availability
Low
Scope
Unchanged
Exploitation
Is it being used?
Exploit prediction (EPSS)0.4% · higher than 36% of CVEs
Exploited in the wildNo evidence yet
CISA KEVNot listed
Ransomware campaign useNot known
Affected products
Which versions
MI
minio · minio
>= RELEASE.2023-05-18T00-05-36Z, < RELEASE.2026-04-11T03-20-12Z · source: vendor, NVD
References
NVD
https://nvd.nist.gov/vuln/detail/CVE-2026-40344
CVE.org
https://www.cve.org/CVERecord?id=CVE-2026-40344
Patch
https://github.com/minio/minio/commit/76913a9fd5c6e5c2dbd4e8c7faf56ed9e9e24091
Issue Tracking
https://github.com/minio/minio/pull/16484
Patch
https://github.com/minio/minio/security/advisories/GHSA-9c4q-hq6p-c237
More from minio
8.8
CVE-2023-28434
MinIO is vulnerable to privilege escalation on Linux/MacOS
7.5
CVE-2023-28432
Minio Information Disclosure in Cluster Deployment
9.8
CVE-2026-33322
MinIO: JWT Algorithm Confusion in OIDC Authentication
9.3
CVE-2024-55949
Privilege escalation in IAM import API in MinIO
8.8
CVE-2024-24747
MinIO unsafe default: Access keys inherit `admin` of root user, allowing privilege escalation
