Severity by source
AV:A/AC:L/PR:N/UI:N/S:C/C:H/I:H/A:H
Description says the listener is externally reachable by network attackers, so AV:N rather than NVD's AV:A; no auth or interaction (PR:N/UI:N), and pivoting into data-plane clusters/pods changes scope (S:C) with full C/I/A loss.
Primary rating from Vendor (github).
CVSS VectorVendor: github
CVSS:3.1/AV:A/AC:L/PR:N/UI:N/S:C/C:H/I:H/A:H
Lifecycle Timeline
4DescriptionCVE.org
OpenChoreo is a complete, open-source developer platform for Kubernetes. Prior to 1.0.2 and 1.1.2, internal/cluster-gateway/server.go served caller-facing management APIs on the externally reachable agent listener without authentication, allowing network-reachable attackers to invoke /api/proxy/ and /api/exec/ operations, proxy the data-plane Kubernetes API, and execute commands in workload pods in multi-cluster deployments. This issue is fixed in versions 1.0.2 and 1.1.2.
Articles & Coverage 1
AnalysisAI
Missing authentication on OpenChoreo's cluster-gateway (before 1.0.2 and 1.1.2) exposed caller-facing management APIs on the same externally reachable listener used for agent WebSocket traffic, letting network-reachable attackers hit /api/proxy/ and /api/exec/ without any credentials. In multi-cluster deployments this permits proxying the data-plane Kubernetes API and executing commands inside workload pods, effectively yielding cross-cluster control. …
Unlock full vulnerability intelligence
- Risk assessment & exploitation conditions
- Attack chain visualization
- Remediation with exact patch versions
- Threat intelligence from 22 sources
- Personal watchlist & email alerts
Free forever · No credit card required
Attack ChainAIDerived
Hypothetical attack flow derived from CVE metadata
Vulnerability AssessmentAI
| Exploitation | Requires a multi-cluster OpenChoreo deployment (before 1.0.2/1.1.2) where the cluster-gateway agent listener - which in the vulnerable design co-hosts the /api/proxy/ and /api/exec/ endpoints on the public port 8443 - is network-reachable by the attacker. … Additional conditions and limiting factors are described in the full assessment. |
| Risk Assessment | All available signals point to genuine high priority. … Full risk analysis with EPSS, KEV, and SSVC signal comparison available after sign-in. |
| Exploit Scenario | An attacker who can reach the OpenChoreo cluster-gateway listener (for example from an adjacent network segment or an over-exposed data-plane endpoint) sends unauthenticated requests to /api/proxy/ to tunnel to a data-plane cluster's Kubernetes API, then calls /api/exec/ to run commands inside a workload pod. With low attack complexity and no authentication or user interaction required, this yields remote code execution and cross-cluster compromise; no public POC was referenced at time of analysis. |
| Remediation | Vendor-released patch: upgrade to OpenChoreo 1.0.2 (1.0.x line) or 1.1.2 (1.1.x line), which move the /api/* management endpoints onto a separate internal listener (port 8444, flag --internal-port / env AGENT_INTERNAL_PORT) intended for in-cluster callers only, leaving the public listener serving only the /ws agent WebSocket. … Detailed patch versions, workarounds, and compensating controls in full report. |
Recommended ActionAI
Within 24 hours: immediately inventory all OpenChoreo cluster-gateway deployments and document version numbers; implement network-level firewall rules to block external and untrusted traffic to cluster-gateway listeners, specifically denying public access to /api/proxy/ and /api/exec/ endpoints; restrict cluster-gateway access to internal networks only. …
Sign in for detailed remediation steps and compensating controls.
Threat intelligence, references, and detailed analysis are available after sign-in.
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 technique Authentication Bypass
View allShare
External POC / Exploit Code
Leaving vuln.today
EUVD-2026-58518