CVSS 3.1
7.4 highCVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:NHigh (7.4) in confluent confluent-kafka. EPSS 0.3% estimated probability of exploitation activity in the next 30 days.
CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:NExplain CVE-2026-15911 for an engineer deciding whether to act. Use https://cve.bz/api/public/cves/CVE-2026-15911?via=ask-ai-copy and https://cve.bz/cve/CVE-2026-15911?via=ask-ai-copy as the source of truth: what is affected and which versions fix it, whether it is in CISA KEV, public exploits, and its EPSS (an internet-wide 30-day estimate of exploitation activity, not a forecast for my systems). If they give no fixed versions, use the CVE record https://cveawg.mitre.org/api/cve/CVE-2026-15911 or the vendor advisory, not third-party mirrors. Tell me how to check whether I am affected and how to verify a fix. Cite the sources and say where they are uncertain.Opens a third-party assistant; its answer is its own, not cve.bz's. The prompt holds only this CVE's id and public links.
From the CNA's record in the CVE List.
| Product | Affected |
|---|---|
| confluent-kafka | through 2.14.2 |
| Distribution | Release | Package | Fixed in | Advisory |
|---|---|---|---|---|
| openSUSE | Tumbleweed | python-confluent-kafka | 2.15.1-1.1 | openSUSE-SU-2026:12006-1 |
From the distributions' data via OSV.dev: SUSE security data, CC BY 4.0. Modified: reformatted and linked to CVE records. Credits. On the distributions' own pages: openSUSE.
Red Hat rates this Important.
An IMPORTANT severity flaw (CVSS 3.1 base score 7.4, CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:N) was found in the confluent-kafka Python client's HashiCorp Vault Key Management Service (KMS) integration, which is used for Schema Registry client-side field-level encryption (CSFLE). The client's HTTPS connection to the Vault service has Transport Layer Security (TLS) certificate verification disabled by default, with no configuration option exposed to re-enable it. A remote attacker in a privileged network position, able to intercept traffic between an affected application and its Vault server, could impersonate the Vault server with any certificate, including a self-signed one, to capture Vault access tokens and AppRole credentials in transit or to return manipulated responses affecting KMS key wrap and unwrap operations. Exploitation requires no application-level authentication, but it does require a man-in-the-middle position on the network path between the client and the Vault service. Only the HashiCorp Vault KMS integration is affected; the AWS, Google Cloud, and Azure KMS integrations in the same package verify certificates by default and are not affected. Red Hat Satellite and Red Hat Insights (cloud.redhat.com) components that bundle the affected confluent-kafka Python package are listed as affected, and fixes are being pursued by the responsible product teams. The Red Hat severity rating of IMPORTANT matches the upstream CVSS rating.
Mitigation for this issue is either not available or the currently available options do not meet the Red Hat Product Security criteria comprising ease of use and deployment, applicability to widespread installation base, or stability. There is no configuration workaround in affected versions because TLS certificate verification is hardcoded to disabled. The upstream confluent-kafka Python package addressed this issue in version 2.15.0, which enables TLS certificate verification by default and allows supplying a CA bundle through the ssl.ca.location configuration option or the VAULT_CACERT environment variable for Vault servers that present certificates signed by a private or internal certificate authority. Updating to a version of the confluent-kafka Python package that enables TLS certificate verification, or updating affected Red Hat products once they incorporate the fixed version, is the recommended resolution.
| Product | Package | State | Advisory |
|---|---|---|---|
| Red Hat Satellite 6.18 | satellite/iop-insights-engine-rhel9:1794505898 | Fixed 2026-11-13 | RHSA-2026:100151 |
| Red Hat Satellite 6.18 | satellite/iop-host-inventory-rhel9:1793772638 | Fixed 2026-11-05 | RHSA-2026:95674 |
| Red Hat Satellite 6.18 | satellite/iop-puptoo-rhel9:1793643099 | Fixed 2026-11-05 | RHSA-2026:95676 |
| Red Hat Satellite 6.18 | satellite/iop-yuptoo-rhel9:1793811191 | Fixed 2026-11-05 | RHSA-2026:95682 |
| Red Hat Satellite 6.18 | satellite/iop-advisor-backend-rhel9:1793757716 | Fixed 2026-11-05 | RHSA-2026:95719 |
| Red Hat Satellite 6.19 | satellite/iop-insights-engine-rhel9:1794506069 | Fixed 2026-11-13 | RHSA-2026:100153 |
| Red Hat Satellite 6.19 | satellite/iop-yuptoo-rhel9:1793811128 | Fixed 2026-11-05 | RHSA-2026:95659 |
| Red Hat Satellite 6.19 | satellite/iop-puptoo-rhel9:1793806180 | Fixed 2026-11-05 | RHSA-2026:95661 |
| Red Hat Satellite 6.19 | satellite/iop-host-inventory-rhel9:1793853308 | Fixed 2026-11-05 | RHSA-2026:95662 |
| Red Hat Satellite 6.19 | satellite/iop-advisor-backend-rhel9:1793758586 | Fixed 2026-11-05 | RHSA-2026:95703 |
Contains Red Hat Security Data © Red Hat, Inc., licensed under CC BY 4.0. Source: https://access.redhat.com/security/data. Modified: reformatted. Red Hat's page for CVE-2026-15911.
Repositories on GitHub named after this CVE or listed for it by the PoC-in-GitHub index. For those marked Harbor Check: matches CVE, Flawharbor read the code and found it implements this CVE's exploitation technique: read, not run, and its dependencies only checked for warning signs, so a pointer and no guarantee. The rest are unverified: some hold a working proof of concept, some nothing useful, and some malware made to look like one. Read the code before you run any of it. How Harbor Check reads them, and what it found.
The attack patterns MITRE's CAPEC relates to this record's weaknesses, as MITRE names them. Credits.