MinIO has released a patch to address a JWT algorithm confusion vulnerability (CVE-2026-33322) and an LDAP brute-force vulnerability (CVE-2026-33419). These vulnerabilities could allow attackers to bypass authentication or gain unauthorized access. Users of MinIO are strongly advised to update to the latest version.
Both CVE-2026-33322 and CVE-2026-33419 have a CVSS score of 9.5, indicating critical severity.
What is Github.com/minio/minio?
CVE-2026-33322: MinIO JWT Algorithm Confusion
Critical severity due to potential for complete system compromise.
EPSS score of 0.019 indicates a low probability of exploitation.
MinIO suffers from a JWT (JSON Web Token) algorithm confusion vulnerability in its OIDC (OpenID Connect) authentication implementation. An attacker could potentially forge JWT tokens using a different algorithm than expected, bypassing authentication and gaining unauthorized access.
How to fix CVE-2026-33322 in Github.com/minio/minio
Patch immediately- 1.Update your MinIO deployment to version RELEASE.2026-03-17T21-25-16Z or later.
go get -u github.com/minio/minio@latestVerify with:
minio --versionWorkaround: There is no known workaround. Apply the patch.
NextGuard automatically flags CVE-2026-33322 if Github.com/minio/minio appears in any of your monitored projects — no manual lookup required.
CVE-2026-33419: MinIO LDAP Brute-Force Vulnerability
Critical severity due to potential for complete system compromise.
EPSS score of 0.059 indicates a slightly higher probability of exploitation compared to CVE-2026-33322.
MinIO is vulnerable to LDAP login brute-force attacks due to user enumeration and a missing rate limit. An attacker can repeatedly attempt logins using different credentials, potentially gaining unauthorized access to the system.
How to fix CVE-2026-33419 in Github.com/minio/minio
Patch immediately- 1.Update your MinIO deployment to version RELEASE.2026-03-17T21-25-16Z or later.
go get -u github.com/minio/minio@latestVerify with:
minio --versionWorkaround: Implement external rate limiting mechanisms if possible, but patching is the recommended solution.
NextGuard automatically flags CVE-2026-33419 if Github.com/minio/minio appears in any of your monitored projects — no manual lookup required.
Stay ahead of go vulnerabilities
Proactively identify and remediate vulnerabilities in your go projects. Use NextGuard to monitor your go dependencies and receive alerts on new CVEs.
Compare PlansFrequently asked questions
These vulnerabilities highlight the importance of keeping your MinIO deployments up-to-date. Regularly patching your systems is crucial for maintaining a strong security posture. See all go vulnerabilities.
Related topics