/

CVE-2026-50152

Severity:

CRITICAL RISK

(9.1)

Improper Authorization (CWE-285) in Ceph Monitor Handler

CVE-2026-50152

Awaiting Analysis

Vulnerability type

Category:

Improper Authorization

CWE:

CWE-285

Impact:

Sensitive Information Disclosure and Privilege Escalation

Severity:

CRITICAL RISK

(9.1)

CVSS version:

3.1

Catch this CVE while code is being written

Detect vulnerable code directly in pull requests, so CVEs are fixed before merge.

Summary

Ceph's Monitor subscription handler may allow a CephX identity with only read-only monitor permissions to access the entire configuration-key store through a crafted subscription request. Because the store can contain disk-encryption passphrases and cluster-management SSH keys, successful exploitation could enable privilege escalation, host compromise, and full cluster takeover.

Affected context

The issue occurs in Ceph Monitor deployments where the subscription handler processes Monitor subscription messages without adequately checking whether the requesting CephX identity is authorized to read configuration-key data. It is particularly significant in environments where the configuration-key store contains OSD encryption secrets or cephadm management credentials. Exploitation depends on the affected handler being reachable by a low-privileged CephX account.

Exploit preconditions

  • Attack surface: Ceph Monitor subscription handling
  • Required access: A valid CephX identity with at least mon allow r capabilities
  • Trigger point: Processing of a crafted MMonSubscribe message
  • Why exploitation is possible: Authorization checks do not sufficiently restrict access to the configuration-key store, allowing a read-only identity to retrieve data beyond its intended privileges

Why this happens

The vulnerability results from an authorization boundary failure in the Monitor subscription handler. The handler permits a principal with limited monitor-read permissions to access configuration-key data without verifying that the requested store contents are within that principal's authorization scope. This maps to CWE-285: Improper Authorization, where an application fails to enforce the required permissions for a sensitive operation or resource.

Potential impact

  • Sensitive configuration secrets may be disclosed
  • OSD disk-encryption passphrases could be exposed
  • Ceph management SSH private keys could be obtained
  • An attacker could escalate from a read-only account to administrative control
  • Cluster nodes may be compromised through exposed management credentials
  • Storage data could be accessed, altered, or disrupted
  • The wider cluster and connected infrastructure could be affected

General mitigation guidance

Mitigation generally focuses on enforcing resource-level authorization for configuration-key operations and reducing the sensitivity of data available to low-privileged identities.

Common defensive patterns include:

  • Enforcing explicit permission checks before returning configuration-key contents
  • Separating read-only monitor access from access to sensitive configuration stores
  • Applying least-privilege CephX capabilities and removing unnecessary identities
  • Limiting the scope and privileges of cluster-management credentials
  • Storing secrets through mechanisms that provide isolation, rotation, and access auditing
  • Avoiding default configurations that grant host-wide administrative access when narrower privileges are practical
  • Monitoring and restricting access to Monitor service endpoints

How teams detect issues like this

Organizations can assess for this class of issue through:

  • Static and behavioral review of Monitor message handlers for missing authorization checks
  • Code review signals where capability checks are performed at the service level but not at the sensitive-resource level
  • Tests that verify read-only CephX identities cannot retrieve configuration-key contents
  • Policy checks requiring explicit authorization for secret-store access
  • Audit monitoring for unusual configuration-key reads or subscription requests from low-privileged identities
  • Automated security testing that exercises authorization boundaries across CephX capability profiles

Sources

SourceLink
github.comgithub.com/ceph/ceph/commit/d971bb2b6199f70b1708a20a63fa944ee7a94727
github.comgithub.com/ceph/ceph/commit/f2840d2fd338ab5de2865f0f78684bbf7b888c84
github.comgithub.com/ceph/ceph/security/advisories/GHSA-rg9p-5xcp-wm8h

Frequently asked

questions

It may be exploitable over the Ceph Monitor communication path when an attacker can connect as a valid CephX user and send a crafted subscription request. The exact reachability depends on network exposure and cluster access controls.

No. The described attack requires only a CephX identity with limited monitor-read capabilities, provided that the identity can reach an affected Monitor service.

Enforce explicit authorization checks for every configuration-key access and ensure that read-only monitor permissions cannot expose sensitive store contents. Defensive controls should also limit the value and scope of stored credentials.

Maintain capability-based authorization tests, review sensitive-resource access independently from general service access, minimize credential privileges, and audit Monitor requests and secret-store reads.

Find out what's already
exploitable in your codebase.