CVE-2026-105311
HIGH 7.7The StreamsHub Console operator acts as a confused deputy: a Kubernetes tenant with permission to create a Console custom resource can set spec.kafkaClusters[].credentials.kafkaUser.namespace to any namespace. The operator, running with cluster-wide Secrets RBAC, reads the victim-namespace KafkaUser Secret (SASL credentials or TLS private keys) and writes the plaintext material into a Secret in the attacker's namespace. No same-namespace check or allowlist exists anywhere in the code path.
ELEVATED IMPACT
Severe if exploited (CVSS 7.7), but no known exploitation and low modeled probability. Patch on a normal cadence.
Exploitation likelihood
0.3%chance of exploitation in 30 days · 22nd percentile
○ In CISA KEV
○ Catalogued PoC
Impact if exploited
7.7CVSS 3.1 · HIGH
- ConfidentialityHigh
- IntegrityNone
- AvailabilityNone
What an attacker needs
- ✓Access: Reachable over the network — no local access needed
- ⚠Privileges: Requires a low-privilege account
- ✓User interaction: No user interaction needed
- ✓Complexity: No special conditions — reliably repeatable
✓ lowers the bar for an attacker · ⚠ raises it
Proof of concept
No public PoC is currently catalogued.
Search for new PoCs
Search GitHub now — results may be empty or unverified.
Tracked sources are checked daily for recent CVEs, including PoCs published after the original disclosure. A later release appears after a tracked source lists it and a refresh succeeds.
Data snapshot:
Affected
Vendors Red Hat
Products Streamshub Console For Apache Kafka® Streams For Apache Kafka 2 Streams For Apache Kafka 3
Weakness (CWE)
- CWE-441: Unintended Proxy or Intermediary ('Confused Deputy')
CVSS vector
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:N/A:N
References and research data (JSON)
Vendor product assessments
console-operator as a component of streams for Apache Kafka 2 · known affected
Vendor assessment for this product only.
pkg:maven/com.github.streamshub/[email protected]
- workaround: 1. Restrict Console CR RBAC — remove create/update verbs on consoles.console.streamshub.github.com from tenant-facing roles. Only trusted cluster administrators should manage Console CRs. 2. Audit existing Console CRs — review all Console CRs for kafkaUser.namespace fields pointing outside the CR's own namespace. 3. Network policy (defense-in-depth) — apply NetworkPolicy to restrict operator pod egress. --- CME Mitigation Guidance (2026-10-20) --- Disclaimer: The following mitigation solutions are provided as a courtesy, pending the application of an official patch. This content was generated utilizing AI tools in conjunction with data from https://cmetaxonomy.org. Customers are advised to independently evaluate and test these temporary mitigations within their own infrastructure. The highest-value action is to enforce strict same-namespace boundary validation on KafkaUser credentials namespace references in Console Operator custom resources to prevent cross-namespace Secret reads: upgrade to the fixed Console Operator builds, which enforce an assertNamespaceAllowed() guard with a same-namespace default check when reading KafkaUser namespace configuration, closing all 2 injection vectors (Console custom resource namespace manipulation, cross-namespace Secret reference). Until patched, this is a concern on Kubernetes clusters running Console Operator where non-admin users have create or update permissions on Console custom resources, so Remove create and update permissions on Console custom resources from tenant roles and audit existing custom resources for kafkaUser.namespace values pointing outside their own namespace. As a compensating measure, Configure Kubernetes API server audit logging to record Console custom resource modifications and cross-namespace Secret read operations performed by the operator service account. These controls limit blast radius and contain exploitation, but they do not fix the underlying confused deputy cross-namespace access defect — apply the upstream patch to fully remediate. Highest-impact CME: CME-711 Admission Controller Policy Enforcement (OPA/Gatekeeper/Kyverno) (high)
- none available: Affected
console-operator as a component of streams for Apache Kafka 3 · known affected
Vendor assessment for this product only.
pkg:maven/com.github.streamshub/[email protected]
- workaround: 1. Restrict Console CR RBAC — remove create/update verbs on consoles.console.streamshub.github.com from tenant-facing roles. Only trusted cluster administrators should manage Console CRs. 2. Audit existing Console CRs — review all Console CRs for kafkaUser.namespace fields pointing outside the CR's own namespace. 3. Network policy (defense-in-depth) — apply NetworkPolicy to restrict operator pod egress. --- CME Mitigation Guidance (2026-10-20) --- Disclaimer: The following mitigation solutions are provided as a courtesy, pending the application of an official patch. This content was generated utilizing AI tools in conjunction with data from https://cmetaxonomy.org. Customers are advised to independently evaluate and test these temporary mitigations within their own infrastructure. The highest-value action is to enforce strict same-namespace boundary validation on KafkaUser credentials namespace references in Console Operator custom resources to prevent cross-namespace Secret reads: upgrade to the fixed Console Operator builds, which enforce an assertNamespaceAllowed() guard with a same-namespace default check when reading KafkaUser namespace configuration, closing all 2 injection vectors (Console custom resource namespace manipulation, cross-namespace Secret reference). Until patched, this is a concern on Kubernetes clusters running Console Operator where non-admin users have create or update permissions on Console custom resources, so Remove create and update permissions on Console custom resources from tenant roles and audit existing custom resources for kafkaUser.namespace values pointing outside their own namespace. As a compensating measure, Configure Kubernetes API server audit logging to record Console custom resource modifications and cross-namespace Secret read operations performed by the operator service account. These controls limit blast radius and contain exploitation, but they do not fix the underlying confused deputy cross-namespace access defect — apply the upstream patch to fully remediate. Highest-impact CME: CME-711 Admission Controller Policy Enforcement (OPA/Gatekeeper/Kyverno) (high)
- none available: Affected
All CVSS metrics
- HIGH 7.7 v3.1 · CNA Primary
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:N/A:N - HIGH 7.7 v3.1 · NVD Secondary
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:N/A:N
References
Advisories
- https://security.access.redhat.com/data/csaf/v2/vex/2026/cve-2026-105311.json Red Hat · CVE-2026-105311 · Updated 2026-10-20T22:33:28+00:00
- https://euvd.enisa.europa.eu/vulnerability/EUVD-2026-104963 EUVD · EUVD-2026-104963
Technical & other
- https://access.redhat.com/security/cve/CVE-2026-105311 CVE record · redhat · Updated 2026-10-20T22:33:30.497Z
NVD · CVE-2026-105311 · Updated 2026-10-21T21:17:44.883
Red Hat · CVE-2026-105311 · Updated 2026-10-20T22:33:28+00:00 - https://bugzilla.redhat.com/show_bug.cgi?id=2510875 CVE record · redhat · Updated 2026-10-20T22:33:30.497Z
NVD · CVE-2026-105311 · Updated 2026-10-21T21:17:44.883
Red Hat · CVE-2026-105311 · Updated 2026-10-20T22:33:28+00:00 - https://www.cve.org/CVERecord?id=CVE-2026-105311 Red Hat · CVE-2026-105311 · Updated 2026-10-20T22:33:28+00:00
- https://nvd.nist.gov/vuln/detail/CVE-2026-105311 Red Hat · CVE-2026-105311 · Updated 2026-10-20T22:33:28+00:00