Attack ChainAIDerived
Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain
-
AccessObtain valid client certificate
-
DeliveryConnect to maestro gRPC broker
-
ExploitBypass authentication check
-
ExecutionSubscribe to other consumers' streams or publish forged agent status
-
ImpactDisclose data or corrupt cluster state
Vulnerability Assessment
| Weakness |
CWE
OWASP Top 10:2025
A07:2025 - Authentication Failures
ASVS 5.0
V6 - Authentication Authentication required for critical functions
MITRE ATT&CK
1 technique across 1 tactic: Initial Access The technique list with ATT&CK links and the kill-chain view is part of the Basic plan and up. |
| Exploitation Conditions | Exploitation requires the attacker to possess a valid client certificate accepted by the maestro gRPC broker - i.e. an already-provisioned mTLS client identity, not anonymous access. Given that certificate, no user interaction or additional configuration is needed (AC:L/UI:N) and the broker's authentication check can be bypassed to subscribe to other consumers' event streams or publish forged agent status. The principal limiting factor is the client-certificate prerequisite (PR:L), which restricts this to trusted-but-lower-privileged or compromised clients rather than arbitrary remote attackers; impact is confined to partial confidentiality and integrity within the broker (no availability impact, scope unchanged). |
| Impact | This is a moderate-severity authentication bypass (CVSS 5.4, CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:L/A:N) in the maestro gRPC broker shipped with Red Hat Multicluster Engine for Kubernetes, classified as CWE-306 (Missing Authentication for a Critical Function). The network attack vector and low complexity raise theoretical exposure, but the PR:L requirement is decisive: the attacker must already hold a valid client certificate, meaning this is not an anonymous internet-facing flaw but a privilege/trust-boundary bypass available to an already-provisioned mTLS client. Impact is partial on both confidentiality and integrity (C:L/I:L, A:N) - reading other consumers' event streams and forging agent status, not full compromise. No EPSS score, CISA KEV listing, SSVC decision data, or public proof-of-concept was provided in the input, so there is no public exploit identified at time of analysis and no evidence of active exploitation; the signals available are internally consistent (a genuine auth-bypass with constrained privilege and impact) rather than conflicting. Net: a legitimate issue worth patching, especially in multi-tenant cluster-management deployments, but it is a bounded insider/lateral-movement risk, not a high-urgency mass-exploitation threat. |
| Exploit ScenarioDerived | An attacker who has obtained a valid client certificate for the maestro gRPC broker (for example a low-privileged or compromised tenant client) connects over the network and exploits the authentication bypass to subscribe to event streams belonging to other consumers, reading their messages, and/or publishes forged agent status messages to corrupt the integrity of cluster state. No proof-of-concept was provided in the input, so this scenario is inferred from the description and CVSS vector (AV:N/AC:L/PR:L). |
Get an e-mail when this CVE is exploited, patched or re-scored. Free account.
Alert meAnalysisAIv1 – Oct 05, 2026
Authentication bypass in the maestro gRPC broker shipped with Red Hat Multicluster Engine for Kubernetes lets a client that already holds a valid mTLS client certificate skip the broker's authentication check and then subscribe to other consumers' event streams or publish forged agent status messages. The consequence is unauthorized information disclosure and loss of data integrity inside the broker, with no availability impact and scope unchanged; the assessed CVSS 3.1 base score is 5.4 (AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:L/A:N). There is no confirmed active exploitation (not listed in CISA KEV) and no public exploit code identified at time of analysis, and the valid-client-certificate prerequisite confines abuse to trusted-but-lower-privileged or already-compromised clients rather than anonymous remote attackers.
RemediationAI
No vendor-released patch was identified at time of analysis; the authoritative fix status and any corrected Multicluster Engine build should be confirmed against https://access.redhat.com/security/cve/CVE-2026-71297 and https://bugzilla.redhat.com/show_bug.cgi?id=2511518 before planning upgrades. Until a fixed release is available, the effective compensating control is to shrink the set of identities that can reach the broker: restrict which client certificates the broker trusts, rotate and re-issue mTLS client credentials so any compromised identity loses access, and treat possession of a broker client certificate as a privileged asset - the trade-off is additional certificate-management overhead and possible disruption if workloads depend on broad trust. Network-side, limit exposure of the broker's gRPC listener to only the namespaces or hosts that legitimately publish agent status, accepting that this reduces but does not eliminate the risk from already-trusted clients. Because the abuse produces cross-consumer subscriptions and forged agent status, enable broker-side audit logging of subscription and publish calls per client identity and alert on consumers subscribing to streams outside their normal scope; this detection is post-hoc and does not prevent the bypass itself.
Affects your stack
Find out whether the stacks and servers you run are on an affected version.
Checking this CVE against your own stacks and servers is part of the Basic plan and up.
Technical ContextAI · show details
The vulnerable component is the maestro gRPC broker, a control-plane messaging service that multiplexes event streams between agents and consumers in Red Hat Multicluster Engine for Kubernetes; CPE data pins the affected offering to cpe:2.3:a:red_hat:multicluster_engine_for_kubernetes (the supplied CPE entries are version-wildcarded, so no specific release range is enumerated in the input). The broker relies on mutual TLS, where a client certificate is the sole authentication artifact, and the defect is classified as CWE-306 (Missing Authentication for a Critical Function): a critical operation - subscription to another consumer's event stream and publication of agent status - is reachable without a proper authorization check once the TLS handshake succeeds, so possession of any accepted client certificate confers access beyond the identity it represents. Because the failure is in the authentication/authorization layer rather than memory handling or injection, exploitation is deterministic and does not require malformed input, and the impact is bounded to partial confidentiality and integrity on the broker's own message bus.
Know when Kubernetes gets its next vulnerability
- Watch products and get an email when something new is published
- Check this CVE against your own stack and servers
- Exploit and PoC references, threat intelligence from 22 sources
No credit card · 7-day full trial
Severity by source
AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:L/A:N
Network-reachable gRPC broker (AV:N/AC:L) requiring a valid client certificate (PR:L), no user interaction; bypass yields partial confidentiality and integrity impact (C:L/I:L) with no availability effect.
Primary rating from Vendor (redhat).
CVSS VectorVendor: redhat
DescriptionCVE.org
A flaw was found in the maestro gRPC broker. This vulnerability allows a remote attacker, with a valid client certificate, to bypass authentication. This bypass enables the attacker to subscribe to other consumers' event streams, leading to unauthorized information disclosure, or to publish forged agent status, which can compromise data integrity.
Threat Intelligence Overview
How this decision was reached
The engine reads each signal below and applies a fixed list of rules from top to bottom. The first rule that matches sets the recommended action – like a statement, every line is shown.
What every action level means
SSVC AssessmentENISA
Priority Score
Attack Technique
Authentication bypass attacks exploit flaws in the verification mechanisms that control access to systems and applications.
Information disclosure occurs when an application unintentionally exposes sensitive data that aids attackers in reconnaissance or directly compromises security.
Affected Products (CPE)CVE.org
More in Kubernetes
View allA critical vulnerability in Kubernetes ingress-nginx controller allows unauthenticated attackers with pod network access
Credential-harvesting malware compromised 84 versions of 42 TanStack npm packages on 2026-05-11 via chained GitHub Actio
Kubernetes ingress-nginx contains a configuration injection vulnerability via the mirror-target and mirror-host Ingress
A security issue was discovered in ingress-nginx https://github.com/kubernetes/ingress-nginx where the `auth-url` Ingres
A security issue was discovered in ingress-nginx https://github.com/kubernetes/ingress-nginx where the `auth-tls-match-c
Kubernetes API server in all versions allow an attacker who is able to create a ClusterIP service and set the spec.exter
A security issue was discovered in Kubernetes where a user that can create pods on Windows nodes may be able to escalate
Argo CD is a declarative, GitOps continuous delivery tool for Kubernetes. Rated critical severity (CVSS 9.9), this vulne
Unauthenticated remote attackers can trigger complete database overwrites, server-side file reads, and SSRF attacks agai
The Kubernetes integration in GitLab Enterprise Edition 11.x before 11.2.8, 11.3.x before 11.3.9, and 11.4.x before 11.4
Fluentd configuration injection in the kube-logging Logging operator before 6.6.0 allows a namespace-scoped user who can
Authenticated Typebot users can abuse the webhook block (HTTP Request component) in versions prior to 3.13.1 to issue ar
EUVD-2026-92711
GHSA-99qh-3h9r-vq6x
NVD
CVE.org
EPSS
Vulnrichment
Exploit-DB