Information ExposureWeakness · CWE-200

CVE-2026-47136

MEDIUM · 6.9 CVSS v4.0 Published 2026-05-28
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
78/100
Remediation priority · High
Remotely reachable No privileges Zero-click

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.

NVD · unedited
RustFS is a distributed object storage system built in Rust. Prior to 1.0.0-beta.2, the RustFS console endpoint GET /rustfs/console/license returns parsed license metadata without requiring authentication. The endpoint is registered on the console listener and returns JSON containing license information such as the license subject and expiration timestamp. Any client that can reach the console listener can query this endpoint without credentials. This vulnerability is fixed in 1.0.0-beta.2.

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.

dbcve analysis · high confidence

The RustFS console endpoint GET /rustfs/console/license exposes license metadata including the license subject and expiration timestamp without requiring authentication. Any client that can reach the console listener can query this endpoint to retrieve sensitive licensing information.

MitigationUpgrade RustFS to version 1.0.0-beta.2 or later, which includes authentication requirements for the license endpoint. Until upgraded, restrict network access to the console listener.

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

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.

From the vector
Attack vector
Network
Complexity
Low
Privileges
None
Authentication
X
User interaction
None
Scope
X

CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:L/VI:N/VA:N/SC:N/SI:N/SA:N/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X

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.

dbcve checks

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

  1. Identify if RustFS is running
    Check for running RustFS processes or services, or identify if port 8080 (default console port) is listening. Commands: 'ps aux | grep rustfs' or 'netstat -tlnp | grep 8080'
    Affected if RustFS process is running and the console port is open
  2. Determine installed RustFS version
    Check the version of the installed RustFS binary or container image. Commands: 'rustfs --version' or 'docker images | grep rustfs'
    Affected if Version is before 1.0.0-beta.2 (vulnerable)
  3. Test console license endpoint accessibility
    Send an unauthenticated HTTP GET request to the console license endpoint. Command: 'curl http://<host>:8080/rustfs/console/license'
    Affected if Endpoint returns license metadata (subject, expiration) without requiring authentication
  4. Verify network exposure of console
    Check if the console listener is bound to 0.0.0.0 or an unrestricted interface. Inspect RustFS configuration files or running process environment variables for console bind address
    Affected if Console is accessible from untrusted network segments (not localhost or restricted VLAN)

User is affected if RustFS version is before 1.0.0-beta.2 AND the /rustfs/console/license endpoint returns license data without authentication

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

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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.

dbcve · scoped
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Upgrade RustFS to version 1.0.0-beta.2 or later, which includes authentication requirements for the license endpoint. Until upgraded, restrict network access to the console listener.

Recommended fix High confidence

1.0.0-beta.2

  1. Upgrade RustFS to version 1.0.0-beta.2 or later to resolve the authentication bypass vulnerability
  2. After upgrading, verify that the /rustfs/console/license endpoint now requires authentication before returning license metadata
  3. If using automated build/deployment tools, update the version specification in your dependency configuration to ^1.0.0-beta.2 or the latest stable release

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

Have this fixed Scoped from the published advisory
  • Consultation2.0 h
  • Implementation2.0 h
  • Testing2.0 h
  • Review / QA1.0 h
7.0 hours of engineering $1,240
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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

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

Primary sources

Practitioner notes

Contributed

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

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