MinIO allows an SFTP authentication bypass due to improperly trusted SSH key

Exploitation

No confirmed exploitation recorded. Patch Next marks exploitation only from CISA KEV.

CVSS 4.0

6.3 · CVSS:4.0/AV:N/AC:H/AT:P/PR:N/UI:N/VC:L/VI:L/VA:N/SC:N/SI:N/SA:N · score source

EPSS

• CVE-2025-27414: 0.59% estimated exploitation activity in the next 30 days; percentile 48.08 (FIRST EPSS, 2026-11-03). This is a model estimate, not proof of exploitation or customer exposure.

As published by the source; long descriptions are shortened.

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: 1. MinIO server must be configured to allow SFTP access and use LDAP as an…

Published by the source

3 Mar 2025, 19:56 UTC

Last modified by the source

3 Mar 2025, 19:56 UTC

Source last checked

26 Oct 2026, 15:09 UTC

1. Revision 1 · created · 26 Oct 2026

   Published from ghsa record GHSA-wc79-7x8x-2p58

Preview the exact text before you copy it. Commands are read-only suggestions; review them before running anything.

# Patch Next advisory brief: CVE-2025-27414

Advisory: MinIO allows an SFTP authentication bypass due to improperly trusted SSH key
IDs: CVE-2025-27414, GHSA-wc79-7x8x-2p58
Record: https://patchnext.com/advisories/cve-2025-27414 (revision 1, source checked 26 Oct 2026, 15:09 UTC)
Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected.
Severity: Medium (CVSS 6.3)
Exploitation: no confirmed exploitation recorded. Patch Next confirms exploitation only from CISA KEV.
Vendor response: Vendor fix available; fixed versions by package: github.com/minio/minio 0.0.0-20250227184332-4c71f1b4ec0f. A vendor fix does not mean a deployment is fixed.

## Affected components
- Go github.com/minio/minio: affected >= 0.0.0-20240605075113-91e1487de457, < 0.0.0-20250227184332-4c71f1b4ec0f; fixed in 0.0.0-20250227184332-4c71f1b4ec0f

## Suggested inspection (read-only)
- Go github.com/minio/minio: check the installed version with your package manager.

## Supported action
Upgrade each affected component to a fixed version on its release line. For a transitive dependency, upgrade the parent package or add an override or constraint, then regenerate the lockfile. Redeploy every environment that ran an affected version.

## Required regression checks
- Run the test suite and a production build.
- Exercise the features that depend on github.com/minio/minio.
- Repeat the inspection and confirm that only fixed versions remain installed.

## Rollback considerations
- Keep the previous lockfile and deployment artifact. Rolling back reinstates the vulnerable version, so apply any documented mitigation while you fix forward.

## Unresolved questions
- Which deployments run an affected version?
- Exploitation status can change. Check again before lowering the priority.
- Mark the work resolved only after the fixed version is verified in production.

## Sources
- Verified: https://github.com/advisories/GHSA-wc79-7x8x-2p58 (GitHub-reviewed advisory GHSA-wc79-7x8x-2p58 lists affected ranges: Go github.com/minio/minio >=0.0.0-20240605075113-91e1487de457 <0.0.0-20250227184332-4c71f1b4ec0f)

Commands are suggestions: review each one before running it.