CVE-2025-27414: MinIO allows an SFTP authentication bypass due to improperly trusted SSH key
Summary A bug in evaluating the trust of the SSH key used in an SFTP connection to MinIO allows authentication bypass and unauthorized data access. Details On a MinIO server with SFTP access configured and using LDAP as an external identity provider, MinIO supports SSH key based authentication for SFTP connections when the user has the sshPublicKey attribute set in their LDAP server.
Published Mar 3, 2025
Affected packages
github.com/minio/minio
- Ecosystem
- Go
- Affected
- >= 0.0.0-20240605075113-91e1487de457, < 0.0.0-20250227184332-4c71f1b4ec0f
- Fixed in
- 0.0.0-20250227184332-4c71f1b4ec0f
- Check
go list -m github.com/minio/minio
Advisory details
From the GitHub Advisory Database (CC BY 4.0).
Summary
_A bug in evaluating the trust of the SSH key used in an SFTP connection to MinIO allows authentication bypass and unauthorized data access._
Details
On a MinIO server with SFTP access configured and using LDAP as an external identity provider, MinIO supports SSH key based authentication for SFTP connections when the user has the sshPublicKey attribute set in their LDAP server. The server trusts the client's key only when the public key is the same as the sshPublicKey attribute.
Due to the bug, when the user has no sshPublicKey property in LDAP, the server ends up trusting the key allowing the client to perform any FTP operations allowed by the MinIO access policies associated with the LDAP user (or any of their groups).
The bug was introduced in https://github.com/minio/minio/commit/91e1487de45720753c9e9e4c02b1bd16b7e452fa.
Impact
The following requirements must be met to exploit this vulnerability:
- MinIO server must be configured to allow SFTP access and use LDAP as an external identity provider.
- Knowledge of an LDAP username that does not have the
sshPublicKeyproperty set. - Such an LDAP username or one of their groups must also have some MinIO access policy configured.
When this bug is successfully exploited, the attacker can perform any FTP operations (i.e. reading, writing, deleting and listing objects) allowed by the access policy associated with the LDAP user account (and their groups).
Credited to donatello, ston1th.
References
- https://github.com/minio/minio/security/advisories/GHSA-wc79-7x8x-2p58
- https://nvd.nist.gov/vuln/detail/CVE-2025-27414
- https://github.com/minio/minio/commit/4c71f1b4ec0fb2a473ddaac18c20ec9e63f267ec
- https://github.com/minio/minio/commit/91e1487de45720753c9e9e4c02b1bd16b7e452fa
- https://github.com/advisories/GHSA-wc79-7x8x-2p58
How this page is made: the data panel comes from the GitHub Advisory Database, CISA’s KEV catalog, the NVD and FIRST EPSS, and updates twice a day. No analysis has been written for this entry yet. Methodology
More Go vulnerabilities
All Go entriesCVE-2026-42600
MinIO vulnerable to Path Traversal via msgpack Body in `ReadMultiple` Storage-REST Endpoint
medium4.9May 5, 2026CVE-2026-40344
MinIO has an Unauthenticated Object Write via Missing Signature Verification in Unsigned-Trailer Uploads
high8.2No fixApr 14, 2026CVE-2026-41145
MinIO has an Unauthenticated Object Write via Query-String Credential Signature Bypass in Unsigned-Trailer Uploads
high8.2No fixApr 14, 2026CVE-2026-39414
MinIO affected a DoS via Unbounded Memory Allocation in S3 Select CSV Parsing
high7.1No fixApr 9, 2026CVE-2026-34204
MinIO is Vulnerable to SSE Metadata Injection via Replication Headers
high7.1No fixMar 27, 2026CVE-2026-33419
MinIO LDAP login brute-force via user enumeration and missing rate limit
critical9.1No fixMar 20, 2026
