Confluent confluent-kafka
Confluent Kafka Python Improper TLS Certificate Validation
Confluent Kafka Python client's HashiCorp Vault KMS integration could allow a remote attacker to obtain sensitive information due to improper TLS certificate validation.
Affected versions and mitigation
From the CVE record and the vendor's references.Affected
- <= 2.14.2
Mitigation
* confluent-kafka (Python): This issue has been addressed in confluent-kafka (Python) 2.15.0, which: * Enables TLS certificate verification by default. * Exposes configuration to supply a custom CA bundle and an optional client certificate for mutual TLS, through both driver configuration and standard Vault environment variables: * ssl.ca.location (or environment variable VAULT_CACERT): CA bundle used to verify the Vault server certificate. * ssl.certificate.location (or environment variable VAULT_CLIENT_CERT): client certificate for mutual TLS. * ssl.key.location (or environment variable VAULT_CLIENT_KEY): client private key for mutual TLS. * An empty or unset CA value keeps verification enabled; it does not silently disable verification. * Confluent Platform: Not affected. The vulnerability resides in the confluent-kafka Python client library and does not affect Confluent Platform server components or their released versions. * Confluent Cloud: Not affected. No remediation is required for Confluent Cloud.
References
- Vendor advisory support.confluent.io/hc/en-us/articles/54133146724244-CO…
Timeline
Days relative to CVE publicationFirst public PoC 5.4 days before publication; not in CISA KEV. First PoC: rahulreddykarne/CVE-2026-15911-Confluent_Kafka (created 26 Sep 2026, found by us: backfilled).
PoC repositories
Found on GitHub.1 PoCs
PoCs 1
| Repository | Created | Stars | Assessment |
|---|---|---|---|
| rahulreddykarne/CVE-2026-15911-Confluent_Kafka | 26 Sep 2026 −5.4 d | 0 | PoC |
Only PoCs count toward the first-PoC date and the characteristics below. Do not run PoC code from unknown sources.