CVE-2026-47846: bitnami/cassandra · Use of Hard-coded Credentials
Affects bitnami/cassandraSource CVE Database V5
Not known to be exploited · CVSS 9.8 Critical · fixed in 5.0.8-photon-5-r4 : patch bitnami/cassandra as a priority.
Data as of 1 Nov 2026, 22:58 UTC
- EPSS
- 0.4% chance of exploitation in 30 days – higher than 41% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
- Patch
- Available – fixed in 5.0.8-photon-5-r4, 4.1.11-photon-5-r7, 4.0.20-photon-5-r7
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:HExploitation evidence
Disclosed: evidence found.
CVE published 18 Jun 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponized: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors
A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 1 Nov 2026.
What to do
Upgrade bitnami/cassandra to 5.0.8-photon-5-r4, 4.1.11-photon-5-r7 or 4.0.20-photon-5-r7.
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| Bitnamibitnami/cassandra | Affected
| Fixed in
|
| Bitnamibitnami/cassandra | Affected
| Fixed in
|
| Bitnamibitnami/cassandra | Affected
| Fixed in
|
GitHubbitnami/cassandrapkg:github/bitnami/cassandraOther threats | Affected
| Fixed in– |
Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.
AI-suggested
If you cannot patch yet, users should avoid deploying affected versions or ensure that the default 'cassandra' superuser account is manually disabled or removed after container initialization. Monitoring for unauthorized access attempts using default credentials is recommended.
Description
Bitnami Cassandra container images contain a vulnerability where the default superuser account 'cassandra' is not removed when a custom administrator account is configured. This results in the default cassandra:cassandra superuser credentials remaining active, providing an unintended access path. The issue affects specific versions of the container images prior to fixed releases in the 4.0.x, 4.1.x, and 5.0.x series. The vulnerability has a critical severity with a CVSS score of 9.8.