CVE-2021-33923: Insecure permissions in Confluent Ansible (cp-ansible) 5.5.0, 5.5.1, 5.5.2 and 6.0.0 allows local attackers to
CVE-2021-33923 is a medium-severity flaw (CVSS 5.5) affecting cp-ansible. Below: why it ranks where it does, which versions are affected, what to do, and the exact commands.
Insecure permissions in Confluent Ansible (cp-ansible) 5.5.0, 5.5.1, 5.5.2 and 6.0.0 allows local attackers to access some sensitive information (private keys, state database).
Why this priority
- No elevated risk signals yet
No fix is published yet: follow the downgrade or mitigation steps.
Risk facts
| CVSS score | 5.5 (Medium) |
| Attack vector | Local |
| Attack complexity | Low |
| Privileges needed | Low |
| User interaction | None |
| EPSS exploit chance | 0.3% (top 78%) |
| CISA exploited list | No |
| Weakness | CWE-276 |
| Published | 2021-09-29 |
| Last modified | 2026-06-17 |
Last updated 2026-06-17 · Sources: CVE Program, NVD, CISA KEV, EPSS and vendor advisories · How we score
Am I affected?
Timeline
- Published CVE record published
- Updated Record last modified
Scores and fixes here are computed automatically from those and other public sources. Confirm with the vendor advisory before changing production systems.
Quick answers
How do I fix CVE-2021-33923?
cp-ansible: downgrade or apply the listed mitigation. Exact commands for each OS are on this page.
Is CVE-2021-33923 being exploited?
CVE-2021-33923 is not on the CISA Known Exploited Vulnerabilities list at the time of the last update. Check again, as this can change.
What does CVE-2021-33923 affect?
CVE-2021-33923 affects cp-ansible. Severity is medium (CVSS 5.5). Insecure permissions in Confluent Ansible (cp-ansible) 5.5.0, 5.5.1, 5.5.2 and 6.0.0 allows local attackers to access some sensitive information (private keys, state database).
How urgent is CVE-2021-33923?
Priority 25/100. No elevated risk signals yet.