Information ExposureWeakness · CWE-200

CVE-2026-55188

HIGH · 8.2 CVSS v3.1 Published 2026-06-26

Mitigation only

No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.

See remediation →

88/100

Remediation priority · High

Remotely reachable Zero-click 8 weeks old

Official description

NVD · unedited

RustFS is a distributed object storage system built in Rust. From 1.0.0-alpha.1 until 1.0.0-beta.9, RustFS contains an authorization bypass in the bucket replication admin API. The ListRemoteTargetHandler handler for listing remote replication targets only checks whether request credentials exist, but does not verify that the caller has replication or administrator permissions. As a result, an authenticated user with no effective bucket or admin permissions can list remote replication target configuration for a bucket. Because the returned BucketTarget objects include remote target credentials, this can disclose replication access keys and secret keys. This vulnerability is fixed in 1.0.0-beta.9.

Technical summary

dbcve analysis · high confidence

RustFS versions 1.0.0-alpha.1 through 1.0.0-beta.8 contain an authorization bypass in the ListRemoteTargetHandler for the bucket replication admin API. The handler only verifies that request credentials exist but fails to validate that the caller has replication or administrator permissions, allowing any authenticated user to list remote replication target configuration and expose sensitive credentials.

MitigationUpgrade to RustFS version 1.0.0-beta.9 or later, which contains the fix for proper permission verification on the ListRemoteTargetHandler.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

CVSS breakdown

From the vector

Attack vector: Network
Complexity: High
Privileges: Low
User interaction: None
Scope: Changed
Confidentiality: High
Integrity: High
Availability: None

CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:C/C:H/I:H/A:N

Am I affected?

dbcve checks

Work through these to decide whether this CVE applies to you.

Check RustFS version

Run 'rustfs --version' or check the binary metadata to determine the installed version

Affected if Version is 1.0.0-alpha.1 through 1.0.0-beta.8 (inclusive)
Verify if replication admin API is enabled

Inspect the server configuration or API endpoint availability for /minio/admin/v3/replication/remotetarget/list or equivalent bucket replication admin endpoints

Affected if The replication target listing API endpoint is accessible on the server
Confirm authentication is configured

Check whether the server has authentication (IAM) enabled and users are authenticated

Affected if Users can authenticate to the system (authentication is not disabled)
Identify users with API access

Review which authenticated users or API keys have access to the replication-related admin endpoints

Affected if Any authenticated user exists in the system who could invoke the vulnerable ListRemoteTargetHandler API

A user is affected if RustFS version is between 1.0.0-alpha.1 and 1.0.0-beta.8, the bucket replication admin API is enabled, and there is any authenticated user in the system who could invoke the unauthorized endpoint.

Generated from the published advisory. Verify against your own configuration.

Remediation

dbcve · scoped

Mitigation available No clean upgrade yet — mitigate in the meantime

Mitigation

Upgrade to RustFS version 1.0.0-beta.9 or later, which contains the fix for proper permission verification on the ListRemoteTargetHandler.

Recommended fix High confidence

1.0.0-beta.9

Upgrade RustFS to version 1.0.0-beta.9 or later to resolve the authorization bypass vulnerability
After upgrading, verify that the ListRemoteTargetHandler now properly checks for replication or administrator permissions before returning bucket target information
Confirm that unauthenticated or unauthorized users can no longer access remote replication target configuration containing credentials

Generated from the published advisory — verify against the referenced sources before acting.

Have this fixed Scoped from the published advisory

Consultation2.0 h
Implementation4.0 h
Testing3.0 h
Review / QA2.0 h

11.0 hours of engineering $1,930

Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,088.

Scan for this in your stack

Free · runs locally

dbcve dependency scanner

Check whether your project pulls in CVE-2026-55188 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References

Primary sources

github.com
nvd.nist.govNVD record

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2026-55188 in production — separate from our analysis above.

Notes0 Guidelines

Know something about CVE-2026-55188?

The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.

The version that genuinely resolved it — not the one the vendor claimed
A config change or rule that shut the vector down
A gotcha in the upgrade path that cost you an afternoon

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here

Verified mitigations, workarounds, and config changes
Version or environment caveats, and links to real fixes
No weaponised exploit code, or anything meant to cause harm
No spam, self-promotion, credentials, or personal data

At a glance

A fix existsA vendor remedy is published

Severity 8.2 High

Exploit likelihood EPSS, next 30 days 0.2%

Remediation

A high-priority fix

Have this fixed 11 hrs · Moderate

Typical engagement from $1,930

Get a fix See the full breakdown ↓

A high-priority vulnerability. Send your environment and a specialist will scope CVE-2026-55188 and return a fixed quote and timeline.

You’ll deal with our team directly and deploy the reviewed fix to staging first — never straight to production.

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

Check your environment

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

Scan for this in your stack

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Practitioner notes

No notes yet

Official description

Technical summary

CVSS breakdown

Am I affected?

Remediation

References