Vulnerability in github.com/minio/minio (CVE-2025-31489)
Summary
Vulnerability in github.com/minio/minio (CVE-2025-31489). Risk of unauthorized operations or information disclosure. Exploitable via curl. Mitigation: upgrade to 0.0.0-20250403145552-8c70975283f9 or later.
Original description
The description as published by the source.
MinIO performs incomplete signature validation for unsigned-trailer uploads in github.com/minio/minio
Source: OSV.dev (Open Source Vulnerabilities) NVD GitHub Advisory OSV
Auto-generated summary
Assembled by SecPulse from the source data (CVSS, CWE, affected versions) using templates — no AI involved. Check the original description and references below for exact details.
A vulnerability tracked as CVE-2025-31489 has been found in github.com/minio/minio.
Attackers can target a specific entry point like curl over the network to misuse the product.
Risk of unauthorized operations or information disclosure.
What to do: upgrade github.com/minio/minio to 0.0.0-20250403145552-8c70975283f9 or later.
If unsure, ask your IT team or search "github.com/minio/minio CVE-2025-31489" on the vendor's site.
CVE-2025-31489 (github.com/minio/minio) — CWE-347
Attack surface: curl
Patched: 0.0.0-20250403145552-8c70975283f9 — apply immediately
Workaround: 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
Plan: 1) Audit SBOM/dependencies, 2) Stage→prod upgrade, 3) Add WAF/proxy monitoring on affected endpoints, 4) Hunt IOCs in logs.
Refs: see the GHSA / vendor advisory / patched release linked on this page.
A vulnerability (CWE-347) exists in github.com/minio/minio. Attackers reach the vulnerable code path via curl.
Check the vendor advisory for the affected versions of github.com/minio/minio. Attack surface: curl.
Severity: ?. Risk of unauthorized operations or information disclosure.
Update to 0.0.0-20250403145552-8c70975283f9.
Workaround: 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
Search webserver/proxy logs for unusual request patterns matching this CVE's known IOCs. Run grep -r 'github.com/minio/minio' . against your dependency files (package-lock.json, requirements.txt, go.sum) to find affected services.
Response actions
Concrete steps and command examples for SOC/SRE teams to execute in order
-
1Identify exposure identify
grep -r 'github.com/minio/minio' . | grep -v node_modulesリポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で
github.com/minio/minioを grep し、稼働しているサービス・バージョンを把握する。 -
2Apply temporary workaround mitigate
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`パッチが適用されるまでの応急処置として、Reject requests with
x-amz-content-sha256: STREAMING-UNSIGNED-PAYLOAD-TRAILERfor now at LB layer, ask application users to useSTREAMING-AWS4-HMAC-SHA256-PAYLOAD-TRAILERを実施。回避策の副作用 (機能低下) を確認した上で。 -
3Apply patch patch
Upgrade github.com/minio/minio to 0.0.0-20250403145552-8c70975283f9ステージング環境で 0.0.0-20250403145552-8c70975283f9 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスを含めること。
-
4Post-deployment verification verify
Confirm patched version is live in productionパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番ではアクセスログ・WAF でアラート再発が無いか継続監視。
Affected packages
References
- advisory github.com
- advisory nvd.nist.gov
- package github.com
- patch github.com
- patch github.com