dbcve.org
MinioApplication

CVE-2026-33322

CRITICAL · 9.8 CVSS v3.1 Published 2026-03-24
Fix available
A fix is available. Upgrade to 2026-03-17t21-25-16z or later.
See remediation →
100/100
Remediation priority · Urgent
Remotely reachable No privileges Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
MinIO is a high-performance object storage system. From RELEASE.2022-11-08T05-27-07Z to before RELEASE.2026-03-17T21-25-16Z, a JWT algorithm confusion vulnerability in MinIO's OpenID Connect authentication allows an attacker who knows the OIDC ClientSecret to forge arbitrary identity tokens and obtain S3 credentials with any policy, including consoleAdmin. This issue has been patched in RELEASE.2026-03-17T21-25-16Z.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

JWT algorithm confusion vulnerability in MinIO's OpenID Connect (OIDC) authentication allows an attacker who knows the OIDC ClientSecret to forge arbitrary identity tokens and obtain S3 credentials with any policy, including consoleAdmin privileges.

MitigationUpgrade MinIO to RELEASE.2026-03-17T21-25-16Z or later. Review OIDC ClientSecret exposure and audit access logs for unauthorized administrative activity until patched.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
MinioApplication
Affected:>= 2022-11-08t05-27-07z, < 2026-03-17t21-25-16z

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
None
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Check MinIO version
    Run 'minio version' command or query the server health endpoint to retrieve the installed MinIO version string
    Affected if Version is >= 2022-11-08t05-27-07z AND < 2026-03-17t21-25-16z
  2. Verify OIDC authentication is enabled
    Inspect MinIO server configuration for identity_openid or similar OIDC-related config keys (check server startup args or config file)
    Affected if OIDC/OpenID Connect authentication is configured and active in the MinIO environment
  3. Assess OIDC ClientSecret exposure risk
    Review where the OIDC ClientSecret is stored, check configuration files, environment variables, and logs for accidental exposure
    Affected if The OIDC ClientSecret is accessible beyond authorized administrators or was logged/displayed insecurely
  4. Audit for unauthorized administrative access
    Review MinIO audit logs and access logs for S3 credential generation events or consoleAdmin policy assignments originating from OIDC sessions
    Affected if There are consoleAdmin credential generation events or policy changes that were not initiated by authorized administrators

User is affected if MinIO version falls within the vulnerable range AND OIDC is enabled AND the ClientSecret could have been compromised or accessed by an attacker

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Upgrade available Upgrade to 2026-03-17t21-25-16z or later
Fixed in 2026-03-17t21-25-16z
Interim mitigation

Upgrade MinIO to RELEASE.2026-03-17T21-25-16Z or later. Review OIDC ClientSecret exposure and audit access logs for unauthorized administrative activity until patched.

Recommended fix High confidence

RELEASE.2026-03-17T21-25-16Z or later

  1. Stop the MinIO server gracefully to ensure all pending operations complete
  2. Backup the MinIO data directory and configuration files (typically /etc/minio/config.json or environment variables)
  3. Download the fixed MinIO binary from the official MinIO releases: RELEASE.2026-03-17T21-25-16Z or later from github.com/minio/minio
  4. Replace the existing MinIO binary with the new version
  5. Verify the MinIO configuration is intact
  6. Start the MinIO server with the updated binary
  7. Confirm the server starts successfully and is running the patched version using `minio version`
  8. If using OpenID Connect, verify OIDC authentication is functioning correctly after upgrade
Caveat Review MinIO release notes between your current version and the target version for any configuration or feature changes that may require adjustment

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Minio Scoped from the published advisory
  • Consultation2.0 h
  • Implementation1.0 h
  • Testing2.0 h
  • Review / QA1.0 h
6.0 hours of engineering $1,060
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,696.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-33322 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2026-33322 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data