Vulnerability in cassandra (CVE-2026-47846)
Summary
Vulnerability in cassandra (CVE-2026-47846). Successful exploitation can lead to full system takeover. Mitigation: upgrade to 4.0.20-0, 4.1.11-0, 5.0.8-0 or later.
Original description
The description as published by the source.
Bitnami Cassandra container images are affected by a retained default superuser vulnerability. When a custom administrator account is configured via the CASSANDRA_USER environment variable, the container initialization script creates the new superuser account but fails to drop the built-in cassandra account in certain scenarios. This leaves the default cassandra:cassandra superuser active as an unintended access path. Any remote attacker who knows the default Cassandra credentials, can authenticate to the cluster as a full superuser regardless of the operator's configuration, bypassing the intent to replace the built-in account.
Source: NIST National Vulnerability Database NVD
Auto-generated summary
Assembled by SecPulse from the source data (CVSS, CWE, affected versions) using templates — no AI involved. Check the original description and references below for exact details.
A vulnerability tracked as CVE-2026-47846 has been found in cassandra.
Successful exploitation can lead to full system takeover. CVSS score: 9.8/10.
What to do: upgrade cassandra to 4.0.20-0, 4.1.11-0, 5.0.8-0 or later.
If unsure, ask your IT team or search "cassandra CVE-2026-47846" on the vendor's site.
CVE-2026-47846 (cassandra) — CWE-798 / CVSS v3 9.8
Attack vector: remote (network-reachable) / unauthenticated / no user interaction
Patched: 4.0.20-0, 4.1.11-0, 5.0.8-0 — apply immediately
Plan: 1) Audit SBOM/dependencies, 2) Stage→prod upgrade, 3) Add WAF/proxy monitoring on affected endpoints, 4) Hunt IOCs in logs.
Refs: see the GHSA / vendor advisory / patched release linked on this page.
A vulnerability (CWE-798) exists in cassandra.
Check the vendor advisory for the affected versions of cassandra.
Severity: Critical (CVSS 9.8/10). Successful exploitation can lead to full system takeover.
Update to 4.0.20-0, 4.1.11-0, 5.0.8-0.
Until the patch is applied: disable the affected feature, apply WAF rules, or restrict access via network ACLs.
Search webserver/proxy logs for unusual request patterns matching this CVE's known IOCs. Run grep -r 'cassandra' . against your dependency files (package-lock.json, requirements.txt, go.sum) to find affected services.
Response actions
Concrete steps and command examples for SOC/SRE teams to execute in order
-
1Identify exposure identify
grep -r 'cassandra' . | grep -v node_modulesリポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で
cassandraを grep し、稼働しているサービス・バージョンを把握する。 -
2Apply patch patch
Upgrade cassandra to 4.0.20-0, 4.1.11-0, 5.0.8-0ステージング環境で 4.0.20-0, 4.1.11-0, 5.0.8-0 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスを含めること。
-
3Post-deployment verification verify
Confirm patched version is live in productionパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番ではアクセスログ・WAF でアラート再発が無いか継続監視。
Affected packages
References
- web github.com