CVE-2026-15911 (GCVE-0-2026-15911)
Vulnerability from cvelistv5
Published
2026-10-01 18:29
Modified
2026-10-06 02:01
Severity ?
VLAI Severity ?
EPSS score ?
CWE
- CWE-295 - Improper certificate validation
Summary
Confluent Kafka Python client's HashiCorp Vault KMS integration could allow a remote attacker to obtain sensitive information due to improper TLS certificate validation.
References
Impacted products
| Vendor | Product | Version | ||
|---|---|---|---|---|
| confluent | confluent-kafka |
Version: 0 ≤ 2.14.2 cpe:2.3:a:confluent:confluent-kafka:*:*:*:*:*:*:*:* cpe:2.3:a:confluent:confluent-kafka:2.14.2:*:*:*:*:*:*:* |
{
"containers": {
"adp": [
{
"metrics": [
{
"other": {
"content": {
"id": "CVE-2026-15911",
"options": [
{
"Exploitation": "none"
},
{
"Automatable": "no"
},
{
"Technical Impact": "total"
}
],
"role": "CISA Coordinator",
"timestamp": "2026-10-06T02:00:19.695616Z",
"version": "2.0.3"
},
"type": "ssvc"
}
}
],
"providerMetadata": {
"dateUpdated": "2026-10-06T02:01:13.972Z",
"orgId": "134c704f-9b21-4f2e-91b3-4a467353bcc0",
"shortName": "CISA-ADP"
},
"title": "CISA ADP Vulnrichment"
}
],
"cna": {
"affected": [
{
"cpes": [
"cpe:2.3:a:confluent:confluent-kafka:*:*:*:*:*:*:*:*",
"cpe:2.3:a:confluent:confluent-kafka:2.14.2:*:*:*:*:*:*:*"
],
"defaultStatus": "unaffected",
"product": "confluent-kafka",
"vendor": "confluent",
"versions": [
{
"lessThanOrEqual": "2.14.2",
"status": "affected",
"version": "0",
"versionType": "semver"
}
]
}
],
"cpeApplicability": [
{
"nodes": [
{
"cpeMatch": [
{
"criteria": "cpe:2.3:a:confluent:confluent-kafka:*:*:*:*:*:*:*:*",
"versionEndIncluding": "2.14.2",
"versionStartIncluding": "0",
"vulnerable": true
}
],
"negate": false,
"operator": "OR"
}
],
"operator": "OR"
}
],
"credits": [
{
"lang": "en",
"type": "finder",
"value": "Rahul Karne"
}
],
"descriptions": [
{
"lang": "en",
"supportingMedia": [
{
"base64": false,
"type": "text/html",
"value": "Confluent Kafka Python client\u0027s HashiCorp Vault KMS integration could allow a remote attacker to obtain sensitive information due to improper TLS certificate validation."
}
],
"value": "Confluent Kafka Python client\u0027s HashiCorp Vault KMS integration could allow a remote attacker to obtain sensitive information due to improper TLS certificate validation."
}
],
"metrics": [
{
"cvssV3_1": {
"attackComplexity": "HIGH",
"attackVector": "NETWORK",
"availabilityImpact": "NONE",
"baseScore": 7.4,
"baseSeverity": "HIGH",
"confidentialityImpact": "HIGH",
"integrityImpact": "HIGH",
"privilegesRequired": "NONE",
"scope": "UNCHANGED",
"userInteraction": "NONE",
"vectorString": "CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:N",
"version": "3.1"
},
"format": "CVSS",
"scenarios": [
{
"lang": "en",
"value": "GENERAL"
}
]
}
],
"problemTypes": [
{
"descriptions": [
{
"cweId": "CWE-295",
"description": "CWE-295 Improper certificate validation",
"lang": "en",
"type": "CWE"
}
]
}
],
"providerMetadata": {
"dateUpdated": "2026-10-01T18:29:42.297Z",
"orgId": "9a959283-ebb5-44b6-b705-dcc2bbced522",
"shortName": "ibm"
},
"references": [
{
"tags": [
"vendor-advisory",
"patch"
],
"url": "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"
}
],
"solutions": [
{
"lang": "en",
"supportingMedia": [
{
"base64": false,
"type": "text/html",
"value": "\u003cul\u003e\u003cli\u003e\u003cstrong\u003econfluent-kafka (Python): \u003c/strong\u003eThis issue has been addressed in confluent-kafka (Python) 2.15.0, which:\u003cul\u003e\u003cli\u003eEnables TLS certificate verification by default.\u003c/li\u003e\u003cli\u003eExposes configuration to supply a custom CA bundle and an optional client certificate for mutual TLS, through both driver configuration and standard Vault environment variables:\u003cul\u003e\u003cli\u003essl.ca.location (or environment variable VAULT_CACERT): CA bundle used to verify the Vault server certificate.\u003c/li\u003e\u003cli\u003essl.certificate.location (or environment variable VAULT_CLIENT_CERT): client certificate for mutual TLS.\u003c/li\u003e\u003cli\u003essl.key.location (or environment variable VAULT_CLIENT_KEY): client private key for mutual TLS.\u003c/li\u003e\u003c/ul\u003e\u003c/li\u003e\u003cli\u003eAn empty or unset CA value keeps verification enabled; it does not silently disable verification.\u003c/li\u003e\u003c/ul\u003e\u003c/li\u003e\u003cli\u003e\u003cstrong\u003eConfluent Platform: \u003c/strong\u003eNot affected. The vulnerability resides in the confluent-kafka Python client library and does not affect Confluent Platform server components or their released versions.\u003c/li\u003e\u003cli\u003e\u003cstrong\u003eConfluent Cloud:\u003c/strong\u003e Not affected. No remediation is required for Confluent Cloud.\u003c/li\u003e\u003c/ul\u003e"
}
],
"value": "* confluent-kafka (Python): This issue has been addressed in confluent-kafka (Python) 2.15.0, which: * Enables TLS certificate verification by default.\n * 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.\n * ssl.certificate.location (or environment variable VAULT_CLIENT_CERT): client certificate for mutual TLS.\n * ssl.key.location (or environment variable VAULT_CLIENT_KEY): client private key for mutual TLS.\n\n\n\n * An empty or unset CA value keeps verification enabled; it does not silently disable verification.\n\n\n\n * 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.\n * Confluent Cloud: Not affected. No remediation is required for Confluent Cloud."
}
],
"source": {
"discovery": "UNKNOWN"
},
"title": "Confluent Kafka Python Improper TLS Certificate Validation",
"x_generator": {
"engine": "Vulnogram 1.0.5"
}
}
},
"cveMetadata": {
"assignerOrgId": "9a959283-ebb5-44b6-b705-dcc2bbced522",
"assignerShortName": "ibm",
"cveId": "CVE-2026-15911",
"datePublished": "2026-10-01T18:29:42.297Z",
"dateReserved": "2026-07-15T19:28:12.162Z",
"dateUpdated": "2026-10-06T02:01:13.972Z",
"state": "PUBLISHED"
},
"dataType": "CVE_RECORD",
"dataVersion": "5.2",
"vulnerability-lookup:meta": {
"vulnrichment": {
"containers": "{\"adp\": [{\"title\": \"CISA ADP Vulnrichment\", \"metrics\": [{\"other\": {\"type\": \"ssvc\", \"content\": {\"id\": \"CVE-2026-15911\", \"role\": \"CISA Coordinator\", \"options\": [{\"Exploitation\": \"none\"}, {\"Automatable\": \"no\"}, {\"Technical Impact\": \"total\"}], \"version\": \"2.0.3\", \"timestamp\": \"2026-10-06T02:00:19.695616Z\"}}}], \"providerMetadata\": {\"orgId\": \"134c704f-9b21-4f2e-91b3-4a467353bcc0\", \"shortName\": \"CISA-ADP\", \"dateUpdated\": \"2026-10-06T02:01:08.619Z\"}}], \"cna\": {\"title\": \"Confluent Kafka Python Improper TLS Certificate Validation\", \"source\": {\"discovery\": \"UNKNOWN\"}, \"credits\": [{\"lang\": \"en\", \"type\": \"finder\", \"value\": \"Rahul Karne\"}], \"metrics\": [{\"format\": \"CVSS\", \"cvssV3_1\": {\"scope\": \"UNCHANGED\", \"version\": \"3.1\", \"baseScore\": 7.4, \"attackVector\": \"NETWORK\", \"baseSeverity\": \"HIGH\", \"vectorString\": \"CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:N\", \"integrityImpact\": \"HIGH\", \"userInteraction\": \"NONE\", \"attackComplexity\": \"HIGH\", \"availabilityImpact\": \"NONE\", \"privilegesRequired\": \"NONE\", \"confidentialityImpact\": \"HIGH\"}, \"scenarios\": [{\"lang\": \"en\", \"value\": \"GENERAL\"}]}], \"affected\": [{\"cpes\": [\"cpe:2.3:a:confluent:confluent-kafka:*:*:*:*:*:*:*:*\", \"cpe:2.3:a:confluent:confluent-kafka:2.14.2:*:*:*:*:*:*:*\"], \"vendor\": \"confluent\", \"product\": \"confluent-kafka\", \"versions\": [{\"status\": \"affected\", \"version\": \"0\", \"versionType\": \"semver\", \"lessThanOrEqual\": \"2.14.2\"}], \"defaultStatus\": \"unaffected\"}], \"solutions\": [{\"lang\": \"en\", \"value\": \"* confluent-kafka (Python): This issue has been addressed in confluent-kafka (Python) 2.15.0, which: * Enables TLS certificate verification by default.\\n * 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.\\n * ssl.certificate.location (or environment variable VAULT_CLIENT_CERT): client certificate for mutual TLS.\\n * ssl.key.location (or environment variable VAULT_CLIENT_KEY): client private key for mutual TLS.\\n\\n\\n\\n * An empty or unset CA value keeps verification enabled; it does not silently disable verification.\\n\\n\\n\\n * 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.\\n * Confluent Cloud: Not affected. No remediation is required for Confluent Cloud.\", \"supportingMedia\": [{\"type\": \"text/html\", \"value\": \"\u003cul\u003e\u003cli\u003e\u003cstrong\u003econfluent-kafka (Python): \u003c/strong\u003eThis issue has been addressed in confluent-kafka (Python) 2.15.0, which:\u003cul\u003e\u003cli\u003eEnables TLS certificate verification by default.\u003c/li\u003e\u003cli\u003eExposes configuration to supply a custom CA bundle and an optional client certificate for mutual TLS, through both driver configuration and standard Vault environment variables:\u003cul\u003e\u003cli\u003essl.ca.location (or environment variable VAULT_CACERT): CA bundle used to verify the Vault server certificate.\u003c/li\u003e\u003cli\u003essl.certificate.location (or environment variable VAULT_CLIENT_CERT): client certificate for mutual TLS.\u003c/li\u003e\u003cli\u003essl.key.location (or environment variable VAULT_CLIENT_KEY): client private key for mutual TLS.\u003c/li\u003e\u003c/ul\u003e\u003c/li\u003e\u003cli\u003eAn empty or unset CA value keeps verification enabled; it does not silently disable verification.\u003c/li\u003e\u003c/ul\u003e\u003c/li\u003e\u003cli\u003e\u003cstrong\u003eConfluent Platform: \u003c/strong\u003eNot affected. The vulnerability resides in the confluent-kafka Python client library and does not affect Confluent Platform server components or their released versions.\u003c/li\u003e\u003cli\u003e\u003cstrong\u003eConfluent Cloud:\u003c/strong\u003e Not affected. No remediation is required for Confluent Cloud.\u003c/li\u003e\u003c/ul\u003e\", \"base64\": false}]}], \"references\": [{\"url\": \"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\", \"tags\": [\"vendor-advisory\", \"patch\"]}], \"x_generator\": {\"engine\": \"Vulnogram 1.0.5\"}, \"descriptions\": [{\"lang\": \"en\", \"value\": \"Confluent Kafka Python client\u0027s HashiCorp Vault KMS integration could allow a remote attacker to obtain sensitive information due to improper TLS certificate validation.\", \"supportingMedia\": [{\"type\": \"text/html\", \"value\": \"Confluent Kafka Python client\u0027s HashiCorp Vault KMS integration could allow a remote attacker to obtain sensitive information due to improper TLS certificate validation.\", \"base64\": false}]}], \"problemTypes\": [{\"descriptions\": [{\"lang\": \"en\", \"type\": \"CWE\", \"cweId\": \"CWE-295\", \"description\": \"CWE-295 Improper certificate validation\"}]}], \"cpeApplicability\": [{\"nodes\": [{\"negate\": false, \"cpeMatch\": [{\"criteria\": \"cpe:2.3:a:confluent:confluent-kafka:*:*:*:*:*:*:*:*\", \"vulnerable\": true, \"versionEndIncluding\": \"2.14.2\", \"versionStartIncluding\": \"0\"}], \"operator\": \"OR\"}], \"operator\": \"OR\"}], \"providerMetadata\": {\"orgId\": \"9a959283-ebb5-44b6-b705-dcc2bbced522\", \"shortName\": \"ibm\", \"dateUpdated\": \"2026-10-01T18:29:42.297Z\"}}}",
"cveMetadata": "{\"cveId\": \"CVE-2026-15911\", \"state\": \"PUBLISHED\", \"dateUpdated\": \"2026-10-06T02:01:13.972Z\", \"dateReserved\": \"2026-07-15T19:28:12.162Z\", \"assignerOrgId\": \"9a959283-ebb5-44b6-b705-dcc2bbced522\", \"datePublished\": \"2026-10-01T18:29:42.297Z\", \"assignerShortName\": \"ibm\"}",
"dataType": "CVE_RECORD",
"dataVersion": "5.2"
}
}
}
Loading…
Loading…
Sightings
| Author | Source | Type | Date |
|---|
Nomenclature
- Seen: The vulnerability was mentioned, discussed, or seen somewhere by the user.
- Confirmed: The vulnerability is confirmed from an analyst perspective.
- Published Proof of Concept: A public proof of concept is available for this vulnerability.
- Exploited: This vulnerability was exploited and seen by the user reporting the sighting.
- Patched: This vulnerability was successfully patched by the user reporting the sighting.
- Not exploited: This vulnerability was not exploited or seen by the user reporting the sighting.
- Not confirmed: The user expresses doubt about the veracity of the vulnerability.
- Not patched: This vulnerability was not successfully patched by the user reporting the sighting.
Loading…
Loading…