CVE-2026-73843: OpenChoreo cluster-gateway authentication bypass

CVE-2026-73843 · Severity: critical · CVSS 9.6 · Published 2026-08-13

OpenChoreo is a multi-cluster application orchestration platform that uses a control-plane component called cluster-gateway to manage data-plane operations. In multi-cluster deployments, the cluster-gateway is exposed externally to allow remote agents to connect. However, the management APIs that control sensitive workload operations (including Kubernetes API proxy and pod command execution) were served on the same public endpoint without authentication. An attacker with network access to this endpoint could perform privileged operations and fully compromise workloads on the affected data plane.

Technologies: github.com/openchoreo/openchoreo (Go), OpenChoreo. Vendors: Go, OpenChoreo.

Quick answers

Is CVE-2026-73843 exploited in the wild?
No. Junglewise Threat Intelligence has no report of CVE-2026-73843 being exploited in the wild.
How severe is CVE-2026-73843?
Critical severity, with a CVSS score of 9.6, published 13 August 2026.
Which products and versions are affected?
github.com/openchoreo/openchoreo (Go) SEMVER:introduced=0,fixed=1.0.2, SEMVER:introduced=0,fixed=1.0.2,introduced=1.1.0,fixed=1.1.2; OpenChoreo < 1.0.2, >= 1.1.0 and < 1.1.2.
Is there a fix for CVE-2026-73843?
Yes. github.com/openchoreo/openchoreo (Go): upgrade to 1.0.2, 1.1.2 or later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
How is CVE-2026-73843 attacked?
It is attacked over the network, in a hosted service.
Am I affected by CVE-2026-73843?
Check whether you run github.com/openchoreo/openchoreo (Go) or OpenChoreo at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

How to fix

  • github.com/openchoreo/openchoreo (Go): upgrade to 1.0.2, 1.1.2 or later
    go get github.com/openchoreo/openchoreo@v1.1.2

Technical details

The vulnerability is a missing authentication and authorization flaw (CWE-306, CWE-862) in the OpenChoreo control-plane cluster-gateway component. The root cause is architectural: caller-facing management APIs that perform critical data-plane operations (Kubernetes API proxying, workload pod command execution) were exposed on the same network listener (public endpoint) used for legitimate data-plane agent connections, without any authentication of the caller. In multi-cluster topologies, this listener is published outside the cluster for remote agents to connect. An unauthenticated attacker able to reach this endpoint can directly invoke privileged operations normally restricted to the OpenChoreo API server and gated by its authorization system. This allows full compromise of workloads: disclosure (data access), tampering (code/configuration modification), and denial of service. The fix (versions 1.0.2, 1.1.2, 1.2.0+) moves management APIs to a separate internal listener not exposed outside the cluster, leaving only the agent-connection endpoint on the external listener. The attack vector is network-adjacent (AV:A), reflecting the requirement to reach the externally published gateway; no authentication or user interaction is required (PR:N/UI:N), and the scope changes beyond the vulnerable component.

Affected products

  • OpenChoreo OpenChoreo < 1.0.2, >= 1.1.0 and < 1.1.2

Identifiers

  • CVE-2026-73843
  • GHSA-qh9r-j7rp-4x2m
  • GO-2026-6362

Timeline

  • 2026-07-09: disclosed: Vulnerability published to GitHub Advisory Database
  • 2026: patched: Patches released in versions 1.0.2, 1.1.2, and 1.2.0
  • 2026-09-02: advisory: Security advisory published (GHSA-qh9r-j7rp-4x2m)
  • 2026-08-13: other: CVE-2026-73843 published to NVD

References

This page as Markdown. Free to reuse under CC BY 4.0 with a link back.