# CVE-2026-42600: MinIO: Path Traversal via msgpack Body in `ReadMultiple` Storage-REST Endpoint

> An attacker with cluster root JWT can read arbitrary files outside configured drive roots via path traversal in the ReadMultiple endpoint.

- **Severity:** Medium 6.9 (`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`)
- **Exploited in the wild:** Not known
- **Login needed:** An administrator
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 11 May 2026
- **Updated:** 15 May 2026
- **Also known as:** GHSA-xh8f-g2qw-gcm7, GO-2026-5757

## What is CVE-2026-42600?

CVE-2026-42600 is a medium-severity path traversal vulnerability in minio, published on 11 May 2026. An attacker needs administrator access to exploit it, with no action from the victim.

### Official description

MinIO is a high-performance object storage system. From RELEASE.2022-07-24T01-54-52Z to before RELEASE.2026-04-14T21-32-45Z, A path traversal vulnerability in MinIO's ReadMultiple internode storage-REST endpoint allows a caller holding the cluster root JWT to read files from outside the configured drive roots, bounded only by the MinIO process UID. The attacker sends POST minio/storage/{drivePath}/v63/rmpl with a msgpack-encoded body carrying ../ sequences in the Bucket field. The server opens the resulting path via os.OpenFile with O_RDONLY|O_NOATIME and returns its contents in the msgpack response stream. This vulnerability is fixed in RELEASE.2026-04-14T21-32-45Z.

Weakness: CWE-22 (Improper Limitation of a Pathname to a Restricted Directory)

## Which versions are affected by CVE-2026-42600?

3 open source packages ship an affected version, including github.com/minio/minio. It affects 1 product.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `github.com/minio/minio` | Go | All versions | None |
| `github.com/minio/minio` | Go | From 0.0.0-20220724015452 | 0.0.0-20260414213245 |
| `github.com/minio/minio` | Go | From 0.0.0-20220724015452 | 0.0.0-20260414213245 |

Products: Minio Minio.

## How do I fix CVE-2026-42600?

Upgrade github.com/minio/minio to 0.0.0-20260414213245 or later.

## Is CVE-2026-42600 being exploited?

There is no known exploitation of CVE-2026-42600 in the wild and no public exploit code.

## Other vulnerabilities in minio

- [CVE-2023-28434](https://insights.sbomify.com/CVE-2023-28434/): MinIO Security Feature Bypass (high 8.8, exploited in the wild)
- [CVE-2023-28432](https://insights.sbomify.com/CVE-2023-28432/): MinIO Information Disclosure (high 7.5, exploited in the wild)
- [CVE-2020-11012](https://insights.sbomify.com/CVE-2020-11012/): Authentication bypass MinIO Admin API (critical 9.3)
- [CVE-2026-33322](https://insights.sbomify.com/CVE-2026-33322/): MinIO: JWT Algorithm Confusion in OIDC Authentication (critical 9.2)
- [CVE-2026-33419](https://insights.sbomify.com/CVE-2026-33419/): MinIO: LDAP login brute-force via user enumeration and missing rate limit (critical 9.1)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-42600 and fix it if it is affected.

What it is: CVE-2026-42600 is a medium-severity path traversal vulnerability in minio, published on 11 May 2026. An attacker needs administrator access to exploit it, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-42600 in the wild and no public exploit code.

Affected packages and fixed versions:
- github.com/minio/minio (Go): affected all versions; no fix listed
- github.com/minio/minio (Go): affected from 0.0.0-20220724015452; fixed in 0.0.0-20260414213245
- github.com/minio/minio (Go): affected from 0.0.0-20220724015452; fixed in 0.0.0-20260414213245

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-42600/ (Markdown: https://insights.sbomify.com/CVE-2026-42600/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-42600
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-42600
- OSV: https://osv.dev/vulnerability/CVE-2026-42600

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-42600/
Summaries are generated and may contain mistakes; the official description above is the record.