Skip to content

[Bug] MinIO no longer releases new docker builds, and minio/minio:latest has a known vulnerability #2425

@miangraham

Description

@miangraham

Is there an existing issue for this?

  • Yes, I have searched the existing issues and none of them match my problem.

Product Variant

Self-Hosted

Current Behavior

minio/minio:latest has an unpatched disclosed vulnerability with no updates planned.

See:
https://github.com/minio/minio?tab=readme-ov-file#source-only-distribution
minio/minio#21647

I'm not sure what your official instance at rxresu.me is doing, but at the very least the self-hosting docs at https://docs.rxresu.me/product-guides/self-hosting-reactive-resume-using-docker which recommend image: minio/minio:latest at "9000:9000" will result in publicly exposed vulnerable instances if placed anywhere without an external firewall in front of them. I guess you also can't easily block the port as-is since it's used for direct downloads from the browser.

Expected Behavior

Given how MinIO maintainership has been behaving of late I think you'd probably be best served migrating to another compatible S3-like storage server. Failing that, maybe keep an eye out for community-built MinIO image repositories, or consider building your own from source.

It would probably also be a good idea to add a note to the self-hosting docs to make Really Extra Sure that the MinIO port is only exposed to private networks until the problem is well-solved.

Metadata

Metadata

Assignees

Labels

bugSomething isn't workingneeds triageIssues that need to be triagedv4Issues related to the latest version

Projects

No projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions