CVE-2026-42600: Github.com/minio/minio Path Traversal Vulnerability
MODERATE
Advisory Identifier:
GHSA-xh8f-g2qw-gcm7
Advisory Summary
CVE-2026-42600 is a MODERATE (CVSS 4.9) path traversal vulnerability (CWE-22: Improper Limitation of a Pathname to a Restricted Directory ('Path Traversal')) affecting Github.com/minio/minio libraries in the Go ecosystem. The issue involves minio vulnerable to path traversal via msgpack body in `readmultiple` storage-rest endpoint. Remediation is available by upgrading affected packages to version 0.0.0-20260414213245.
CVE-2026-42600 at a Glance
CVE Identifier
CVE-2026-42600
GHSA Identifier
GHSA-xh8f-g2qw-gcm7
Severity
MODERATE
CVSS v3.1 Base Score
4.9
CWE Classification
CWE-22: Improper Limitation of a Pathname to a Restricted Directory ('Path Traversal')
Affected Product
Github.com/minio/minio
Package Ecosystem
Go
Published Date
Last Updated
Security Impact
CVSS: 4.9
The security impact metrics below are parsed directly from the CVSS v3.1 vector string (CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:H/I:N/A:N).
Attack Vector
Network (AV:N)
Attack Complexity
Low (AC:L)
Privileges Required
High (PR:H)
User Interaction
None (UI:N)
Scope
Unchanged (S:U)
Confidentiality
High (C:H)
Integrity
None (I:N)
Availability
None (A:N)
How to Fix CVE-2026-42600
To remediate this vulnerability, upgrade all affected Github.com/minio/minio dependencies to a patched release. Both direct and transitive dependencies should be checked, as frameworks or security libraries may pull in vulnerable versions transitively.
github.com/minio/minio
fixed: 0.0.0-20260414213245
Upgrade github.com/minio/minio to 0.0.0-20260414213245
Verify Direct and Transitive Dependencies
Run the following command in your project directory to verify that all resolved dependencies use the patched release:
inspect dependencies for github.com/minio/minioHow to Check if You Are Affected
To determine whether your application is affected by CVE-2026-42600, inspect your project dependencies for Github.com/minio/minio:
inspect dependencies for github.com/minio/minioAnalyze the terminal output to locate any version of Github.com/minio/minio in your dependency tree. If any resolved version matches the vulnerable ranges listed in the table below (for example, versions earlier than 0.0.0-20260414213245), your application is affected.
Note: Verify declared build manifests and deployed runtime container environments.
Technical Details
Vulnerability Mechanism & Technical Analysis
This vulnerability is classified under CWE-22: Improper Limitation of a Pathname to a Restricted Directory ('Path Traversal'), where the product uses external input to construct a pathname that is intended to identify a file or directory that is located underneath a restricted parent directory, but the product does not properly neutralize special elements within the pathname that can cause the pathname to resolve to a location that is outside of the restricted directory. In Github.com/minio/minio, software state validation or input boundaries are circumvented during processing. Review the official source advisory statement below for specific affected components, classes, and reproduction details.
Source Advisory Statement
### Impact
_What kind of vulnerability is it? Who is impacted?_
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.
Distributed-erasure (multi-node) MinIO deployments are impacted. Single-node
standalone deployments do not register the route and are not affected. The
attack requires an HS512 JWT signed with `MINIO_ROOT_PASSWORD` and carrying
`accessKey = MINIO_ROOT_USER` — the same secret every peer in the cluster
holds to authenticate internode traffic, so a compromised peer or any actor in
possession of the root credential can mint one.
The `ReadMultiple` handler (`cmd/storage-rest-server.go`) decodes a msgpack
`ReadMultipleReq` body containing `Bucket`, `Prefix`, and `Files` fields and
forwards them to `xlStorage.ReadMultiple` (`cmd/xl-storage.go`) without
validation:
```go
volumeDir := pathJoin(s.drivePath, req.Bucket) // traversal resolves here
for _, f := range req.Files {
fullPath := pathJoin(volumeDir, req.Prefix, f)
data, mt, err = s.readAllDataWithDMTime(ctx, req.Bucket, volumeDir, fullPath)
}
```
`pathJoin` calls `path.Clean`, which resolves `..` components and produces an
absolute path anywhere on the filesystem — it is not a root jail. The global
`setRequestValidityMiddleware` rejects `..` in `r.URL.Path` and `r.Form` but
does not inspect request bodies, so msgpack-encoded traversal bypasses it.
Sibling storage methods (`StatInfoFile`, `ReadFileHandler`, `ReadVersion`)
validate their volume argument through `s.getVolDir(volume)`, which rejects
`..`; `ReadMultiple` skips this call.
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.
**Impact by deployment:**
- **Bare-metal with `User=minio` in the systemd unit** — the `O_NOATIME`
ownership check bounds the read to files owned by the MinIO UID. Reachable
secrets include TLS private keys, KMS/KES key material, systemd credentials,
and data belonging to other tenants sharing the same UID on the host.
Secrets leaked this way persist across cluster credential rotation.
- **Containerized running as UID 0** (the historical default for the official
Docker image, `docker-compose` examples, and Helm charts without
`securityContext.runAsNonRoot`) — the primitive escalates to arbitrary
host-filesystem disclosure: `/etc/shadow`, `/root/**`, Kubernetes
service-account tokens, cloud-init metadata caches.
**Affected components:** `cmd/storage-rest-server.go` (`ReadMultiple` handler),
`cmd/xl-storage.go` (`xlStorage.ReadMultiple`).
**CWE:** CWE-22 (Improper Limitation of a Pathname to a Restricted Directory
— 'Path Traversal')
**CVSS v4.0 Score:** 6.9 (Medium)
**Vector:** `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`
### Affected Versions
All MinIO releases from `RELEASE.2022-07-24T01-54-52Z` through the final
release of the minio/minio open-source project, `RELEASE.2025-09-07T16-13-09Z`.
The vulnerability was introduced in commit
[`f939d1c18`](https://github.com/minio/minio/commit/f939d1c1831c71f4b1c14df6d9cd62b12ccce7a3)
("Independent Multipart Uploads",
[PR #15346](https://github.com/minio/minio/pull/15346)), which added the
`ReadMultiple` storage-REST endpoint as part of the multipart upload
redesign. The first affected release is `RELEASE.2022-07-24T01-54-52Z`.
### Patches
**Fixed in**: MinIO AIStor `RELEASE.2026-04-14T21-32-45Z` (recommended
upgrade target). The fix — which removed the `ReadMultiple` handler, the
corresponding storage-driver method, the msgpack datatypes, the REST-client
wrapper, and the route registration — first shipped in **MinIO AIStor
`RELEASE.2024-10-23T19-38-07Z`**. Every AIStor release from
`RELEASE.2024-10-23T19-38-07Z` onward is unaffected; users should upgrade to
`RELEASE.2026-04-14T21-32-45Z` or later to pick up the accumulated fixes and
improvements shipped since.
#### Binary Downloads
| Platform | Architecture | Download |
| -------- | ------------ | --------------------------------------------------------------------------- |
| Linux | amd64 | [minio](https://dl.min.io/aistor/minio/release/linux-amd64/minio) |
| Linux | arm64 | [minio](https://dl.min.io/aistor/minio/release/linux-arm64/minio) |
| macOS | arm64 | [minio](https://dl.min.io/aistor/minio/release/darwin-arm64/minio) |
| macOS | amd64 | [minio](https://dl.min.io/aistor/minio/release/darwin-amd64/minio) |
| Windows | amd64 | [minio.exe](https://dl.min.io/aistor/minio/release/windows-amd64/minio.exe) |
#### FIPS Binaries
| Platform | Architecture | Download |
| -------- | ------------ | --------------------------------------------------------------------------- |
| Linux | amd64 | [minio.fips](https://dl.min.io/aistor/minio/release/linux-amd64/minio.fips) |
| Linux | arm64 | [minio.fips](https://dl.min.io/aistor/minio/release/linux-arm64/minio.fips) |
#### Package Downloads
| Format | Architecture | Download |
| ------ | ------------ | ----------------------------------------------------------------------------------------------------------------------------------- |
| DEB | amd64 | [minio_20260414213245.0.0_amd64.deb](https://dl.min.io/aistor/minio/release/linux-amd64/minio_20260414213245.0.0_amd64.deb) |
| DEB | arm64 | [minio_20260414213245.0.0_arm64.deb](https://dl.min.io/aistor/minio/release/linux-arm64/minio_20260414213245.0.0_arm64.deb) |
| RPM | amd64 | [minio-20260414213245.0.0-1.x86_64.rpm](https://dl.min.io/aistor/minio/release/linux-amd64/minio-20260414213245.0.0-1.x86_64.rpm) |
| RPM | arm64 | [minio-20260414213245.0.0-1.aarch64.rpm](https://dl.min.io/aistor/minio/release/linux-arm64/minio-20260414213245.0.0-1.aarch64.rpm) |
#### Container Images
```bash
# Standard
docker pull quay.io/minio/aistor/minio:RELEASE.2026-04-14T21-32-45Z
podman pull quay.io/minio/aistor/minio:RELEASE.2026-04-14T21-32-45Z
# FIPS
docker pull quay.io/minio/aistor/minio:RELEASE.2026-04-14T21-32-45Z.fips
podman pull quay.io/minio/aistor/minio:RELEASE.2026-04-14T21-32-45Z.fips
```
#### Homebrew (macOS)
```bash
brew install minio/aistor/minio
```
### Workarounds
- [Users of the open-source `minio/minio` project should upgrade to MinIO AIStor `RELEASE.2026-04-14T21-32-45Z` or later.](https://docs.min.io/enterprise/aistor-object-store/upgrade-aistor-server/community-edition/)
If upgrading is not immediately possible:
- **Rotate the root credential and restrict who holds it.** The exploit
requires a JWT signed with `MINIO_ROOT_PASSWORD`. Treat the root credential
as the host-filesystem disclosure primitive that it is: rotate it after any
suspected exposure, store it only in the secret manager that bootstraps the
cluster, and do not hand it to applications or operators who only need
object-level access.
- **Do not run the MinIO container as UID 0.** Set
`securityContext.runAsNonRoot: true` (and a non-zero `runAsUser`) in
Kubernetes manifests, or add `--user` to `docker run`. This reduces the
blast radius from arbitrary host-filesystem disclosure to MinIO-UID-owned
files only.
- **Restrict the internode storage-REST port at the network layer.** In
distributed deployments, the storage-REST route is served on the same port
as the S3 API by default. Where feasible, use `--internode-port` to expose
internode traffic on a separate interface reachable only from other cluster
peers, and block that interface from client networks.
### Credits
- **Finders:** Discovered by Claude, Anthropic's AI assistant, and triaged by
**Adrian Denkiewicz** at **Doyensec** in collaboration with **Anthropic
Research**.
### Resources
- Introducing commit: [`f939d1c18`](https://github.com/minio/minio/commit/f939d1c1831c71f4b1c14df6d9cd62b12ccce7a3)
([PR #15346](https://github.com/minio/minio/pull/15346))
- [CWE-22 — Improper Limitation of a Pathname to a Restricted Directory](https://cwe.mitre.org/data/definitions/22.html)
- [CVE-2022-35919 — MinIO admin-authenticated path traversal in server-update endpoint (same class, different channel)](https://github.com/minio/minio/security/advisories/GHSA-gr9v-6pcm-rqvg)
- [MinIO AIStor](https://min.io/aistor)
CVE-2026-42600 Affected Github.com/minio/minio Versions
1 component(s)
Fixed Versions:
0.0.0-20260414213245
| Product / Package | Ecosystem | Affected Versions | Fixed Version |
|---|---|---|---|
|
github.com/minio/minio
|
Go |
≥ 0.0.0-20220724015452
< 0.0.0-20260414213245
|
0.0.0-20260414213245
|
References
Frequently Asked Questions
What is CVE-2026-42600?
CVE-2026-42600 is a security vulnerability in Github.com/minio/minio involving MinIO vulnerable to Path Traversal via msgpack Body in `ReadMultiple` Storage-REST Endpoint under CWE-22: Improper Limitation of a Pathname to a Restricted Directory ('Path Traversal').
Which Github.com/minio/minio versions are affected?
Affected versions include releases prior to 0.0.0-20260414213245 across affected packages: github.com/minio/minio.
What version fixes CVE-2026-42600?
Upgrading to 0.0.0-20260414213245 (or the latest patched release for your respective branch) resolves the vulnerability.
Is github.com/minio/minio affected?
Yes, github.com/minio/minio is affected in releases prior to 0.0.0-20260414213245. Upgrade your dependency to 0.0.0-20260414213245 or later.
What is the CVSS score of CVE-2026-42600?
CVE-2026-42600 has a CVSS v3.1 base score of 4.9 (MODERATE) with vector string CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:H/I:N/A:N.
What CWE is associated with CVE-2026-42600?
CVE-2026-42600 is classified under CWE-22: Improper Limitation of a Pathname to a Restricted Directory ('Path Traversal') (The product uses external input to construct a pathname that is intended to identify a file or directory that is located underneath a restricted parent directory, but the product does not properly neutralize special elements within the pathname that can cause the pathname to resolve to a location that is outside of the restricted directory.).
How can I check Go dependencies for CVE-2026-42600?
Run the dependency tree command: 'inspect dependencies for github.com/minio/minio'. This command lists direct and transitive dependencies in your build configuration so you can verify if a vulnerable version is resolved.
Machine-readable OSV JSON
OSV v1.5 Schema
Normalized schema output
{
"schema_version" : "1.4.0",
"id" : "GHSA-xh8f-g2qw-gcm7",
"modified" : "2026-06-08T23:26:31Z",
"published" : "2026-05-05T20:05:05Z",
"aliases" : [ "CVE-2026-42600" ],
"summary" : "MinIO vulnerable to Path Traversal via msgpack Body in `ReadMultiple` Storage-REST Endpoint",
"details" : "### Impact\n\n_What kind of vulnerability is it? Who is impacted?_\n\nA path traversal vulnerability in MinIO's `ReadMultiple` internode storage-REST\nendpoint allows a caller holding the cluster root JWT to read files from\noutside the configured drive roots, bounded only by the MinIO process UID.\n\nDistributed-erasure (multi-node) MinIO deployments are impacted. Single-node\nstandalone deployments do not register the route and are not affected. The\nattack requires an HS512 JWT signed with `MINIO_ROOT_PASSWORD` and carrying\n`accessKey = MINIO_ROOT_USER` — the same secret every peer in the cluster\nholds to authenticate internode traffic, so a compromised peer or any actor in\npossession of the root credential can mint one.\n\nThe `ReadMultiple` handler (`cmd/storage-rest-server.go`) decodes a msgpack\n`ReadMultipleReq` body containing `Bucket`, `Prefix`, and `Files` fields and\nforwards them to `xlStorage.ReadMultiple` (`cmd/xl-storage.go`) without\nvalidation:\n\n```go\nvolumeDir := pathJoin(s.drivePath, req.Bucket) // traversal resolves here\nfor _, f := range req.Files {\n fullPath := pathJoin(volumeDir, req.Prefix, f)\n data, mt, err = s.readAllDataWithDMTime(ctx, req.Bucket, volumeDir, fullPath)\n}\n```\n\n`pathJoin` calls `path.Clean`, which resolves `..` components and produces an\nabsolute path anywhere on the filesystem — it is not a root jail. The global\n`setRequestValidityMiddleware` rejects `..` in `r.URL.Path` and `r.Form` but\ndoes not inspect request bodies, so msgpack-encoded traversal bypasses it.\nSibling storage methods (`StatInfoFile`, `ReadFileHandler`, `ReadVersion`)\nvalidate their volume argument through `s.getVolDir(volume)`, which rejects\n`..`; `ReadMultiple` skips this call.\n\nThe attacker sends `POST /minio/storage/{drivePath}/v63/rmpl` with a\nmsgpack-encoded body carrying `../` sequences in the `Bucket` field. The\nserver opens the resulting path via `os.OpenFile` with `O_RDONLY|O_NOATIME`\nand returns its contents in the msgpack response stream.\n\n**Impact by deployment:**\n\n- **Bare-metal with `User=minio` in the systemd unit** — the `O_NOATIME`\n ownership check bounds the read to files owned by the MinIO UID. Reachable\n secrets include TLS private keys, KMS/KES key material, systemd credentials,\n and data belonging to other tenants sharing the same UID on the host.\n Secrets leaked this way persist across cluster credential rotation.\n\n- **Containerized running as UID 0** (the historical default for the official\n Docker image, `docker-compose` examples, and Helm charts without\n `securityContext.runAsNonRoot`) — the primitive escalates to arbitrary\n host-filesystem disclosure: `/etc/shadow`, `/root/**`, Kubernetes\n service-account tokens, cloud-init metadata caches.\n\n**Affected components:** `cmd/storage-rest-server.go` (`ReadMultiple` handler),\n`cmd/xl-storage.go` (`xlStorage.ReadMultiple`).\n\n**CWE:** CWE-22 (Improper Limitation of a Pathname to a Restricted Directory\n— 'Path Traversal')\n\n**CVSS v4.0 Score:** 6.9 (Medium)\n\n**Vector:** `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`\n\n### Affected Versions\n\nAll MinIO releases from `RELEASE.2022-07-24T01-54-52Z` through the final\nrelease of the minio/minio open-source project, `RELEASE.2025-09-07T16-13-09Z`.\n\nThe vulnerability was introduced in commit\n[`f939d1c18`](https://github.com/minio/minio/commit/f939d1c1831c71f4b1c14df6d9cd62b12ccce7a3)\n(\"Independent Multipart Uploads\",\n[PR #15346](https://github.com/minio/minio/pull/15346)), which added the\n`ReadMultiple` storage-REST endpoint as part of the multipart upload\nredesign. The first affected release is `RELEASE.2022-07-24T01-54-52Z`.\n\n### Patches\n\n**Fixed in**: MinIO AIStor `RELEASE.2026-04-14T21-32-45Z` (recommended\nupgrade target). The fix — which removed the `ReadMultiple` handler, the\ncorresponding storage-driver method, the msgpack datatypes, the REST-client\nwrapper, and the route registration — first shipped in **MinIO AIStor\n`RELEASE.2024-10-23T19-38-07Z`**. Every AIStor release from\n`RELEASE.2024-10-23T19-38-07Z` onward is unaffected; users should upgrade to\n`RELEASE.2026-04-14T21-32-45Z` or later to pick up the accumulated fixes and\nimprovements shipped since.\n\n#### Binary Downloads\n\n| Platform | Architecture | Download |\n| -------- | ------------ | --------------------------------------------------------------------------- |\n| Linux | amd64 | [minio](https://dl.min.io/aistor/minio/release/linux-amd64/minio) |\n| Linux | arm64 | [minio](https://dl.min.io/aistor/minio/release/linux-arm64/minio) |\n| macOS | arm64 | [minio](https://dl.min.io/aistor/minio/release/darwin-arm64/minio) |\n| macOS | amd64 | [minio](https://dl.min.io/aistor/minio/release/darwin-amd64/minio) |\n| Windows | amd64 | [minio.exe](https://dl.min.io/aistor/minio/release/windows-amd64/minio.exe) |\n\n#### FIPS Binaries\n\n| Platform | Architecture | Download |\n| -------- | ------------ | --------------------------------------------------------------------------- |\n| Linux | amd64 | [minio.fips](https://dl.min.io/aistor/minio/release/linux-amd64/minio.fips) |\n| Linux | arm64 | [minio.fips](https://dl.min.io/aistor/minio/release/linux-arm64/minio.fips) |\n\n#### Package Downloads\n\n| Format | Architecture | Download |\n| ------ | ------------ | ----------------------------------------------------------------------------------------------------------------------------------- |\n| DEB | amd64 | [minio_20260414213245.0.0_amd64.deb](https://dl.min.io/aistor/minio/release/linux-amd64/minio_20260414213245.0.0_amd64.deb) |\n| DEB | arm64 | [minio_20260414213245.0.0_arm64.deb](https://dl.min.io/aistor/minio/release/linux-arm64/minio_20260414213245.0.0_arm64.deb) |\n| RPM | amd64 | [minio-20260414213245.0.0-1.x86_64.rpm](https://dl.min.io/aistor/minio/release/linux-amd64/minio-20260414213245.0.0-1.x86_64.rpm) |\n| RPM | arm64 | [minio-20260414213245.0.0-1.aarch64.rpm](https://dl.min.io/aistor/minio/release/linux-arm64/minio-20260414213245.0.0-1.aarch64.rpm) |\n\n#### Container Images\n\n```bash\n# Standard\ndocker pull quay.io/minio/aistor/minio:RELEASE.2026-04-14T21-32-45Z\npodman pull quay.io/minio/aistor/minio:RELEASE.2026-04-14T21-32-45Z\n\n# FIPS\ndocker pull quay.io/minio/aistor/minio:RELEASE.2026-04-14T21-32-45Z.fips\npodman pull quay.io/minio/aistor/minio:RELEASE.2026-04-14T21-32-45Z.fips\n```\n\n#### Homebrew (macOS)\n\n```bash\nbrew install minio/aistor/minio\n```\n\n### Workarounds\n\n- [Users of the open-source `minio/minio` project should upgrade to MinIO AIStor `RELEASE.2026-04-14T21-32-45Z` or later.](https://docs.min.io/enterprise/aistor-object-store/upgrade-aistor-server/community-edition/)\n\nIf upgrading is not immediately possible:\n\n- **Rotate the root credential and restrict who holds it.** The exploit\n requires a JWT signed with `MINIO_ROOT_PASSWORD`. Treat the root credential\n as the host-filesystem disclosure primitive that it is: rotate it after any\n suspected exposure, store it only in the secret manager that bootstraps the\n cluster, and do not hand it to applications or operators who only need\n object-level access.\n\n- **Do not run the MinIO container as UID 0.** Set\n `securityContext.runAsNonRoot: true` (and a non-zero `runAsUser`) in\n Kubernetes manifests, or add `--user` to `docker run`. This reduces the\n blast radius from arbitrary host-filesystem disclosure to MinIO-UID-owned\n files only.\n\n- **Restrict the internode storage-REST port at the network layer.** In\n distributed deployments, the storage-REST route is served on the same port\n as the S3 API by default. Where feasible, use `--internode-port` to expose\n internode traffic on a separate interface reachable only from other cluster\n peers, and block that interface from client networks.\n\n### Credits\n\n- **Finders:** Discovered by Claude, Anthropic's AI assistant, and triaged by\n **Adrian Denkiewicz** at **Doyensec** in collaboration with **Anthropic\n Research**.\n\n### Resources\n\n- Introducing commit: [`f939d1c18`](https://github.com/minio/minio/commit/f939d1c1831c71f4b1c14df6d9cd62b12ccce7a3)\n ([PR #15346](https://github.com/minio/minio/pull/15346))\n- [CWE-22 — Improper Limitation of a Pathname to a Restricted Directory](https://cwe.mitre.org/data/definitions/22.html)\n- [CVE-2022-35919 — MinIO admin-authenticated path traversal in server-update endpoint (same class, different channel)](https://github.com/minio/minio/security/advisories/GHSA-gr9v-6pcm-rqvg)\n- [MinIO AIStor](https://min.io/aistor)",
"severity" : [ {
"type" : "CVSS_V3",
"score" : "CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:H/I:N/A:N"
}, {
"type" : "CVSS_V4",
"score" : "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"
} ],
"affected" : [ {
"package" : {
"ecosystem" : "Go",
"name" : "github.com/minio/minio"
},
"ranges" : [ {
"type" : "ECOSYSTEM",
"events" : [ {
"introduced" : "0.0.0-20220724015452"
}, {
"fixed" : "0.0.0-20260414213245"
} ]
} ]
} ],
"references" : [ {
"type" : "WEB",
"url" : "https://github.com/minio/minio/security/advisories/GHSA-xh8f-g2qw-gcm7"
}, {
"type" : "ADVISORY",
"url" : "https://nvd.nist.gov/vuln/detail/CVE-2026-42600"
}, {
"type" : "PACKAGE",
"url" : "https://github.com/minio/minio"
} ],
"database_specific" : {
"cwe_ids" : [ "CWE-22" ],
"severity" : "MODERATE",
"github_reviewed" : true,
"github_reviewed_at" : "2026-05-05T20:05:05Z",
"nvd_published_at" : "2026-05-11T22:22:11Z"
}
}