Skip to content

Releases

r6

Choose a tag to compare

@github-actions github-actions released this 30 Oct 15:15

Impreza S3 Server r6: the fork renamed (module github.com/imprezahost/impreza-s3-server, binary impreza-s3-server). Binaries only; the legacy browser Console is removed; security contact and maintenance deadlines are in SECURITY.md and MAINTENANCE.md. Server behaviour and the MINIO_* configuration are unchanged from r4.

  • Source commit: d21a54d49159230bb0411d485ff938eb8621bff3
  • Upstream base commit: 9e49d5e7a648f00e26f2246f4dc28e6b07f8c84a
  • Go toolchain: go1.26.10
  • Each binary was built twice in CI (byte-identical) and rebuilt independently by the maintainer with the same result.

Verify before use. Use the public key and the sums published outside GitHub, not this page alone:

minisign -V -p minisign.pub.txt -m SHA256SUMS
minisign -V -p minisign.pub.txt -m impreza-s3-server-linux-amd64
sha256sum --check SHA256SUMS

There is no r5 release: the r5 tag was created on a commit outside main by mistake and the release workflow refused it.

impreza-s3-server r4 (29af40558eac)

Choose a tag to compare

@imprezahost imprezahost released this 27 Oct 12:41

Security maintenance release of the MinIO server fork. It fixes an Object Lock retention bypass, stops the server from contacting a third party, and changes how the client address is determined. Read the compatibility notes before upgrading.

Security changes

These have no CVE identifier.

Area Change
Object Lock default retention A PUT, copy or multipart upload that carries x-amz-object-lock-legal-hold (ON or OFF) now inherits the bucket's default retention. Before, any legal-hold header suppressed it.
PutObjectRetention authorization s3:PutObjectRetention is required and is evaluated before any object state is read. s3:BypassGovernanceRetention alone no longer sets or shortens retention.
Writes that name a version A version whose lock state cannot be read is no longer treated as unlocked, and an unexpired GOVERNANCE version blocks the write like a COMPLIANCE one.
Update check The server no longer contacts dl.min.io at startup, and in-place update (mc admin update) is removed. Both revealed the server address, version, OS and architecture to a third party.
Source address X-Forwarded-For, X-Real-IP and Forwarded are ignored by default, so a client can no longer choose the address seen by aws:SourceIp, audit and logs.

Robustness fixes backported from SILO

Error joining over the full error list, reader buffer mapping when preferred readers are reordered, erasure fields reset when a legacy xl.meta header is decoded, and conditional multipart completion evaluated across pools under the object lock. Credits are in NOTICE.

Compatibility

  • Behind a reverse proxy or load balancer, every request now appears to come from the proxy. Set _MINIO_API_XFF_HEADER=on only if every request reaches the server through a proxy that overwrites all three headers. Do not turn it on for an onion service.
  • MINIO_UPDATE is ignored and mc admin update answers MethodNotAllowed. Update by replacing the binary.
  • Callers that relied on s3:BypassGovernanceRetention alone to change retention now need s3:PutObjectRetention too.
  • The browser Console stays disabled by default, as in r2.

Reproducible build (linux/amd64)

  • Source commit: 29af40558eac20a5de865ffd5d197b5387adc40e
  • Toolchain: go1.26.10
  • SHA-256 of minio: 3a5aa2ad7e15110249d4d0458801100372fadf6e098f1933a47dd0cbe967a03b

To verify, follow the build steps in the README (two independent builds with engineering/build/build.sh, then engineering/build/compare.sh) and compare the SHA-256 above.

No binary is attached: build it from source and check the hash.

Security reports: see SECURITY.md.

impreza-s3-server r2 (6e9f993c4fa4)

Choose a tag to compare

@imprezahost imprezahost released this 26 Oct 20:16

Security maintenance release of the MinIO server fork. It fixes eight server vulnerabilities, mitigates a ninth, and changes the default of the embedded browser Console. Read the compatibility notes before upgrading.

Security changes

Advisory Component and change
CVE-2026-39414 S3 Select: CSV and JSON Lines records over 1 MiB are refused (OverMaxRecordSize).
CVE-2026-41145 Unsigned-trailer PUT and multipart: query-string credentials are refused for this upload mode.
CVE-2026-40344 Snowball (PutObjectExtract): unsigned-trailer uploads are authenticated before extraction.
CVE-2026-42600 Internode storage: ReadMultiple is removed; storage-REST paths and erasure metadata are validated.
CVE-2026-97731 SigV4 and CopyObject: unsigned x-amz-* headers and repeated x-amz-copy-source are refused.
CVE-2026-33322 OpenID Connect STS: HMAC-signed tokens are no longer accepted.
CVE-2026-33419 LDAP STS: uniform answers for unknown users and wrong passwords; logins are throttled per source.
CVE-2026-34204 Replication metadata headers: internal replication headers are trusted only from authorized replicas.

CVE-2026-113466 is mitigated, not fixed. The browser Console is now disabled by default. This is a breaking change for installations that relied on the implicit default. S3 API access is unchanged. To use the Console, set MINIO_BROWSER=on explicitly and restart: this restores exposure to the unresolved Console vulnerability and prints a warning. If you enable it, restrict network access to the Console port and use strong, unique root credentials. Installations that already set MINIO_BROWSER=on keep the Console enabled until they remove that setting.

Other compatibility changes: a 1 MiB S3 Select record limit, LDAP login throttling, rejection of OIDC HS* tokens, stricter signing of x-amz-* request headers, and policy conditions bound to the effective request values. Test your identity providers and S3 clients before upgrading. See SECURITY.md for details and the remaining known difference.

Most fixes are backported from SILO (AGPLv3), by Feng Ruohang and SILO contributors; see NOTICE.

Reproducible build (linux/amd64)

  • Source commit: 6e9f993c4fa4c4d3e486081e5401abcf56d115d0
  • Toolchain: go1.26.10
  • SHA-256 of minio: 41fc51e46afb27a73e48607f91c41a0b6ca438a6a3842436d0a63b360ee2358f

No binary is attached. Build it yourself and compare: follow the README (two independent builds with engineering/build/build.sh, then engineering/build/compare.sh) and check the SHA-256 above. The recipe embeds the source commit in the executable, so a different commit gives a different checksum. Vulnerability scanners do not certify that every server vulnerability is resolved.

Upgrade

Back up object data, configuration, credentials, IAM policies and external encryption keys with your usual recovery procedure. Build and verify the binary, replace it, restart, and check that the server, your clients and identity providers work. Keep the previous binary until you have confirmed the upgrade.

Report security issues through the channel in SECURITY.md.

impreza-s3-server r1 (6aa26ab8f771)

Choose a tag to compare

@imprezahost imprezahost released this 25 Oct 20:27

Security-maintenance build of the MinIO server, from upstream commit 9e49d5e with updated dependencies and Go 1.26.10. This is the build Impreza Host runs for its S3 service.

Reproducible build (linux/amd64)

  • Source commit: 6aa26ab8f771b3ea84ffe417a1f710fc0fd86e58
  • Toolchain: go1.26.10
  • SHA-256 of minio: b0a04862d9ac3a32c9e38c33e4486c1e4c85ac4ab845fcc2ee4cf7eb77ed75ca

To verify, follow the build steps in the README (two independent builds with engineering/build/build.sh, then engineering/build/compare.sh) and compare the SHA-256 above.

No binary is attached: build it from source and check the hash.

Security reports: see SECURITY.md.