EUVD-2026-58516
GHSA-rh53-xvx2-j327
Attack ChainAIDerived
Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain
-
AccessGain in-cluster network foothold
-
DeliveryReach unauthenticated gateway internal listener
-
ExploitCall /api/exec and /api/proxy without credentials
-
ExecutionExecute commands and read tenant Secrets on data planes
-
ImpactMutate workloads and pivot across clusters
Vulnerability Assessment
| Weakness |
CWE
OWASP Top 10:2025
A06:2025 - Insecure Design
ASVS 5.0
V8 - Authorization Least privilege enforcement
MITRE ATT&CK
1 technique across 1 tactic: Privilege Escalation The technique list with ATT&CK links and the kill-chain view is part of the Basic plan and up. |
| Exploitation Conditions | Exploitation requires network reachability to the cluster-gateway's internal API listener (CVSS AV:A, adjacent) that serves /api/proxy/, /api/exec/, and /api/wirelogs/ - typically an in-cluster position such as a compromised pod, a workload sharing the pod/service network, or a listener inadvertently exposed on a routable interface. On vulnerable versions the endpoints accept requests with no client certificate and no bearer token, so no valid credentials are needed once the listener is reachable; the deployment must be running OpenChoreo before 1.0.3/1.1.3/1.2.0-rc.2 with the internal listener bound where the attacker can reach it. The main limiting factor is that the listener is intended to be internal-only, so environments that already firewall or NetworkPolicy-restrict it to controller-manager and openchoreo-api dramatically shrink the attack surface even before patching; there is a data conflict between the NVD PR:L rating and the description's no-cert/no-token claim, which defenders should verify against their own network exposure. |
| Impact | This is a genuine high-priority issue: the CVSS 3.1 vector (AV:A/AC:L/PR:L/UI:N/S:C, C:H/I:H/A:H, base 9.0) reflects low complexity, no user interaction, and a scope change that spans from the gateway into connected data planes, which matches the described ability to read Secrets, mutate workloads, and run commands cluster-wide. There is a notable discrepancy that defenders must reconcile: NVD scored PR:L (some privilege), yet the description explicitly states the endpoints required no client certificate or token, which argues for PR:N (unauthenticated) - I assess this as effectively unauthenticated on the internal network and have scored it accordingly below. No EPSS score, KEV entry, or POC was provided, so exploitation is not confirmed in the wild; the AV:A rating means an attacker still needs adjacency to the internal listener (in-cluster foothold, pod network reach, or a misconfigured/over-exposed listener) rather than raw internet access, which limits opportunistic mass exploitation. Given that any lateral-movement foothold near the gateway yields full multi-tenant, multi-cluster compromise, even a small platform team running a handful of clusters should treat this as urgent and patch immediately rather than waiting for a public exploit. |
| Exploit ScenarioDerived | An attacker who gains a foothold on the cluster network - for example a compromised pod or a workload on the same segment as the cluster-gateway - sends unauthenticated HTTP requests to the internal /api/exec/ endpoint and executes commands inside pods on a connected data plane, then queries /api/proxy/ to dump tenant Kubernetes Secrets. Because low attack complexity and no user interaction are required, this can be scripted for rapid cross-tenant, multi-cluster compromise; no public POC was provided in the input. |
Get an e-mail when this CVE is exploited, patched or re-scored. Free account.
Alert meAnalysisAIv1 – Aug 13, 2026
Missing authentication in OpenChoreo's cluster-gateway internal API lets any network-reachable caller invoke /api/proxy/, /api/exec/, and /api/wirelogs/ without a client certificate or token, exposing tenant Kubernetes Secrets and allowing workload mutation and arbitrary command execution across every connected data plane. All deployments before 1.0.3, 1.1.3, and 1.2.0-rc.2 are affected, and the fix introduces an opt-in --internal-mtls mode plus a dedicated internal CA. No public exploit has been identified at time of analysis, and the flaw is not listed in CISA KEV; risk is amplified because the internal listener effectively brokers cross-tenant, multi-cluster control-plane access.
RemediationAI
Vendor-released patch: upgrade to OpenChoreo 1.0.3, 1.1.3, or 1.2.0-rc.2 depending on your release line, per GHSA-rh53-xvx2-j327 and the corresponding release tags and PRs (https://github.com/openchoreo/openchoreo/pull/4256, /4258, /4259; commits 50fcae3, 93e6f10, e3da3c6). After upgrading, enable the new internal mTLS protection by setting clusterGateway.internalMtls.enabled=true (with clusterGateway.tls.enabled=true) in the Helm chart, which provisions a dedicated internal CA and issues client certificates to controller-manager and openchoreo-api; note the deprecated --skip-client-cert-verify flag no longer has any effect. If you cannot upgrade immediately, restrict network reachability to the cluster-gateway internal listener as a compensating control - apply Kubernetes NetworkPolicies (or host/firewall rules) so only the controller-manager and openchoreo-api pods can reach the /api/* internal port, and ensure that listener is never exposed beyond the cluster; the trade-off is that overly tight policies can break legitimate control-plane-to-gateway traffic, so validate connectivity for controller-manager and openchoreo-api after applying them.
Affected VersionsENISA
Affected Packages
Source: OSV (Open Source Vulnerabilities)
Affects your stack
Affects 3 packages in go, euvd
Checking this CVE against your own stacks and servers is part of the Basic plan and up.
Technical ContextAI · show details
OpenChoreo is a Kubernetes-native developer/PaaS platform; the affected component is the cluster-gateway, which brokers control-plane-to-data-plane traffic. The vulnerable code in internal/cluster-gateway/server.go bound the internal API endpoints (/api/proxy/ for Kubernetes API proxying, /api/exec/ for pod command execution, /api/wirelogs/ for traffic logs) to a listener that performed no client-certificate or token verification. The root cause maps to CWE-269 (Improper Privilege Management): the gateway held broad, trusted access to connected data planes but failed to authenticate callers of its internal interface, so any reachable client inherited the gateway's privileges. The commit diffs show the remediation adds an --internal-mtls flag (INTERNAL_MTLS_ENABLED) and a separate internal client CA, deliberately distinct from the agent CA so that data-plane agent certificates cannot authenticate to the internal API; the previously relied-upon --skip-client-cert-verify flag was deprecated as having no effect.
Know when Kubernetes gets its next vulnerability
- Watch products and get an email when something new is published
- Check this CVE against your own stack and servers
- Exploit and PoC references, threat intelligence from 22 sources
No credit card · 7-day full trial
Severity by source
AV:A/AC:L/PR:L/UI:N/S:C/C:H/I:H/A:H
Description states no client cert or token is required so PR:N not PR:L; internal listener implies adjacent AV:A, low complexity, and gateway-to-data-plane reach gives S:C with full C/I/A impact.
Primary rating from Vendor (github).
CVSS VectorVendor: github
Lifecycle Timeline
2DescriptionCVE.org
OpenChoreo is a complete, open-source developer platform for Kubernetes. Prior to 1.0.3, 1.1.3, and 1.2.0-rc.2, internal/cluster-gateway/server.go exposed /api/proxy/, /api/exec/, and /api/wirelogs/ on an internal listener without requiring a client certificate or token, allowing any network-reachable caller to read tenant Kubernetes Secrets, mutate workloads, and execute commands across connected data planes. This issue is fixed in versions 1.0.3, 1.1.3, and 1.2.0-rc.2.
Articles & Coverage 1
Latest POC
1 public PoC link from github
Sign in to open the public PoC links collected for this CVE.
Executive ViewAI
OpenChoreo cluster-gateway (versions before 1.0.3, 1.1.3, and 1.2.0-rc.2) contains a critical authentication bypass in its internal API, allowing any network-reachable attacker to access Kubernetes Secrets, modify workloads, and execute arbitrary commands across all connected data planes. Organizations running affected versions face immediate risk of multi-tenant data exposure and operational compromise of their Kubernetes infrastructure.
No vendor-released patch identified at time of analysis. Interim mitigations include: restrict network access to the internal listener using firewall rules and Kubernetes network policies limited to trusted internal systems only; implement enhanced monitoring and alerting on the vulnerable API endpoints to detect unauthorized access attempts; rotate Kubernetes Secrets regularly to limit exposure window if a breach occurs; implement network segmentation to isolate cluster-gateway from untrusted networks. These controls significantly reduce risk but do not eliminate the vulnerability; patching is mandatory once available.
Threat Intelligence Overview
NVD
CVE.org
EPSS
How this decision was reached
The engine reads each signal below and applies a fixed list of rules from top to bottom. The first rule that matches sets the recommended action – like a statement, every line is shown.
What every action level means
SSVC AssessmentENISA
Priority Score
Attack Technique
Privilege escalation occurs when an attacker leverages flaws in access control mechanisms to gain permissions beyond what they were originally granted.
More in Kubernetes
View allA critical vulnerability in Kubernetes ingress-nginx controller allows unauthenticated attackers with pod network access
Credential-harvesting malware compromised 84 versions of 42 TanStack npm packages on 2026-05-11 via chained GitHub Actio
Kubernetes ingress-nginx contains a configuration injection vulnerability via the mirror-target and mirror-host Ingress
A security issue was discovered in ingress-nginx https://github.com/kubernetes/ingress-nginx where the `auth-url` Ingres
A security issue was discovered in ingress-nginx https://github.com/kubernetes/ingress-nginx where the `auth-tls-match-c
Kubernetes API server in all versions allow an attacker who is able to create a ClusterIP service and set the spec.exter
A security issue was discovered in Kubernetes where a user that can create pods on Windows nodes may be able to escalate
Argo CD is a declarative, GitOps continuous delivery tool for Kubernetes. Rated critical severity (CVSS 9.9), this vulne
Unauthenticated remote attackers can trigger complete database overwrites, server-side file reads, and SSRF attacks agai
The Kubernetes integration in GitLab Enterprise Edition 11.x before 11.2.8, 11.3.x before 11.3.9, and 11.4.x before 11.4
Fluentd configuration injection in the kube-logging Logging operator before 6.6.0 allows a namespace-scoped user who can
Kyverno Kubernetes policy engine prior to 1.x has a privilege escalation vulnerability (CVSS 9.9) allowing policy bypass
Same weakness CWE-269 – Improper Privilege Management
View allSame technique Privilege Escalation
View allVendor StatusVendor
SUSE
Severity: Critical| Product | Status |
|---|---|
| SUSE Linux Enterprise Module for Package Hub 15 SP5 | Affected |
| SUSE Linux Enterprise Module for Package Hub 15 SP6 | Affected |
| openSUSE Leap 15.5 | Affected |
| openSUSE Leap 15.6 | Affected |
Exploit-DB