MinIO is a High Performance Object Storage, API compatible with Amazon S3 cloud storage service. Use MinIO to build high performance infrastructure for machine learning, analytics and application data workloads.

MinIO

minio:0.20251015.172955-20.2

bash

bash-sh

ca-certificates-mozilla-prebuilt

coreutils

filesystem

glibc

gpg-pubkey

libacl1

libattr1

libcap2

libgcc_s1

libgmp10

libncurses6

libpcre2-8-0

libreadline7

libselinux1

libstdc++6

mc-0

minio-0

skelcd-EULA-bci

sles-release

system-user-root

terminfo-base

An authenticated SSH client that repeatedly opened channels which were rejected by the server caused unbounded memory growth, eventually crashing the server process and affecting all connected users. Rejected channels are now properly removed from the connection's internal state and released for garbage collection.

CVE-2026-39827

Previously, a revoked 'SignatureKey' belonging to a CA was not correctly checked for revocation. Now, both the 'key' and 'key.SignatureKey' are checked for @revoked.

CVE-2026-42508

When adding a key to a remote agent constraint extensions such as restrict-destination-v00@openssh.com were not serialized in the request. Destination restrictions were silently stripped when forwarding keys, allowing unrestricted use of the key on the remote host. The client now serializes all constraint extensions. Additionally, the in-memory keyring returned by NewKeyring() now rejects keys with unsupported constraint extensions instead of silently ignoring them.

CVE-2026-39832

A malicious SSH peer could send unsolicited global request responses to fill an internal buffer, blocking the connection's read loop. The blocked goroutine could not be released by calling Close(), resulting in a resource leak per connection. Unsolicited global responses are now discarded.

CVE-2026-39830

When writing data larger than 4GB in a single Write call on an SSH channel, an integer overflow in the internal payload size calculation caused the write loop to spin indefinitely, sending empty packets without making progress. The size comparison now uses int64 to prevent truncation.

CVE-2026-39834

Previously, after a channel has been established, a malicious peer could send crafted messages that would deadlock the entire connection. Now, we handle all RFC 4254 channel messages; global requests are handled explicitly. Then, treat all other messages as a protocol error and tear the connection down instead of buffering and blocking.

CVE-2026-56855

When an SSH server authentication callback returned PartialSuccessError with non-nil Permissions, those permissions were silently discarded, potentially dropping certificate restrictions such as force-command after a second factor succeeded. Returning non-nil Permissions with PartialSuccessError now results in a connection error.

CVE-2026-39828

filippo.io/edwards25519 is a Go library implementing the edwards25519 elliptic curve with APIs for building cryptographic primitives. In versions 1.1.0 and earlier, MultiScalarMult produces invalid results or undefined behavior if the receiver is not the identity point. If (*Point).MultiScalarMult is called on an initialized point that is not the identity point, it returns an incorrect result. If the method is called on an uninitialized point, the behavior is undefined. In particular, if the receiver is the zero value, MultiScalarMult returns an invalid point that compares Equal to every other point. Note that MultiScalarMult is a rarely used, advanced API. For example, users who depend on filippo.io/edwards25519 only through github.com/go-sql-driver/mysql are not affected. This issue has been fixed in version 1.1.1.

CVE-2026-26958

Previously, a channel registered in the mux's chanList is not usable until it is established. A malicious peer was able flood the channel's incomingRequests, deadlocking the entire connection. Now, we add an atomic established state, set when a channel becomes usable. Until such a time, handlePacket drops every packet other than the open confirmation/failure, without blocking and without tearing down the connection.

CVE-2026-78662

The RSA and DSA public key parsers did not enforce size limits on key parameters. A crafted public key with an excessively large modulus or DSA parameter could cause several minutes of CPU consumption during signature verification. This could be triggered by unauthenticated clients during public key authentication. RSA moduli are now limited to 8192 bits, and DSA parameters are validated per FIPS 186-2.

CVE-2026-39829

Parsing an invalid SVCB or HTTPS RR can panic when the size of a parameter value overflows the message buffer.

CVE-2026-46600

SSH servers which use CertChecker as a public key callback without setting IsUserAuthority or IsHostAuthority could be caused to panic by a client presenting a certificate. CertChecker now returns an error instead of panicking when these callbacks are nil.

CVE-2026-39835

Previously, CVE-2024-45337 fixed an authorization bypass for misused ssh server configurations; if any other type of callback is passed other than public key, then the source-address validation would be skipped.

CVE-2026-46595

gRPC-Go is the Go language implementation of gRPC. Prior to 1.83.1, the xDS RBAC HTTP filter in internal/xds/httpfilter/rbac/rbac.go does not lowercase header matcher names in normalizeHeaderMatcher even though incoming metadata keys are lowercase. A DENY policy using a mixed-case name such as X-Role or User-Agent therefore does not match and fails open, allowing requests that should be rejected. The same case mismatch permits :Scheme or Grpc-Status to evade gRFC A41 validation and prevents Host from being rewritten to :authority. This issue is fixed in version 1.83.1.

CVE-2026-84303

amqp091-go is a Go AMQP 0.9.1 client. Before version 1.13.0, a compromised or malicious AMQP broker can force the client to allocate resources for and process content body frames that exceed the negotiated frame_max limit. This can lead to unexpected memory consumption or application-layer denial of service (DoS), bypassing the protocol's built-in framing constraints. Version 1.13.0 contains a fix. No known workarounds are available.

CVE-2026-79921

For certain crafted inputs, a 'ed25519.PrivateKey' was created by casting malformed wire bytes, leading to a panic when used.

CVE-2026-46598

compress provides various compression algorithms. Prior to version 1.18.7, a signed integer overflow vulnerability in s2.NewDict() allows an attacker to bypass repeat index validation by supplying a dictionary with a uvarint-encoded repeat value exceeding MaxInt64. When Dict.Encode() is subsequently called, the overflowed negative repeat value causes an out-of-bounds memory access via unsafe.Pointer arithmetic, crashing the process with SIGSEGV. This issue has been patched in version 1.18.7.

CVE-2026-63209

The Verify() method for FIDO/U2F security key types (sk-ecdsa-sha2-nistp256@openssh.com, sk-ssh-ed25519@openssh.com) did not check the User Presence flag. Signatures generated without physical touch were accepted, allowing unattended use of a hardware security key. To restore the previous behavior, return a "no-touch-required" extension in Permissions.Extensions from PublicKeyCallback.

CVE-2026-39831

OpenTelemetry-Go is the Go implementation of OpenTelemetry. From version 1.5.0 to 1.44.0, sdk/trace.NewTracerProvider emits a TracerProvider created internal Info-level diagnostic event whose MarshalLog implementations recursively include span processor, exporter, and client configuration. Applications that call otel.SetLogger to enable OpenTelemetry internal Info logging can therefore record OTLP gRPC and HTTP collector endpoints, the OTLP HTTP Insecure flag, and complete Zipkin collector URLs. A person or system with access to those logs can learn internal collector topology and can recover credentials or tokens embedded in Zipkin URL user information or query strings. The default OpenTelemetry logger does not emit the event, and this path does not log OTLP authentication headers, TLS key material, or span payloads. This issue is fixed in version 1.45.0.

CVE-2026-81870

The golang.org/x/crypto/openpgp package is unsafe by design, has numerous known security issues, is not maintained, and should not be used.

If you are required to interoperate with OpenPGP systems and need a maintained package, consider github.com/ProtonMail/go-crypto/openpgp which is a maintained fork that aims to be a drop-in replacement for this package.

GO-2026-5932

The Nickname profile can panic with an out-of-bounds slice error when transforming crafted input into a short destination buffer.

CVE-2026-56851

The source-address critical option in the Permissions returned by an authentication callback was only enforced for the PublicKeyCallback and VerifiedPublicKeyCallback paths, extending the fix for CVE-2026-46595. Permissions returned by the PasswordCallback, KeyboardInteractiveCallback, NoClientAuthCallback, and GSSAPIWithMICConfig.AllowLogin callbacks were not validated against the client's remote address, so a source-address restriction set by those callbacks was silently ignored. The check is now applied to the Permissions returned by any authentication callback.

CVE-2026-56854

An incorrectly placed cast from bytes to int allowed for server-side panic in the AES-GCM packet decoder for well-crafted inputs.

CVE-2026-46597

The in-memory keyring returned by NewKeyring() silently accepted keys with the ConfirmBeforeUse constraint but never enforced it. The key would sign without any confirmation prompt, with no indication to the caller that the constraint was not in effect. NewKeyring() now returns an error when unsupported constraints are requested.

ID	Severity	Package	Installed version	Fixed version
CVE-2026-77405	CRITICAL	Go github.com/rabbitmq/amqp091-go	v1.10.0	1.13.0
CVE-2026-77408	CRITICAL	Go github.com/rabbitmq/amqp091-go	v1.10.0	1.13.0
CVE-2026-77411	CRITICAL	Go github.com/rabbitmq/amqp091-go	v1.10.0	1.13.0
CVE-2026-43871	HIGH	Go github.com/apache/thrift	v0.23.0	0.24.0
CVE-2026-56852	HIGH	Go golang.org/x/text	v0.37.0	0.39.0
CVE-2026-77403	HIGH	Go github.com/rabbitmq/amqp091-go	v1.10.0	1.13.0
CVE-2026-77404	HIGH	Go github.com/rabbitmq/amqp091-go	v1.10.0	1.13.0
CVE-2026-77406	HIGH	Go github.com/rabbitmq/amqp091-go	v1.10.0	1.13.0
CVE-2026-77407	HIGH	Go github.com/rabbitmq/amqp091-go	v1.10.0	1.13.0
CVE-2026-77410	HIGH	Go github.com/rabbitmq/amqp091-go	v1.10.0	1.13.0
CVE-2026-77412	HIGH	Go github.com/rabbitmq/amqp091-go	v1.10.0	1.13.0
CVE-2026-78669	HIGH	Go golang.org/x/net	v0.55.0	0.60.0
CVE-2026-84304	HIGH	Go google.golang.org/grpc	v1.81.1	1.83.1
CVE-2026-84304	HIGH	Go google.golang.org/grpc	v1.79.3	1.83.1
CVE-2026-84445	HIGH	Go google.golang.org/grpc	v1.81.1	1.82.2, 1.83.2, 1.84.0-dev.0.20260825144003-d5a41119e0e3, 1.85.0-dev.0.20260825072537-93e31b48545e
CVE-2026-84445	HIGH	Go google.golang.org/grpc	v1.79.3	1.82.2, 1.83.2, 1.84.0-dev.0.20260825144003-d5a41119e0e3, 1.85.0-dev.0.20260825072537-93e31b48545e
GHSA-hrxh-6v49-42gf	HIGH	Go google.golang.org/grpc	v1.81.1	1.82.1
GHSA-hrxh-6v49-42gf	HIGH	Go google.golang.org/grpc	v1.79.3	1.82.1
CVE-2026-107386	MEDIUM	Go github.com/rabbitmq/amqp091-go	v1.10.0	1.14.0
CVE-2026-78659	MEDIUM	Go golang.org/x/net	v0.55.0	0.60.0
CVE-2026-78660	MEDIUM	Go golang.org/x/net	v0.55.0	0.60.0
CVE-2026-78663	MEDIUM	Go golang.org/x/net	v0.55.0	0.60.0
CVE-2026-97032	MEDIUM	Go golang.org/x/net	v0.55.0	0.60.0

minio:0.20251015.172955-20.2

Attestation