Security readout for executives and security teams
Plain-English summary
This critical Red Hat Hypershift issue lets an attacker who can reach the Konnectivity cluster endpoint connect as an agent without certificate validation. That could let them interfere with sensitive control-plane-to-node traffic. The business risk is high for hosted control plane environments because confidentiality, integrity, and some availability of cluster communications may be affected.
Executive priority
Treat as an urgent patching item for Red Hat hosted control plane environments. Prioritize systems where the Konnectivity endpoint is exposed beyond trusted cluster networks. If your organization does not use Hypershift hosted control planes or listed affected packages, urgency is lower after validation.
Technical view
The Konnectivity proxy-server agent-facing listener for hosted control planes was started without --cluster-ca-cert and without token-based agent authentication. Client certificates were not validated, enabling unauthenticated agent connections to join the routing pool and potentially proxy, inspect, modify, or drop control-plane-to-node traffic. CVSS is 9.4, CWE-306.
Likely exposure
Exposure is most likely in Red Hat hosted control plane deployments using affected multicluster-engine/hypershift-rhel9-operator packages, plus affected OADP packages listed by Red Hat. Risk depends on whether the Konnectivity cluster endpoint is reachable by an attacker.
Exploitation context
The source bundle does not show CISA KEV listing or confirmed active exploitation. Exploitation requires network reachability to the Konnectivity cluster endpoint, but no credentials or user interaction are required according to the CVSS vector.
Researcher notes
The core defect is missing authentication on the Konnectivity agent path, not a generic Kubernetes issue. Public sources provided do not include exploit code or confirmed exploitation. Fixed version details are not present in the bundle, so rely on Red Hat errata and product advisories for remediation targeting.
Mitigation direction
- Apply the relevant Red Hat security advisories for affected products and packages.
- Prioritize hosted control plane environments with reachable Konnectivity cluster endpoints.
- Restrict network access to Konnectivity cluster endpoints where operationally possible.
- Verify vendor guidance for exact fixed builds before change approval.
- Track Hypershift PR 9031 and Red Hat Bugzilla 2502690 for implementation details.
Validation and detection
- Inventory Red Hat MCE, Hypershift, and OADP deployments against Red Hat's affected package list.
- Confirm Konnectivity proxy-server agent authentication is enabled after remediation.
- Check whether agent-facing Konnectivity endpoints are reachable from untrusted networks.
- Review Red Hat errata applicability for each cluster and operator channel.
- Document unaffected packages separately to avoid unnecessary emergency changes.
Public sources used
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Conservative CVE-to-ATT&CK context
These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.
ATT&CK lookup starting points
Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.
CWE-306: Credential and account abuse lookup
Authentication and credential weaknesses can make valid-account abuse and credential telemetry useful review starting points. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.
Open ATT&CK lookupCredential and access behavior lookup
The CVE wording references authentication or credential exposure, so valid-account and credential-access review may help. This is a Glexia inferred lookup path, not an official MITRE, ATT&CK, or CVE Program mapping.
Open ATT&CK lookupContainer behavior lookup
The affected technology mentions containers, so container-specific ATT&CK technique review may help. This is a Glexia inferred lookup path, not an official MITRE, ATT&CK, or CVE Program mapping.
Open ATT&CK lookupCVE-2026-16242 mapping review
Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.
Open ATT&CK lookup- Severity
- Critical
- CVSS
- 9.4 (3.1)
- Known Exploited
- No
- Published
Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:L
CNA and ADP enrichment extracted from CVE v5
These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.
SSVC decision data
CVSS vector scores
1 official scoreWe collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:L3.95.5redhatVulnerability scoring details
Base CVSS 3.1 score
9.4CriticalVector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:L
Vulnerability timeline
Timeline events are normalized from CVE metadata, CNA source timelines, ADP timelines, and KEV metadata when present.
- Source timelineredhat
Made public.
- Source timelineredhat
Reported to Red Hat.
- CVE reservedCVE Program
The CVE ID was reserved by the assigning CNA.
- CVE publishedCVE Program
The CVE record was published.
- CVE updatedCVE Program
The CVE record metadata indicates this as the latest update time.
ADP provider summaries
Source materials
- CVE List V5 sourceCVE List V5
- RHSA-2026:46885CVE reference, redhat · vendor-advisory, x_refsource_REDHAT
- RHSA-2026:47388CVE reference, redhat · vendor-advisory, x_refsource_REDHAT
- RHSA-2026:47735CVE reference, redhat · vendor-advisory, x_refsource_REDHAT
- RHSA-2026:47949CVE reference, redhat · vendor-advisory, x_refsource_REDHAT
- RHSA-2026:47953CVE reference, redhat · vendor-advisory, x_refsource_REDHAT
- RHSA-2026:47974CVE reference, redhat · vendor-advisory, x_refsource_REDHAT
- RHSA-2026:48284CVE reference, redhat · vendor-advisory, x_refsource_REDHAT
- https://access.redhat.com/security/cve/CVE-2026-16242CVE reference, redhat · vdb-entry, x_refsource_REDHAT
- RHBZ#2502690CVE reference, redhat · issue-tracking, x_refsource_REDHAT
- https://github.com/openshift/hypershift/pull/9031CVE reference, redhat
Products and packages named in the record
CWE details
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.
Missing Authentication for Critical Function
Missing Authentication for Critical Function represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.