Monitor vulnerabilities like this one. Sign up free to get alerted when software you use is affected.
9.6

CVE-2026-73843: OpenChoreo: Unauthenticated access to data-plane operations

CVE-2026-73843 · published today
Summary

A security issue in OpenChoreo, a developer platform for Kubernetes, allowed attackers to access sensitive data and execute commands in workload pods without a password. This issue has been fixed in versions 1.0.2 and 1.1.2, so update your OpenChoreo to the latest version to protect your system. If you're using an earlier version, consider updating as soon as possible to prevent potential security risks.

What to do
  • Update github.com openchoreo to version 1.0.2.
  • Update github.com openchoreo to version 1.1.2.
Affected software
Ecosystem VendorProductAffected versions
go github.com openchoreo < 1.0.2
>= 1.1.0, < 1.1.2
Fix: upgrade to 1.0.2
openchoreo openchoreo < 1.0.2
Original advisory text
OpenChoreo: Unauthenticated access to data-plane operations via OpenChoreo cluster-gateway management APIs
### Summary
The OpenChoreo control-plane **cluster-gateway** served its caller-facing management APIs on the same network listener that accepts data-plane agent connections. In the multi-cluster topology that listener is published outside the cluster, and the management APIs did not authenticate the calling client. A party able to reach the listener could therefore invoke privileged data-plane operations without authenticating and without passing through the OpenChoreo API server's authorization.

### Impact
An attacker who can reach the externally published cluster-gateway endpoint can perform data-plane operations normally restricted to the OpenChoreo API server and gated by its authorization — including proxying the data plane's Kubernetes API and executing commands inside workload pods. This can result in full compromise of workloads on the affected data plane (disclosure, tampering, and denial of service).

The exposure applies to the multi-cluster / remote data-plane topology, where the cluster-gateway is published outside the cluster so remote data-plane agents can connect. That same externally reachable listener also served the caller-facing management APIs, which did not authenticate the caller. Deployments that do not publish the cluster-gateway outside the cluster are not affected.

### Patches
Fixed in **1.0.2**, **1.1.2**, and **1.2.0**. The fix moves the caller-facing management APIs onto a separate internal listener that is not published outside the cluster, leaving only the agent-connection endpoint on the externally reachable listener. Upgrading is non-disruptive — no data-plane agent or configuration changes are required beyond the standard chart upgrade. Upgrade path: 1.1.x → 1.1.2, 1.0.x and earlier → 1.0.2, 1.2 line → 1.2.0.

### Workarounds
If you cannot upgrade immediately:
- If you do run remote data planes, restrict reachability of the external gateway endpoint to known data-plane source addresses only (firewall / gateway-level allowlisting).
Severity
9.6 Critical
CVSS 3.1: 9.6 (NVD)
CVSS 3.1: 9.6 (OSV)
Exploitation
EPSS <1%
Type
CWE-306Missing Authentication for Critical Function
CWE-668Exposure of Resource to Wrong Sphere
CWE-862Missing Authorization
Timeline
Published2 Sep 2026
Updated3 Sep 2026
First seen13 Aug 2026
Sources
CVE-2026-73843 · MITRE
Monitor software like this
Free during beta