High [CVE-2026-39944] RGW STS session tokens vulnerable to CBC bit-flip attack enabling admin privilege escalation
This high-severity Red Hat Linux advisory covers CVE-2026-39944 affecting Red Hat Ceph Storage 4, Red Hat Ceph Storage 5, Red Hat Ceph Storage 6.
Android app · Google Play
Monitor future Red Hat Linux CVEs from your phone.
Choose a whole vendor or a precise platform, then receive matching security advisories by phone notification, email, or both. Coverage follows 32 official vendor sources and 160+ reviewed platform categories.
Summary
A flaw was found in Ceph RGW's STS (Security Token Service) session token implementation. The STS tokens use the same unauthenticated AES-128-CBC encryption as CephX, which lacks message authentication and uses a hardcoded initialization vector.
Because there is no integrity protection on the tokens, an attacker who holds any valid unprivileged STS token can perform a CBC bit-flip attack to modify the token contents and escalate to full RGW admin privileges. This requires only that STS is enabled (rgw_s3_auth_use_sts = true) and that the attacker has a single valid STS token.
Successful exploitation grants complete control over the RGW service, including reading, writing, and deleting all objects and buckets. The Red Hat Product Security team has assessed the severity of this vulnerability as Important, given that it can be exploited over the network by any holder of a valid STS token without user interaction.
Successful exploitation allows an attacker to escalate from any unprivileged STS session to full RGW admin, gaining complete read, write, and delete access to all S3 objects and buckets. The vulnerability's root cause is the use of unauthenticated AES-128-CBC encryption in STS session tokens, sharing the same cryptographic weakness as CVE-2025-30156.
Weakness: CWE-327.
Affected versions
No affected-version range was extracted from the source record. The vendor advisory is authoritative — check it before change work.
Official advisory · high-confidence parse· fetched 1 hour ago·verify at source
Fixed versions
No fixed release is recorded yet. That does not prove no patch exists — confirm against the vendor advisory.
Official advisory · high-confidence parse· fetched 1 hour ago·verify at source
Mitigation checklist
- Mitigation for this issue is either not available or the currently available options don't meet the Red Hat Product Security criteria comprising ease of use and deployment, applicability to widespread installation base or stability.
Official advisory · high-confidence parse· fetched 1 hour ago·verify at source
Discussion(0)
No comments yet. Share field notes, upgrade gotchas, or questions — verify against the vendor advisory before acting on community advice.
Sign in to join the discussion.