Missing Authorization Affecting github.com/minio/minio package, versions >=RELEASE.2024-03-30T09-41-56Z
Threat Intelligence
The probability is the direct output of the EPSS model, and conveys an overall sense of the threat of exploitation in the wild. The percentile measures the EPSS probability relative to all known EPSS scores. Note: This data is updated daily, relying on the latest available EPSS model version. Check out the EPSS documentation for more details.
Do your applications use this vulnerable package?
In a few clicks we can analyze your entire application and see what components are vulnerable in your application, and suggest you quick fixes.
Test your applicationsSnyk Learn
Learn about Missing Authorization vulnerabilities in an interactive lesson.
Start learning- Snyk IDSNYK-GOLANG-GITHUBCOMMINIOMINIO-15813301
- published30 Mar 2026
- disclosed27 Mar 2026
- creditUnknown
Introduced: 27 Mar 2026
CVE-2026-34204 (opens in a new tab)How to fix?
A fix was pushed into the master branch but not yet published.
Overview
github.com/minio/minio is a high performance object storage server compatible with Amazon S3 APIs.
Affected versions of this package are vulnerable to Missing Authorization via the extractMetadataFromMime function. An attacker can make objects permanently unreadable by injecting crafted replication headers in a standard PutObject request, causing the server to map these headers to internal encryption metadata without proper verification. This results in objects being encrypted with non-existent keys, rendering them inaccessible through the S3 API.
Notes
- This is only exploitable if the attacker has
s3:PutObjectpermission on a bucket. - This package (
minio/minio) has been renamed/succeeded byminio/aistor/minioon Quay. The fix is available only in the new package starting from tagRELEASE.2026-03-26T21-24-40Z.
Workaround
This vulnerability can be mitigated by configuring a reverse proxy or load balancer to drop or reject any request containing X-Minio-Replication-Server-Side-Encryption-* headers that do not also include X-Minio-Source-Replication-Request. Additionally, auditing IAM policies to limit s3:PutObject grants to trusted principals can reduce the attack surface.