CVE-2026-16242
CVE-2026-16242: 1 tracked advisory record across Red Hat. Compare vendor sources and published fix guidance.
Compare the source-linked records below. Ratings and product/version details belong to each advisory; they are not a single CVE-wide score or proof that every listed product is affected. How VulniPulse collects and checks evidence.
Vendor advisory comparison
Red Hat
1 advisory- Advisory severityCritical9.4
Critical [CVE-2026-16242] Konnectivity proxy-server accepts agent connections without validating client certificates
CVE-2026-16242Source published Source updated
A flaw was found in the Konnectivity proxy-server configuration for hosted control planes. The agent-facing listener was started without --cluster-ca-cert (and without token-based agent authentication), so client certificates were not validated. A remote attacker who can reach the Konnectivity cluster endpoint could connect as an unauthenticated agent, join the routing pool, and potentially proxy, inspect, modify, or drop control-plane-to-node traffic. Because that endpoint is exposed so worker agents can connect, a successful attack can enroll an untrusted agent in the routing pool. When the proxy selects that stream for a control-plane dial, the attacker may proxy, inspect, modify, or drop control-plane-to-node traffic, affecting confidentiality, integrity, and availability of that…
- Affected products in this advisory
- multicluster engine for Kubernetes 2.11
- multicluster engine for Kubernetes 2.17
- multicluster engine for Kubernetes 2.6
- multicluster engine for Kubernetes 2.8
10 more entries in the full advisory.
- Source-reported affected versions
- Affected-version details not available in this record.
- Source-reported fixed versions
- multicluster-engine/hypershift-rhel9-operator:1784905766
- multicluster-engine/hypershift-rhel9-operator:1784945966
- multicluster-engine/hypershift-rhel9-operator:1784856942
- multicluster-engine/hypershift-rhel9-operator:1784905804
27 more entries in the full advisory.
- Mitigation guidance
- Until an update that configures Konnectivity agent authentication is applied, restrict network access to the Konnectivity cluster (agent) endpoint so that only trusted worker networks can reach it. For NodePort or LoadBalancer publishing, limit ingress to port 8091 to worker node subnet ranges. For Route-based publishing, restrict access to the Konnectivity route to trusted networks where possible. These controls reduce the chance that an unauthenticated attacker can reach the agent listener; they do not replace proper agent client-certificate (or token) authentication.
Android app · Google Play
Monitor future Red Hat CVEs from your phone.
Choose a whole vendor or a precise platform, then receive matching security advisories by phone notification, email, or both. Coverage follows 34 official vendor sources and 160+ reviewed platform categories.