https://cve.radiocsirt.org Contains only the most 10 recent entries. http://www.rssboard.org/rss-specification python-feedgen en Sun, 04 Oct 2026 05:53:44 +0000 https://cve.radiocsirt.org/vuln/bdu:2025-13411 bdu:2025-13411 https://cve.radiocsirt.org/vuln/bdu:2025-13411 https://cve.radiocsirt.org/vuln/bit-minio-2025-62506 <p><strong>Affected:</strong> Bitnami: minio</p> <p>MinIO is a high-performance object storage system. In all versions prior to RELEASE.2025-10-15T17-29-55Z, a privilege escalation vulnerability allows service accounts and STS (Security Token Service) accounts with restricted session policies to bypass their inline policy restrictions when performing operations on their own account, specifically when creating new service accounts for the same user. The vulnerability exists in the IAM policy validation logic where the code incorrectly relied on the DenyOnly argument when validating session policies for restricted accounts. When a session policy is present, the system should validate that the action is allowed by the session policy, not just that it is not denied. An attacker with valid credentials for a restricted service or STS account can create a new service account for itself without policy restrictions, resulting in a new service account with full parent privileges instead of being restricted by the inline policy. This allows the attacker to access buckets and objects beyond their intended restrictions and modify, delete, or create objects outside their authorized scope. The vulnerability is fixed in version RELEASE.2025-10-15T17-29-55Z.</p> <p><strong>Affected:</strong> Bitnami: minio</p> <p>MinIO is a high-performance object storage system. In all versions prior to RELEASE.2025-10-15T17-29-55Z, a privilege escalation vulnerability allows service accounts and STS (Security Token Service) accounts with restricted session policies to bypass their inline policy restrictions when performing operations on their own account, specifically when creating new service accounts for the same user. The vulnerability exists in the IAM policy validation logic where the code incorrectly relied on the DenyOnly argument when validating session policies for restricted accounts. When a session policy is present, the system should validate that the action is allowed by the session policy, not just that it is not denied. An attacker with valid credentials for a restricted service or STS account can create a new service account for itself without policy restrictions, resulting in a new service account with full parent privileges instead of being restricted by the inline policy. This allows the attacker to access buckets and objects beyond their intended restrictions and modify, delete, or create objects outside their authorized scope. The vulnerability is fixed in version RELEASE.2025-10-15T17-29-55Z.</p> https://cve.radiocsirt.org/vuln/bit-minio-2025-62506 https://cve.radiocsirt.org/vuln/euvd-2026-256747 EUVD-2026-256747 https://cve.radiocsirt.org/vuln/euvd-2026-256747 https://cve.radiocsirt.org/vuln/fkie_cve-2025-62506 <p>MinIO is a high-performance object storage system. In all versions prior to RELEASE.2025-10-15T17-29-55Z, a privilege escalation vulnerability allows service accounts and STS (Security Token Service) accounts with restricted session policies to bypass their inline policy restrictions when performing operations on their own account, specifically when creating new service accounts for the same user. The vulnerability exists in the IAM policy validation logic where the code incorrectly relied on the DenyOnly argument when validating session policies for restricted accounts. When a session policy is present, the system should validate that the action is allowed by the session policy, not just that it is not denied. An attacker with valid credentials for a restricted service or STS account can create a new service account for itself without policy restrictions, resulting in a new service account with full parent privileges instead of being restricted by the inline policy. This allows the attacker to access buckets and objects beyond their intended restrictions and modify, delete, or create objects outside their authorized scope. The vulnerability is fixed in version RELEASE.2025-10-15T17-29-55Z.</p> <p>MinIO is a high-performance object storage system. In all versions prior to RELEASE.2025-10-15T17-29-55Z, a privilege escalation vulnerability allows service accounts and STS (Security Token Service) accounts with restricted session policies to bypass their inline policy restrictions when performing operations on their own account, specifically when creating new service accounts for the same user. The vulnerability exists in the IAM policy validation logic where the code incorrectly relied on the DenyOnly argument when validating session policies for restricted accounts. When a session policy is present, the system should validate that the action is allowed by the session policy, not just that it is not denied. An attacker with valid credentials for a restricted service or STS account can create a new service account for itself without policy restrictions, resulting in a new service account with full parent privileges instead of being restricted by the inline policy. This allows the attacker to access buckets and objects beyond their intended restrictions and modify, delete, or create objects outside their authorized scope. The vulnerability is fixed in version RELEASE.2025-10-15T17-29-55Z.</p> https://cve.radiocsirt.org/vuln/fkie_cve-2025-62506 https://cve.radiocsirt.org/vuln/ghsa-jjjj-jwhf-8rgr <p><strong>Affected:</strong> Go: github.com/minio/minio</p> <p>### Summary A privilege escalation vulnerability allows service accounts and STS (Security Token Service) accounts with restricted session policies to bypass their inline policy restrictions when performing &#34;own&#34; account operations, specifically when creating new service accounts for the same user.</p> <p>### Details The vulnerability exists in the IAM policy validation logic in `cmd/iam.go`. When validating session policies for restricted accounts performing operations on their own account (such as creating service accounts), the code incorrectly relied on the `DenyOnly` argument.</p> <p>The `DenyOnly` flag is used to allow accounts to perform actions related to their own account by only checking if the action is explicitly denied. However, when a session policy (sub-policy) is present, the system should validate that the action is actually **allowed** by the session policy, not just that it isn&#39;t denied.</p> <p>### Attack Scenario 1. An administrator creates a service account or STS account with a restricted inline policy (e.g., access only to bucket1 and bucket2) 2. The restricted account attempts to create a new service account for itself without specifying any policy restrictions 3. Due to the bypass, the new service account is created with full parent privileges instead of being restricted by the inline policy 4. The attacker now has escalated privileges beyond the intended restrictions</p> <p>### Impact</p> <p>**Attack Complexity**: LOW - Exploitation requires only valid credentials for…</p> <p><strong>Affected:</strong> Go: github.com/minio/minio</p> <p>### Summary A privilege escalation vulnerability allows service accounts and STS (Security Token Service) accounts with restricted session policies to bypass their inline policy restrictions when performing &#34;own&#34; account operations, specifically when creating new service accounts for the same user.</p> <p>### Details The vulnerability exists in the IAM policy validation logic in `cmd/iam.go`. When validating session policies for restricted accounts performing operations on their own account (such as creating service accounts), the code incorrectly relied on the `DenyOnly` argument.</p> <p>The `DenyOnly` flag is used to allow accounts to perform actions related to their own account by only checking if the action is explicitly denied. However, when a session policy (sub-policy) is present, the system should validate that the action is actually **allowed** by the session policy, not just that it isn&#39;t denied.</p> <p>### Attack Scenario 1. An administrator creates a service account or STS account with a restricted inline policy (e.g., access only to bucket1 and bucket2) 2. The restricted account attempts to create a new service account for itself without specifying any policy restrictions 3. Due to the bypass, the new service account is created with full parent privileges instead of being restricted by the inline policy 4. The attacker now has escalated privileges beyond the intended restrictions</p> <p>### Impact</p> <p>**Attack Complexity**: LOW - Exploitation requires only valid credentials for…</p> https://cve.radiocsirt.org/vuln/ghsa-jjjj-jwhf-8rgr https://cve.radiocsirt.org/vuln/opensuse-su-2025:15710-1 <p>govulncheck-vulndb-0.0.20251105T184115-1.1 on GA media</p> <p>govulncheck-vulndb-0.0.20251105T184115-1.1 on GA media</p> https://cve.radiocsirt.org/vuln/opensuse-su-2025:15710-1 https://cve.radiocsirt.org/vuln/wid-sec-w-2025-2331 <p>Ein entfernter, authentisierter Angreifer kann eine Schwachstelle in MinIO ausnutzen, um seine Privilegien zu erhöhen.</p> <p>Ein entfernter, authentisierter Angreifer kann eine Schwachstelle in MinIO ausnutzen, um seine Privilegien zu erhöhen.</p> https://cve.radiocsirt.org/vuln/wid-sec-w-2025-2331