# CVE-2025-30156: Ceph: AES-CBC misuse in CephX and RADOSGW enables authentication bypass and credential forgery > Weak AES-CBC implementation in CephX allows attackers to forge credentials and escalate privileges to cluster-wide access. - **Severity:** High 8.9 (`CVSS:3.1/AV:A/AC:L/PR:L/UI:N/S:C/C:H/I:H/A:L`) - **Exploited in the wild:** Not known - **Login needed:** Any signed-in user - **Attackable:** Local or same network only - **Victim action needed:** Not needed - **Fix available:** Yes - **Published:** 27 Aug 2026 - **Updated:** 1 Sep 2026 - **Also known as:** AZL-98039, BIT-ceph-2025-30156, DEBIAN-CVE-2025-30156, ECHO-5896-cc77-aa09, GHSA-7q3q-3975-qw3q, MINI-7cjm-7pr8-cmr6, MINI-jqvh-r38x-qgc2, UBUNTU-CVE-2025-30156 ## What is CVE-2025-30156? CVE-2025-30156 is a high-severity vulnerability in ceph, published on 27 Aug 2026. It can only be exploited from the same machine or local network, with no action from the victim. ### Official description Ceph is an open-source distributed storage platform providing object, block, and file storage. In versions prior to 20.2.4 and 19.2.6, the CephX authentication protocol encrypts tickets with AES-128-CBC in an unauthenticated mode that uses a hard-coded initialization vector and no message authentication, allowing an attacker to forge credentials and gain cluster-wide access. Because the ciphertext is malleable and the monitor will encrypt attacker-chosen entity names, an attacker holding one low-privilege key and able to observe CephX traffic can use the monitor as an encryption oracle and splice ciphertext blocks into valid tickets for privileged entities such as Manager, MDS, and OSD. The same lack of authentication also lets an attacker with CephX permissions escalate privileges by flipping a single bit in a service ticket to set its allow_all field to true. This issue is fixed in versions 20.2.4 and 19.2.6. Weakness: CWE-327 (Use of a Broken or Risky Cryptographic Algorithm) ## Which versions are affected by CVE-2025-30156? 1 open source package ship an affected version, including ceph. | Package | Ecosystem | Affected | Fixed in | | --- | --- | --- | --- | | `ceph` | Bitnami | All versions | 19.2.6, 20.2.4 | ## How do I fix CVE-2025-30156? Upgrade ceph to a fixed version for your release line: 19.2.6 or 20.2.4. ## Is CVE-2025-30156 being exploited? There is no known exploitation of CVE-2025-30156 in the wild and no public exploit code. ## Fix prompt for AI coding agents ```text Check this codebase for CVE-2025-30156 and fix it if it is affected. What it is: CVE-2025-30156 is a high-severity vulnerability in ceph, published on 27 Aug 2026. It can only be exploited from the same machine or local network, with no action from the victim. Exploitation: There is no known exploitation of CVE-2025-30156 in the wild and no public exploit code. Affected packages and fixed versions: - ceph (Bitnami): affected all versions; fixed in 19.2.6, 20.2.4 Task: 1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies. 2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it. 3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead. 4. Run the tests and summarise what changed and why. 5. If nothing in the project is affected, say so and change nothing. Reference: https://insights.sbomify.com/CVE-2025-30156/ (Markdown: https://insights.sbomify.com/CVE-2025-30156/index.md) ``` ## Sources - CVE record: https://www.cve.org/CVERecord?id=CVE-2025-30156 - NVD: https://nvd.nist.gov/vuln/detail/CVE-2025-30156 - OSV: https://osv.dev/vulnerability/CVE-2025-30156 --- From sbomify Insights: https://insights.sbomify.com/CVE-2025-30156/ Summaries are generated and may contain mistakes; the official description above is the record.