https://cve.radiocsirt.org Contains only the most 10 recent entries. http://www.rssboard.org/rss-specification python-feedgen en Fri, 02 Oct 2026 19:33:24 +0000 https://cve.radiocsirt.org/vuln/bdu:2025-11494 bdu:2025-11494 https://cve.radiocsirt.org/vuln/bdu:2025-11494 https://cve.radiocsirt.org/vuln/bit-minio-2025-31489 <p><strong>Affected:</strong> Bitnami: minio</p> <p>MinIO is a High Performance Object Storage released under GNU Affero General Public License v3.0. The signature component of the authorization may be invalid, which would mean that as a client you can use any arbitrary secret to upload objects given the user already has prior WRITE permissions on the bucket. Prior knowledge of access-key, and bucket name this user might have access to - and an access-key with a WRITE permissions is necessary. However with relevant information in place, uploading random objects to buckets is trivial and easy via curl. This issue is fixed in RELEASE.2025-04-03T14-56-28Z.</p> <p><strong>Affected:</strong> Bitnami: minio</p> <p>MinIO is a High Performance Object Storage released under GNU Affero General Public License v3.0. The signature component of the authorization may be invalid, which would mean that as a client you can use any arbitrary secret to upload objects given the user already has prior WRITE permissions on the bucket. Prior knowledge of access-key, and bucket name this user might have access to - and an access-key with a WRITE permissions is necessary. However with relevant information in place, uploading random objects to buckets is trivial and easy via curl. This issue is fixed in RELEASE.2025-04-03T14-56-28Z.</p> https://cve.radiocsirt.org/vuln/bit-minio-2025-31489 https://cve.radiocsirt.org/vuln/euvd-2026-227055 EUVD-2026-227055 https://cve.radiocsirt.org/vuln/euvd-2026-227055 https://cve.radiocsirt.org/vuln/fkie_cve-2025-31489 <p>MinIO is a High Performance Object Storage released under GNU Affero General Public License v3.0. The signature component of the authorization may be invalid, which would mean that as a client you can use any arbitrary secret to upload objects given the user already has prior WRITE permissions on the bucket. Prior knowledge of access-key, and bucket name this user might have access to - and an access-key with a WRITE permissions is necessary. However with relevant information in place, uploading random objects to buckets is trivial and easy via curl. This issue is fixed in RELEASE.2025-04-03T14-56-28Z.</p> <p>MinIO is a High Performance Object Storage released under GNU Affero General Public License v3.0. The signature component of the authorization may be invalid, which would mean that as a client you can use any arbitrary secret to upload objects given the user already has prior WRITE permissions on the bucket. Prior knowledge of access-key, and bucket name this user might have access to - and an access-key with a WRITE permissions is necessary. However with relevant information in place, uploading random objects to buckets is trivial and easy via curl. This issue is fixed in RELEASE.2025-04-03T14-56-28Z.</p> https://cve.radiocsirt.org/vuln/fkie_cve-2025-31489 https://cve.radiocsirt.org/vuln/ghsa-wg47-6jq2-q2hh <p><strong>Affected:</strong> Go: github.com/minio/minio</p> <p>### Impact This is a high priority vulnerability and users must upgrade ASAP.</p> <p>The signature component of the authorization may be invalid, which would mean that as a client you can use any arbitrary secret to upload objects given the user already has prior WRITE permissions on the bucket,</p> <p>Prior knowledge of access-key, and bucket name this user might have access to - and an access-key with a WRITE permissions is necessary.</p> <p>However with relevant information in place, uploading random objects to buckets is trivial and easy via `curl`</p> <p>### Patches Yes https://github.com/minio/minio/pull/21103</p> <p>### Workarounds Reject requests with `x-amz-content-sha256: STREAMING-UNSIGNED-PAYLOAD-TRAILER` for now at LB layer, ask application users to use `STREAMING-AWS4-HMAC-SHA256-PAYLOAD-TRAILER`</p> <p><strong>Affected:</strong> Go: github.com/minio/minio</p> <p>### Impact This is a high priority vulnerability and users must upgrade ASAP.</p> <p>The signature component of the authorization may be invalid, which would mean that as a client you can use any arbitrary secret to upload objects given the user already has prior WRITE permissions on the bucket,</p> <p>Prior knowledge of access-key, and bucket name this user might have access to - and an access-key with a WRITE permissions is necessary.</p> <p>However with relevant information in place, uploading random objects to buckets is trivial and easy via `curl`</p> <p>### Patches Yes https://github.com/minio/minio/pull/21103</p> <p>### Workarounds Reject requests with `x-amz-content-sha256: STREAMING-UNSIGNED-PAYLOAD-TRAILER` for now at LB layer, ask application users to use `STREAMING-AWS4-HMAC-SHA256-PAYLOAD-TRAILER`</p> https://cve.radiocsirt.org/vuln/ghsa-wg47-6jq2-q2hh https://cve.radiocsirt.org/vuln/opensuse-su-2025:14982-1 <p>govulncheck-vulndb-0.0.20250409T170536-1.1 on GA media</p> <p>govulncheck-vulndb-0.0.20250409T170536-1.1 on GA media</p> https://cve.radiocsirt.org/vuln/opensuse-su-2025:14982-1 https://cve.radiocsirt.org/vuln/wid-sec-w-2025-0714 <p>Ein Angreifer kann eine Schwachstelle in MinIO ausnutzen, um Sicherheitsvorkehrungen zu umgehen.</p> <p>Ein Angreifer kann eine Schwachstelle in MinIO ausnutzen, um Sicherheitsvorkehrungen zu umgehen.</p> https://cve.radiocsirt.org/vuln/wid-sec-w-2025-0714