# CVE-2025-27414: MinIO SFTP authentication bypass due to improperly trusted SSH key > Attackers can bypass SFTP authentication in MinIO when LDAP users lack SSH keys, allowing unauthorized data access and modification. - **Severity:** Medium 4.6 (`CVSS:4.0/AV:N/AC:L/AT:P/PR:N/UI:N/VC:N/VI:H/VA:N/SC:N/SI:N/SA:N/E:U`) - **Exploited in the wild:** Not known - **Login needed:** Not needed - **Attackable:** Over the internet - **Victim action needed:** Not needed - **Fix available:** Yes - **Published:** 28 Feb 2025 - **Updated:** 4 Mar 2025 - **Also known as:** GHSA-wc79-7x8x-2p58, GO-2025-3495 ## What is CVE-2025-27414? CVE-2025-27414 is a medium-severity authentication bypass vulnerability in minio, published on 28 Feb 2025. An attacker can exploit it over the internet without logging in, with no action from the victim. ### Official description MinIO is a high performance object storage. Starting in RELEASE.2024-06-06T09-36-42Z and prior to RELEASE.2025-02-28T09-55-16Z, a bug in evaluating the trust of the SSH key used in an SFTP connection to MinIO allows authentication bypass and unauthorized data access. 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). Three requirements must be met in order to exploit the vulnerability. First, the MinIO server must be configured to allow SFTP access and use LDAP as an external identity provider. Second, the attacker must have knowledge of an LDAP username that does not have the `sshPublicKey` property set. Third, 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). Version 1.2.0 fixes the issue. Weakness: CWE-287 (Improper Authentication) ## Which versions are affected by CVE-2025-27414? 3 open source packages ship an affected version, including github.com/minio/minio. | Package | Ecosystem | Affected | Fixed in | | --- | --- | --- | --- | | `github.com/minio/minio` | Go | All versions | None | | `github.com/minio/minio` | Go | From 0.0.0-20240605075113-91e1487de457 | 0.0.0-20250227184332-4c71f1b4ec0f | | `github.com/minio/minio` | Go | From 0.0.0-20240605075113-91e1487de457 | 0.0.0-20250227184332-4c71f1b4ec0f | ## How do I fix CVE-2025-27414? Upgrade github.com/minio/minio to 0.0.0-20250227184332-4c71f1b4ec0f or later. ## Is CVE-2025-27414 being exploited? There is no known exploitation of CVE-2025-27414 in the wild and no public exploit code. ## Fix prompt for AI coding agents ```text Check this codebase for CVE-2025-27414 and fix it if it is affected. What it is: CVE-2025-27414 is a medium-severity authentication bypass vulnerability in minio, published on 28 Feb 2025. An attacker can exploit it over the internet without logging in, with no action from the victim. Exploitation: There is no known exploitation of CVE-2025-27414 in the wild and no public exploit code. Affected packages and fixed versions: - github.com/minio/minio (Go): affected all versions; no fix listed - github.com/minio/minio (Go): affected from 0.0.0-20240605075113-91e1487de457; fixed in 0.0.0-20250227184332-4c71f1b4ec0f - github.com/minio/minio (Go): affected from 0.0.0-20240605075113-91e1487de457; fixed in 0.0.0-20250227184332-4c71f1b4ec0f Task: 1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies. 2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it. 3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead. 4. Run the tests and summarise what changed and why. 5. If nothing in the project is affected, say so and change nothing. Reference: https://insights.sbomify.com/CVE-2025-27414/ (Markdown: https://insights.sbomify.com/CVE-2025-27414/index.md) ``` ## Sources - CVE record: https://www.cve.org/CVERecord?id=CVE-2025-27414 - NVD: https://nvd.nist.gov/vuln/detail/CVE-2025-27414 - OSV: https://osv.dev/vulnerability/CVE-2025-27414 --- From sbomify Insights: https://insights.sbomify.com/CVE-2025-27414/ Summaries are generated and may contain mistakes; the official description above is the record.