Quick answers
- Is CVE-2026-50152 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-50152 being exploited in the wild.
- How severe is CVE-2026-50152?
- Critical severity, with a CVSS score of 9.1, published 28 August 2026.
- Which products and versions are affected?
- Ceph prior to 20.2.4 and 19.2.6.
- Is there a fix for CVE-2026-50152?
- No fixed version is recorded yet. Check the vendor's advisory in the references below. If you run it, Junglewise drafts a mitigation that fits your setup and applies it once you approve, with senior security engineers behind it.
- How is CVE-2026-50152 attacked?
- It is attacked over the network, in a hosted service.
- Am I affected by CVE-2026-50152?
- Check whether you run Ceph at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.
Technical details
The vulnerability is an authorization bypass in Ceph's Monitor subscription handler that fails to properly validate access to the config-key store. Any CephX user with only `mon allow r` (read) capabilities can send a crafted MMonSubscribe message to read the entire config-key store without proper permission checks. The store contains sensitive secrets including OSD LUKS disk-encryption passphrases and, in cephadm-managed clusters, SSH private keys used for cluster administration. This allows privilege escalation from a read-only account to full cluster and host compromise. The issue is fixed in Ceph versions 20.2.4 and 19.2.6.
Affected products
- Ceph Ceph prior to 20.2.4 and 19.2.6
Timeline
- 2026-08-28: disclosed: CVE-2026-50152 published on NVD