Advisory record · GHSA-xh8f-g2qw-gcm7

MinIO vulnerable to Path Traversal via msgpack Body in `ReadMultiple` Storage-REST Endpoint

CVSS 6.9 MediumEPSS 0.087 · 95th percentile

Published by the GitHub Advisory Database at 5 May 2026, 20:05 UTC. agentprime has not analysed this yet, so whether it affects any app is not known.

PackageEcosystemAffectedFixed in
github.com/minio/minioGo>=0.0.0-20220724015452, <0.0.0-202604142132450.0.0-20260414213245
Identifiers
GHSA-xh8f-g2qw-gcm7 · CVE-2026-42600 · GO-2026-5757
Weakness (CWE)
CWE-22
Published
5 May 2026
Updated
8 Oct 2026

Machine-written summary

Summary written by Claude Haiku from the source advisory. Not reviewed by a person.

MinIO (github.com/minio/minio) versions from 0.0.0-20220724015452 before 0.0.0-20260414213245 have a path traversal flaw in the ReadMultiple storage-REST endpoint, which is present only in distributed deployments. An attacker holding the cluster root JWT, which requires the root credential, can read files outside the configured drive roots, limited only by the MinIO process's user ID. Upgrade to version 0.0.0-20260414213245 or later; if that is not possible, rotate and tightly restrict the root credential and avoid running the container as root.

Written 1 Nov 2026.

Not analysed yet

We haven’t published our analysis of this Advisory yet. Once a person has reviewed it, this page will say what’s vulnerable, what has to be true for your app to be affected, and how to check.

Severity and exploitation

ScoreRatingCVSSVectorSource
6.9 Medium 4.0 CVSS:4.0/AV:N/AC:L/AT:N/PR:H/UI:N/VC:H/VI:N/VA:N/SC:N/SI:N/SA:N CNA (GitHub_M)
  • CISA KEV Not listed.
  • EPSS 0.087, the 95th percentile, on 16 Nov 2026: FIRST’s estimate of the chance of exploitation in the next 30 days.

Timeline

  1. 11 May 2026, 22:22 UTC Confirmed by NVD
  2. 31 Oct 2026, 14:12 UTC First seen by agentprime
  3. 31 Oct 2026, 14:12 UTC Confirmed by OSV

Sources

Facts on this page come from the GitHub Advisory Database (CC-BY 4.0), OSV and the other sources listed, as published. We don’t reproduce full advisory descriptions, which can contain exploit code.