CubeFS leaks magic secret key when starting Blobstore access service

Exploitation

No confirmed exploitation recorded. Patch Next marks exploitation only from CISA KEV.

CVSS 4.0

5.1 · CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:P/VC:L/VI:L/VA:L/SC:N/SI:N/SA:N · score source

EPSS

• CVE-2023-46741: 0.30% estimated exploitation activity in the next 30 days; percentile 22.92 (FIRST EPSS, 2026-11-03). This is a model estimate, not proof of exploitation or customer exposure.

As published by the source; long descriptions are shortened.

A vulnerability was found in CubeFS that could allow users to read sensitive data from the logs which could allow them escalate privileges. CubeFS leaks configuration keys in plaintext format in the logs. These keys could allow anyone to carry out operations on blobs that they otherwise do not have permissions for. For example, an attacker that has succesfully retrieved a secret key from the logs can delete blogs from the blob store. The attacker can either be an internal user with limited privileges to read the log, or it can be an external user who has escalated privileges sufficiently to access the logs. There is no evidence of this vulnerability being exploited in the wild. It was found during an ongoing security audit carried out by Ada Logics in collaboration with OSTIF and the CNCF. The vulnerability has been patched in v3.3.1. There is no other mitigated than upgrading.

Published by the source

3 Jan 2024, 16:14 UTC

Last modified by the source

7 Aug 2024, 05:01 UTC

Source last checked

26 Oct 2026, 15:04 UTC

1. Revision 1 · created · 26 Oct 2026

   Published from ghsa record GHSA-8h2x-gr2c-c275

Preview the exact text before you copy it. Commands are read-only suggestions; review them before running anything.

# Patch Next advisory brief: CVE-2023-46741

Advisory: CubeFS leaks magic secret key when starting Blobstore access service
IDs: CVE-2023-46741, GHSA-8h2x-gr2c-c275
Record: https://patchnext.com/advisories/cve-2023-46741 (revision 1, source checked 26 Oct 2026, 15:04 UTC)
Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected.
Severity: Medium (CVSS 5.1)
Exploitation: no confirmed exploitation recorded. Patch Next confirms exploitation only from CISA KEV.
Vendor response: Vendor fix available; fixed versions by package: github.com/cubefs/cubefs 3.3.1. A vendor fix does not mean a deployment is fixed.

## Affected components
- Go github.com/cubefs/cubefs: affected < 3.3.1; fixed in 3.3.1

## Suggested inspection (read-only)
- Go github.com/cubefs/cubefs: check the installed version with your package manager.

## Supported action
Upgrade each affected component to a fixed version on its release line. For a transitive dependency, upgrade the parent package or add an override or constraint, then regenerate the lockfile. Redeploy every environment that ran an affected version.

## Required regression checks
- Run the test suite and a production build.
- Exercise the features that depend on github.com/cubefs/cubefs.
- Repeat the inspection and confirm that only fixed versions remain installed.

## Rollback considerations
- Keep the previous lockfile and deployment artifact. Rolling back reinstates the vulnerable version, so apply any documented mitigation while you fix forward.

## Unresolved questions
- Which deployments run an affected version?
- Exploitation status can change. Check again before lowering the priority.
- Mark the work resolved only after the fixed version is verified in production.

## Sources
- Verified: https://github.com/advisories/GHSA-8h2x-gr2c-c275 (GitHub-reviewed advisory GHSA-8h2x-gr2c-c275 lists affected ranges: Go github.com/cubefs/cubefs >=0 <3.3.1)

Commands are suggestions: review each one before running it.