CVE-2026-97731

LOWCVSS 7.1 · HIGH

Signal is active with 2 mentions in latest observed window

Immediate actions

  • Track advisory updates for patch or workaround availability

Recommended action window: Monitor and triage in normal cycle

NVD description

MinIO through 7aac2a2 does not verify that every x-amz-* header present on a request also appears in the client-supplied X-Amz-SignedHeaders list. extractSignedHeaders() in cmd/signature-v4-utils.go iterates only the claimed list and never enumerates the headers that actually arrived, and thus a header that arrives unsigned is neither hashed into the canonical request nor rejected. Because cmd/api-router.go dispatches CopyObject on the presence of x-amz-copy-source alone, the holder of a presigned PUT URL scoped to a single object can add that header to the unmodified URL and cause a server-side copy, executed as the signer, of any object the signing key can read. A grant to write one object becomes a read of every bucket that key can reach. Amazon S3 rejects the equivalent request with HTTP 403 AccessDenied. The minio/minio GitHub repository was archived in April 2026; pgsty/silo before 1233254 is also affected.

0.0/ 10 priority

Sources & remediation

Weakness type (CWE)
CWE-347

Priority

LOW

Exploitation

NONE

PoC

NONE

Patch

NONE

Momentum

NONE

Threat summary

  • 2 mentions across 1 observed day

What's happening

  • 2 total mentions across 1 day

Deep dive

Activity timeline2 mentions / 1d
01122Mentions · 2026-09-25: 209-25
Referenced assets1 URL
Full discourse2 posts
  • CyberSignal | Cybersecurity & AI News@XQOPTRX

    🚨 NEW MINIO FLAW CAN TURN LIMITED PRESIGNED WRITE ACCESS INTO BROADER DATA READ ACCESS A newly published vulnerability in MinIO is worth attention for organizations running S3-compatible object storage. Tracked as: CVE-2026-97731 CVSS: 7.1 HIGH The issue concerns AWS Signature Version 4 header validation. According to the published CVE record, MinIO does not ensure that every incoming x-amz-* header is included in the request's signed-header list. The result? An attacker holding a presigned PUT URL for one object may be able to add an x-amz-copy-source header. MinIO can then perform the copy using the permissions of the identity that originally signed the URL. In certain scenarios: Permission to write one object could become access to copy/read other objects accessible to the signer. Amazon S3 rejects the equivalent request. 🧠 Why this matters: Presigned URLs are deliberately used to grant narrow, temporary permissions. A vulnerability that expands what such a URL can authorize undermines the security assumption behind the entire delegation mechanism. Source: CVE/MITRE data via CVEKit · NVD/ENISA enrichment.

    0102065
    228 followersView on X
  • Severity Daily@severitydaily

    A CVE published today lists every MinIO build as affected, and the only fix it cites lives in a community fork — MinIO's repository has been archived since April. No exploitation reported. https://severitydaily.com/minio-cve-2026-97731-unsigned-x-amz-headers-fix-only-in-fork-repo-archived/

    0000021
    24 followersView on X

Explore more