# CVE-2026-16242: Hypershift: konnectivity proxy-server accepts agent connections without validating client certificates

> Remote attackers can connect as unauthenticated agents to proxy or modify control-plane traffic due to missing certificate validation in Konnectivity.

- **Severity:** Critical 9.4 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:L`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 20 Jul 2026
- **Updated:** 14 Sep 2026
- **Also known as:** GHSA-43hh-68v6-mf36

## What is CVE-2026-16242?

CVE-2026-16242 is a critical missing authorization vulnerability in Logging Subsystem for Red Hat OpenShift, published on 20 Jul 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

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.

Weakness: CWE-306 (Missing Authentication for Critical Functionality)

## Which versions are affected by CVE-2026-16242?


## How do I fix CVE-2026-16242?

No fix has been published for CVE-2026-16242 yet. Limit exposure of the affected software until one is available.

## Is CVE-2026-16242 being exploited?

There is no known exploitation of CVE-2026-16242 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-16242 and fix it if it is affected.

What it is: CVE-2026-16242 is a critical missing authorization vulnerability in Logging Subsystem for Red Hat OpenShift, published on 20 Jul 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-16242 in the wild and no public exploit code.

Affected product: Logging Subsystem for Red Hat OpenShift. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-16242/ (Markdown: https://insights.sbomify.com/CVE-2026-16242/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-16242
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-16242
- OSV: https://osv.dev/vulnerability/CVE-2026-16242

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-16242/
Summaries are generated and may contain mistakes; the official description above is the record.