The cluster‑gateway internal proxy in OpenChoreo exposed several endpoints (/api/proxy/, /api/exec/, /api/wirelogs/) on an internal listener without requiring client certificates or tokens. This lack of caller authentication and the absence of read‑only restrictions let any network‑reachable caller read tenant Kubernetes Secrets, mutate workloads, and execute commands on data planes. The vulnerability is classified as an authority/privilege management flaw (CWE‑269), missing authentication (CWE‑306), and missing authorization (CWE‑862). It could lead to data exfiltration and arbitrary modification of cluster resources, compromising confidentiality, integrity, and availability.

The issue affects OpenChoreo deployments running any of the affected versions: before 1.0.3, before 1.1.3, or before 1.2.0‑rc.2, regardless of the tenant or cluster environment. The product is used as an open‑source developer platform for Kubernetes, and the flaw resides in the internal cluster‑gateway component.

The CVSS score of 9.0 indicates critical severity. EPSS is not available, so the exploitation likelihood cannot be quantified here, but the absence of authentication and authorization makes exploitation trivial for any actor with network reach to the internal listener. The vulnerability is not yet listed in the CISA KEV catalog, but the potential for immediate data loss and cluster tampering warrants urgent action. Attackers could simply send HTTP requests to the exposed endpoints to pull secret payloads or modify deployment manifests.