GPU VulnDB

Database/Control plane, storage & DevOps

MinIO: unsigned x-amz-* headers accepted in SigV4, escalating a presigned PUT into a cross-bucket read

CVSS 8.8CVE-2026-122267Control plane, storage & DevOpscurated

Impact

MinIO is a common object store behind training datasets, checkpoints and model registries on GPU fleets. Signature V4 verification before RELEASE.2026-09-22T19-25-18Z does not cover x-amz-* headers that were not signed, so anyone holding a single narrow presigned PUT URL can add headers that turn the request into a read of objects in another bucket. On a shared cluster that breaks the tenant boundary the bucket policy was supposed to enforce: a presigned upload URL handed to a job, a notebook user or an external party becomes a way to pull datasets or checkpoints belonging to someone else. Presigned URLs are routinely passed around and logged, so the credential needed is one an operator does not think of as sensitive.

Who can reach it

Anyone who obtains a presigned PUT URL for the MinIO endpoint - no MinIO account or further authentication needed. Network reach to the S3 endpoint is enough.

What to do

Upgrade MinIO to RELEASE.2026-09-22T19-25-18Z or later and restart the server processes; on a distributed deployment this is a rolling restart of each MinIO node, no host reboot. Until then, treat outstanding presigned URLs as broader than intended - shorten expiries and re-issue any long-lived ones. GPU nodes do not need draining.

References

Related entries

All Control plane, storage & DevOps entries

This entry is curated: imported from vendor advisories with machine assistance, not yet individually verified. Confirm against your vendor's advisory before acting, and report anything wrong.