Critical [CVE-2026-16242] Konnectivity proxy-server accepts agent connections without validating client certificates
This critical-severity Red Hat Linux advisory covers CVE-2026-16242.
Android app · Google Play
Monitor future Red Hat Linux 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 32 official vendor sources and 160+ reviewed platform categories.
Summary
Konnectivity proxy-server accepts agent connections without validating client certificates. Red Hat rates this critical (CVSS 9.4).
Weakness: CWE-306. Red Hat lists fixing advisory RHSA-2026:48284 with package multicluster-engine/hypershift-rhel9-operator:1784856942, multicluster-engine/hypershift-rhel9-operator:1784905769, openshift4/ose-hypershift-rhel9:1785192936, multicluster-engine/hypershift-rhel9-operator:1784905804.
Affected versions
No affected-version range was extracted from the source record. The vendor advisory is authoritative — check it before change work.
Official advisory · high-confidence parse· fetched 1 month ago·verify at source
- multicluster-engine/hypershift-rhel9-operator:1784856942
- multicluster-engine/hypershift-rhel9-operator:1784905769
- openshift4/ose-hypershift-rhel9:1785192936
- multicluster-engine/hypershift-rhel9-operator:1784905804
- openshift4/ose-hypershift-rhel9:1784912882
- multicluster-engine/hypershift-rhel9-operator:1784905766
- multicluster-engine/hypershift-rhel9-operator:1784905783
- openshift4/ose-hypershift-rhel9:1785288843
- openshift4/ose-hypershift-rhel9:1784914869
- multicluster-engine/hypershift-rhel9-operator:1784945966
- openshift4/ose-hypershift-rhel9:1785301941
- openshift4/ose-hypershift-rhel9:1784913720
- RHSA-2026:48284
Official advisory · high-confidence parse· fetched 1 month ago·verify at source
Mitigation checklist
- 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.
Official advisory · high-confidence parse· fetched 1 month ago·verify at source
Discussion(0)
No comments yet. Share field notes, upgrade gotchas, or questions — verify against the vendor advisory before acting on community advice.
Sign in to join the discussion.