Categories
CVE-2026-42600 medium CVSS 4.9

Path Traversal in github.com/minio/minio (CVE-2026-42600)

Summary

Path traversal in github.com/minio/minio (CVE-2026-42600). Confidential information can be exposed externally. Exploitable via ReadMultiple.

Original description

The description as published by the source.

MinIO vulnerable to Path Traversal via msgpack Body in ReadMultiple Storage-REST Endpoint in github.com/minio/minio.

NOTE: The source advisory for this report contains additional versions that could not be automatically mapped to standard Go module versions.

(If this is causing false-positive reports from vulnerability scanners, please suggest an edit to the report.)

The additional affected modules and versions are: github.com/minio/minio from v0.0.0-20220724015452 before v0.0.0-20260414213245.

Source: NIST National Vulnerability Database NVD GitHub Advisory

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-2026-42600 has been found in github.com/minio/minio.
Attackers can target a specific entry point like ReadMultiple over the network to misuse the product.
Confidential information can be exposed externally. CVSS score: 4.9/10.
What to do: apply the vendor's official patched release.
If unsure, ask your IT team or search "github.com/minio/minio CVE-2026-42600" on the vendor's site.

CVE-2026-42600 (github.com/minio/minio) — CWE-22 / CVSS v3 4.9
Attack vector: remote (network-reachable) / no user interaction
Attack surface: ReadMultiple
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.

❓ What is the problem

Path traversal (CWE-22) exists in github.com/minio/minio. Attackers reach the vulnerable code path via ReadMultiple.

📍 Affected scope

Check the vendor advisory for the affected versions of github.com/minio/minio. Attack surface: ReadMultiple.

🔥 Severity

Severity: Medium (CVSS 4.9/10). Confidential information can be exposed externally.

🔧 How to fix

Update to the patched release per vendor advisory.

🛡️ Workaround

Until the patch is applied: disable the affected feature, apply WAF rules, or restrict access via network ACLs.

🔍 Detection

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

  1. 1
    Identify 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 し、稼働しているサービス・バージョンを把握する。

  2. 2
    Post-deployment verification verify
    Confirm patched version is live in production

    パッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番ではアクセスログ・WAF でアラート再発が無いか継続監視。

Affected packages

go github.com/minio/minio
[{"type":"SEMVER","events":[{"introduced":"0"}]}]
Bitnami minio
[{"type":"SEMVER","events":[{"introduced":"2022.07.24"}]}]

References

We use cookies for analytics and ad measurement. This setting applies to all Game co., Ltd. sites. Details