Skip to main content

Ceph CephX CVE-2025-30156

HIGH
Use of a Broken or Risky Cryptographic Algorithm (CWE-327)
2026-08-19
8.9
CVSS 3.1 · Vendor
View

Attack ChainAIDerived

Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain

  1. Recon
    Obtain any valid CephX credential
  2. Delivery
    Gain adjacency to Ceph messenger network
  3. Exploit
    Capture encrypted CephX authentication traffic
  4. Install
    Identify plaintext structure via deterministic IV-fixed ciphertexts
  5. C2
    Compute CBC bit-flip deltas for target scope fields
  6. Execute
    Submit forged authentication token with expanded credential scope
  7. Impact
    Access cluster resources beyond original authorization

Vulnerability Assessment

Weakness
CWE
OWASP Top 10:2025
A04:2025 - Cryptographic Failures
ASVS 5.0
V11 - Cryptography Approved algorithm selection
Exploitation Conditions

The attacker must have network adjacency to the Ceph internal messenger network, which is the private storage network over which Ceph daemons and clients communicate - this network is typically isolated from the internet but reachable from any authorized storage client host, hypervisor, or compromised internal system. At least one valid CephX credential is required (PR:L); the credential may have minimal capabilities (e.g., a client key with restricted caps), as the attack modifies the credential scope fields in transit or in captured tokens rather than requiring a privileged starting point. CephX is the default and ubiquitous authentication mechanism in Ceph - no non-default configuration or optional feature needs to be enabled. Exploitation is bounded by the adjacent-network requirement: attackers without access to the Ceph storage network cannot exploit this remotely. No user interaction is required.

Impact

The vendor-confirmed CVSS score of 8.9 (AV:A/AC:L/PR:L/UI:N/S:C/C:H/I:H/A:L) accurately characterizes the threat profile: attack vector is adjacent-network only (the Ceph internal messenger network, not the internet), any valid CephX account is sufficient, no user interaction is needed, and the scope change reflects that a minimally privileged attacker can expand their credential reach across the cluster. EPSS data is absent from the provided intelligence, and the vulnerability is not listed in CISA KEV, indicating no confirmed active exploitation at time of analysis. However, the underlying technique - CBC bit-flipping with a known or guessable plaintext structure - is well-documented in academic literature and requires no novel research, lowering the practical exploitation barrier for a capable attacker who already has Ceph network access. Even a mid-sized municipal IT team in zabrze operating a Ceph cluster for block storage or backup infrastructure should treat this as urgent, since the credential escalation path could expose LUKS passphrases and SSH keys if the cluster also runs cephadm. The adjacent-network attack vector meaningfully limits internet-scale exposure, but any internal host on the storage network - a compromised hypervisor, a misconfigured client, or a malicious insider - has the required adjacency. The combination of low attack complexity, no required user interaction, and high confidentiality and integrity impact makes this a genuine priority for Ceph operators, not a theoretical risk inflated by CVSS.

Exploit ScenarioDerived

An attacker who has obtained a low-privilege CephX service key - for example, a client key with minimal caps granted to a backup agent - and who can reach the Ceph messenger network from a compromised host captures encrypted CephX authentication exchanges. Exploiting the hardcoded IV, they identify deterministic ciphertext patterns corresponding to known plaintext fields in the credential structure. Using CBC bit-flip arithmetic against a previously captured authentication token, they craft a modified ciphertext whose decryption expands the credential scope fields, then present the forged token to authenticate with elevated cluster permissions - accessing OSD data or monitor commands beyond their original grant.

This Week Schedule remediation this week. Why: HIGH severity (CVSS 7.0-8.9).
1 PoC candidate (unverified) No patch listed yet 0.1% exploitation probability (EPSS)

Get an e-mail when this CVE is exploited, patched or re-scored. Free account.

Alert me

AnalysisAIv1 – Aug 19, 2026

Broken cryptography in Ceph's CephX authentication subsystem enables credential scope escalation and plaintext inference for any network-adjacent attacker holding a compromised Ceph account. CephX employed AES-CBC with a hardcoded initialization vector and no message authentication code, making encrypted authentication traffic both deterministic (identical plaintexts yield identical ciphertexts) and malleable (bit-flip attacks alter decrypted credential payloads undetected). Fixed in Ceph Tentacle 20.2.4 and Squid 19.2.6 by replacing the scheme with AES-256-CTS-HMAC-SHA384-192; no public exploit has been identified at time of analysis.

RemediationAI

Upgrade to Ceph Tentacle 20.2.4 or Ceph Squid 19.2.6, which replace the vulnerable AES-CBC scheme with AES-256-CTS-HMAC-SHA384-192 across all CephX authentication paths; partial or rolling upgrades that leave any daemons on vulnerable versions should be avoided as the cryptographic changes require full fleet consistency. Release tags and artifacts are at https://github.com/ceph/ceph/releases/tag/v20.2.4 and https://github.com/ceph/ceph/releases/tag/v19.2.6, with the full advisory at https://docs.ceph.com/en/latest/security/CVE-2025-30156/. Until patching is complete, isolate the Ceph messenger network (monitor default port 6789; OSD ports 6800-7300) via firewall rules or VLAN segmentation to block adjacency from any host not authorized for cluster access - this eliminates the AV:A attack vector as a compensating control, at the cost of operational complexity in environments with broad storage-network access. After patching, rotate all CephX credentials, as any key active during the vulnerable period could have been observed or its scope altered undetected.

Affected ProductsAI

All Ceph releases across the Tentacle (20.x) and Squid (19.x) branches prior to the fixed versions are affected, as the vulnerable AES-CBC implementation was present in the CephX authentication layer used by all standard Ceph deployments. No CPE strings were included in the provided intelligence data, but the vulnerability applies to the CephX subsystem present in all deployments where Ceph messenger-based authentication is in use - which is the default. Fixed versions are Tentacle 20.2.4 (https://github.com/ceph/ceph/releases/tag/v20.2.4) and Squid 19.2.6 (https://github.com/ceph/ceph/releases/tag/v19.2.6). The Ceph security advisory is available at https://docs.ceph.com/en/latest/security/CVE-2025-30156/ and the GitHub Security Advisory at https://github.com/ceph/ceph/security/advisories/GHSA-rmjq-ffrm-j6vj.

Affects your stack

Find out whether the stacks and servers you run are on an affected version.

Checking this CVE against your own stacks and servers is part of the Basic plan and up.

Technical ContextAI · show details

CephX is Ceph's native challenge-response authentication protocol, conceptually analogous to Kerberos, governing all daemon-to-daemon and client-to-cluster authentication over the internal Ceph messenger network. The cryptographic flaw mirrors the vulnerability class documented in the MIT 'Perils of Kerberos 4' paper (NDSS 2004): AES-CBC operated with a static, hardcoded IV and without a MAC or HMAC. A fixed IV eliminates semantic security - identical plaintext blocks always encrypt to identical ciphertext blocks, enabling traffic analysis. The absence of authenticated encryption (AE/AEAD) enables CBC malleability: an attacker can XOR a targeted byte in a known ciphertext block to produce a predictable, controlled change in the next decrypted plaintext block, permitting credential scope field manipulation without detection. The root cause maps to CWE-327 (Use of a Broken or Risky Cryptographic Algorithm) and CWE-329 (Not Using a Random IV with CBC Mode). The remediation - AES-256-CTS-HMAC-SHA384-192 - provides both confidentiality (CTS mode) and integrity (HMAC-SHA384) and required coordinated changes across Ceph userspace daemons and upstream Linux kernel support.

Know when the next one hits your stack

  • Watch products and get an email when something new is published
  • Check this CVE against your own stack and servers
  • Exploit and PoC references, threat intelligence from 22 sources

No credit card · 7-day full trial

Severity by source

Vendor (CNA) PRIMARY 8.9 HIGH
AV:A/AC:L/PR:L/UI:N/S:C/C:H/I:H/A:L
vuln.today AI 8.9 HIGH

Attack confined to the Ceph messenger network (AV:A); any valid CephX account suffices (PR:L); scope change reflects credential escalation across cluster boundaries beyond the initial account.

3.1 AV:A/AC:L/PR:L/UI:N/S:C/C:H/I:H/A:L
4.0 AV:A/AC:L/AT:N/PR:L/UI:N/VC:H/VI:H/VA:L/SC:H/SI:H/SA:L
SUSE HIGH
Red Hat 8.7 HIGH

Primary rating from Vendor (CNA).

CVSS VectorVendor

Attack Vector
Adjacent
Attack Complexity
Low
Privileges Required
Low
User Interaction
None
Scope
Changed
Confidentiality
High
Integrity
High
Availability
Low

Lifecycle Timeline

2
CVSS changed
Aug 28, 2026 - 00:22 NVD
8.9 (HIGH)
CVE Published
Aug 19, 2026 - 18:58 oss-security
HIGH

Description PRE-NVD

Disclosed via oss-security. NVD scoring and full description are pending.

Latest POC

1 PoC candidate from github (unverified)

Sign in to open the public PoC links collected for this CVE.

Executive ViewAI

Why It Matters

Ceph's CephX authentication subsystem contains a critical cryptographic flaw that allows network-adjacent attackers with compromised cluster credentials to escalate privileges and recover plaintext authentication data. Organizations operating Ceph storage clusters face immediate risk to cluster security and data access controls; this vulnerability requires priority patching to maintain authentication integrity and prevent lateral movement within cluster operations.

Business Impact: High
Compensating Controls

Vendor-released patch: Ceph Tentacle 20.2.4, Squid 19.2.6. Until upgrade is complete, restrict cluster network access to trusted administrative networks, audit and rotate all Ceph user credentials, disable cross-cluster authentication where feasible, and monitor CephX traffic for anomalous patterns.

Threat Intelligence Overview

EPSS Score
0.1%
Top 99% exploitable
Prevalence
Medium
deployed in enterprise, cloud, and OpenStack storage stacks
Threat Intel
1
1 sources
Data Quality
5 sources
Confidence: Medium

How this decision was reached

The engine reads each signal below and applies a fixed list of rules from top to bottom. The first rule that matches sets the recommended action – like a statement, every line is shown.

SignalValue
Severity HIGH
CISA KEV No
Public POC Yes
EPSS 0.1%
Patch available No
Active threat No
Deciding rule
HIGH severity (CVSS 7.0-8.9)
What every action level means
Emergency Immediate action required. Criteria: CRITICAL + in CISA KEV (actively exploited) without patch, OR CRITICAL + EPSS > 30% without patch, OR CRITICAL + active threat signals without patch.
Act Now Prioritize within 24-48h. Criteria: in KEV with patch available, OR CRITICAL + public POC, OR HIGH + EPSS > 10%, OR CRITICAL + active threat, OR any CRITICAL severity.
This Week Schedule remediation this week. Criteria: HIGH severity (CVSS 7.0-8.9). Patch within normal change window.
This Month Plan within 30 days. Criteria: MEDIUM severity (CVSS 4.0-6.9), lower exploitation probability. Include in regular patch cycle.
Monitor Track and reassess. Criteria: LOW severity (CVSS 0.1-3.9), minimal exploitation risk. No immediate action needed.

SSVC AssessmentENISA

SSVC Decision· derived
Scheduled
Exploitation· derived
Poc
System Exposure· derived
Controlled
Automatable· derived
No
Human Impact
High

Priority Score

64
Low Medium High Critical
KEV: 0
EPSS: 0
CVSS: +44
PoC: +20
Weaponized: 0
Threat intel: 0
Gov advisory: 0

Attack Technique

Privilege escalation occurs when an attacker leverages flaws in access control mechanisms to gain permissions beyond what they were originally granted.

Vendor StatusVendor

SUSE

Severity: Important
Product Status
SUSE Linux Enterprise Desktop 15 SP7 Not-Affected
SUSE Linux Enterprise Micro 5.3 Not-Affected
SUSE Linux Enterprise Micro 5.4 Not-Affected
SUSE Linux Enterprise Micro 5.5 Not-Affected
SUSE Linux Enterprise Module for Basesystem 15 SP7 Not-Affected

This site uses cookies essential for authentication and security. No tracking or analytics cookies are used. Privacy Policy