# CVE-2024-48916: Ceph is vulnerable to authentication bypass through RadosGW > Attackers can bypass authentication in Ceph RadosGW by sending JWTs with the 'none' algorithm, allowing unauthorized access to the storage system. - **Severity:** High 8.1 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:N`) - **Exploited in the wild:** Not known - **Login needed:** Any signed-in user - **Attackable:** Over the internet - **Victim action needed:** Not needed - **Fix available:** Yes - **Published:** 30 Jul 2025 - **Updated:** 30 Jul 2025 - **Also known as:** AZL-65996, AZL-66005, BIT-ceph-2024-48916, DEBIAN-CVE-2024-48916, GHSA-5g9m-mmp6-93mq, MGASA-2025-0011, OESA-2025-1206, OESA-2025-1207, OESA-2025-1208, OESA-2025-1209, RHSA-2024:10956, UBUNTU-CVE-2024-48916, USN-7182-1 ## What is CVE-2024-48916? CVE-2024-48916 is a high-severity authentication bypass vulnerability in ceph, published on 30 Jul 2025. Any signed-in user can exploit it over the network, with no action from the victim. ### Official description Ceph is a distributed object, block, and file storage platform. In versions 19.2.3 and below, it is possible to send an JWT that has "none" as JWT alg. And by doing so the JWT signature is not checked. The vulnerability is most likely in the RadosGW OIDC provider. As of time of publication, a known patched version has yet to be published. Weakness: CWE-345 (Insufficient Verification of Data Authenticity) ## Which versions are affected by CVE-2024-48916? 1 open source package ship an affected version, including ceph. | Package | Ecosystem | Affected | Fixed in | | --- | --- | --- | --- | | `ceph` | Bitnami | All versions | 20.2.1 | | `ceph` | Red Hat:ceph_storage:8.0::el9 | All versions | 2:19.2.0-55.el9cp | | `ceph-base` | Red Hat:ceph_storage:8.0::el9 | All versions | 2:19.2.0-55.el9cp | | `ceph-base-debuginfo` | Red Hat:ceph_storage:8.0::el9 | All versions | 2:19.2.0-55.el9cp | | `ceph-common` | Red Hat:ceph_storage:8.0::el9 | All versions | 2:19.2.0-55.el9cp | | `ceph-common-debuginfo` | Red Hat:ceph_storage:8.0::el9 | All versions | 2:19.2.0-55.el9cp | | `ceph-debuginfo` | Red Hat:ceph_storage:8.0::el9 | All versions | 2:19.2.0-55.el9cp | | `ceph-debugsource` | Red Hat:ceph_storage:8.0::el9 | All versions | 2:19.2.0-55.el9cp | | `ceph-exporter-debuginfo` | Red Hat:ceph_storage:8.0::el9 | All versions | 2:19.2.0-55.el9cp | | `ceph-fuse` | Red Hat:ceph_storage:8.0::el9 | All versions | 2:19.2.0-55.el9cp | | `ceph-fuse-debuginfo` | Red Hat:ceph_storage:8.0::el9 | All versions | 2:19.2.0-55.el9cp | | `ceph-immutable-object-cache` | Red Hat:ceph_storage:8.0::el9 | All versions | 2:19.2.0-55.el9cp | | `ceph-immutable-object-cache-debuginfo` | Red Hat:ceph_storage:8.0::el9 | All versions | 2:19.2.0-55.el9cp | | `ceph-mds-debuginfo` | Red Hat:ceph_storage:8.0::el9 | All versions | 2:19.2.0-55.el9cp | | `ceph-mgr-debuginfo` | Red Hat:ceph_storage:8.0::el9 | All versions | 2:19.2.0-55.el9cp | | `ceph-mib` | Red Hat:ceph_storage:8.0::el9 | All versions | 2:19.2.0-55.el9cp | | `ceph-mon-client-nvmeof-debuginfo` | Red Hat:ceph_storage:8.0::el9 | All versions | 2:19.2.0-55.el9cp | | `ceph-mon-debuginfo` | Red Hat:ceph_storage:8.0::el9 | All versions | 2:19.2.0-55.el9cp | | `ceph-osd-debuginfo` | Red Hat:ceph_storage:8.0::el9 | All versions | 2:19.2.0-55.el9cp | | `ceph-radosgw-debuginfo` | Red Hat:ceph_storage:8.0::el9 | All versions | 2:19.2.0-55.el9cp | | `ceph-resource-agents` | Red Hat:ceph_storage:8.0::el9 | All versions | 2:19.2.0-55.el9cp | | `ceph-selinux` | Red Hat:ceph_storage:8.0::el9 | All versions | 2:19.2.0-55.el9cp | | `ceph-test-debuginfo` | Red Hat:ceph_storage:8.0::el9 | All versions | 2:19.2.0-55.el9cp | | `cephadm` | Red Hat:ceph_storage:8.0::el9 | All versions | 2:19.2.0-55.el9cp | | `cephfs-mirror-debuginfo` | Red Hat:ceph_storage:8.0::el9 | All versions | 2:19.2.0-55.el9cp | | `cephfs-top` | Red Hat:ceph_storage:8.0::el9 | All versions | 2:19.2.0-55.el9cp | | `libcephfs-daemon-debuginfo` | Red Hat:ceph_storage:8.0::el9 | All versions | 2:19.2.0-55.el9cp | | `libcephfs-devel` | Red Hat:ceph_storage:8.0::el9 | All versions | 2:19.2.0-55.el9cp | | `libcephfs-proxy2` | Red Hat:ceph_storage:8.0::el9 | All versions | 2:19.2.0-55.el9cp | | `libcephfs-proxy2-debuginfo` | Red Hat:ceph_storage:8.0::el9 | All versions | 2:19.2.0-55.el9cp | | `libcephfs2` | Red Hat:ceph_storage:8.0::el9 | All versions | 2:19.2.0-55.el9cp | | `libcephfs2-debuginfo` | Red Hat:ceph_storage:8.0::el9 | All versions | 2:19.2.0-55.el9cp | | `libcephsqlite-debuginfo` | Red Hat:ceph_storage:8.0::el9 | All versions | 2:19.2.0-55.el9cp | | `librados-devel` | Red Hat:ceph_storage:8.0::el9 | All versions | 2:19.2.0-55.el9cp | | `librados-devel-debuginfo` | Red Hat:ceph_storage:8.0::el9 | All versions | 2:19.2.0-55.el9cp | | `librados2` | Red Hat:ceph_storage:8.0::el9 | All versions | 2:19.2.0-55.el9cp | | `librados2-debuginfo` | Red Hat:ceph_storage:8.0::el9 | All versions | 2:19.2.0-55.el9cp | | `libradospp-devel` | Red Hat:ceph_storage:8.0::el9 | All versions | 2:19.2.0-55.el9cp | | `libradosstriper1` | Red Hat:ceph_storage:8.0::el9 | All versions | 2:19.2.0-55.el9cp | | `libradosstriper1-debuginfo` | Red Hat:ceph_storage:8.0::el9 | All versions | 2:19.2.0-55.el9cp | ## How do I fix CVE-2024-48916? Upgrade ceph to 20.2.1 or later. ## Is CVE-2024-48916 being exploited? It is not confirmed as exploited in the wild, but public exploit code for CVE-2024-48916 exists. ## Fix prompt for AI coding agents ```text Check this codebase for CVE-2024-48916 and fix it if it is affected. What it is: CVE-2024-48916 is a high-severity authentication bypass vulnerability in ceph, published on 30 Jul 2025. Any signed-in user can exploit it over the network, with no action from the victim. Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2024-48916 exists. Affected packages and fixed versions: - ceph (Bitnami): affected all versions; fixed in 20.2.1 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-2024-48916/ (Markdown: https://insights.sbomify.com/CVE-2024-48916/index.md) ``` ## Sources - CVE record: https://www.cve.org/CVERecord?id=CVE-2024-48916 - NVD: https://nvd.nist.gov/vuln/detail/CVE-2024-48916 - OSV: https://osv.dev/vulnerability/CVE-2024-48916 --- From sbomify Insights: https://insights.sbomify.com/CVE-2024-48916/ Summaries are generated and may contain mistakes; the official description above is the record.