OpenChoreo: cluster-gateway internal proxy performs no caller authentication and is not read-only — data-plane Secret disclosure and arbitrary Kubernetes mutation
Published 4 Sept 2026 · Updated 10 Sept 2026
Is your project on an affected github.com/openchoreo/openchoreo?
Look after several Go apps? Indie watches up to 15 repos, private ones too, for $5 a month. See Indie
Affected packages
- Affected
- <1.0.3
- Fixed in
- 1.0.3
go get github.com/openchoreo/openchoreo@v1.0.3- Affected
- >=1.1.0 <1.1.3
- Fixed in
- 1.1.3
go get github.com/openchoreo/openchoreo@v1.1.3- Affected
- >=1.2.0-rc.1 <1.2.0
- Fixed in
- 1.2.0
go get github.com/openchoreo/openchoreo@v1.2.0Details
Summary
The OpenChoreo control-plane cluster-gateway exposes internal management APIs (/api/proxy/, /api/exec/, /api/wirelogs/) that tunnel requests through to connected data planes' Kubernetes APIs, but the internal listener authenticates no caller. Its request validator permits mutating HTTP methods and reads of Secrets in tenant namespaces (only kube-system Secrets are blocked), so although the client library documents these requests as "read-only," the server enforces no such restriction. Any party able to reach the internal listener can — with no client certificate or token — read Secrets in any tenant namespace, create/modify/delete workloads, and exec into pods across every connected data plane.
Impact
An attacker with network access to the cluster-gateway internal listener obtains tunneled access to every connected data plane's Kubernetes API with no caller-level access control. Across all connected data planes, this allows:
- Secret disclosure — reading any Secret outside
kube-systemin any tenant namespace (database credentials, cloud/KMS keys, TLS private keys), independent of any workload ServiceAccount permissions. - Workload tampering or destruction — creating, modifying, or deleting Deployments, Services, and other resources.
- Pod command execution inside workload pods via
/api/exec/.
This is also the missing second authorization layer behind GHSA-52gf-6rpq-fgmx (the openchoreo-api exec/wirelogs cross-project authorization bypass): because the gateway provides no compensating authorization, that bypass — and any other authz gap or SSRF that reaches the internal API — reaches the data-plane Kubernetes API unchecked.
Direct exploitability depends on the network isolation of the internal listener, which is not fixed in source. Where the internal port is reachable by untrusted workloads with no restrictive NetworkPolicy — and with impact landing in a separate data-plane cluster — this is Critical; it is scored conservatively as High otherwise.
Patches
Fixed in 1.0.3, 1.1.3, and 1.2.0. Upgrade path: 1.1.x → 1.1.2, 1.0.x and earlier → 1.0.2, 1.2.0-rc1 line → 1.2.0.
Is GHSA-rh53-xvx2-j327 in any of your client repos?
Checking one package by hand is fine. Checking it across forty client projects is not. NPMscan reads the lockfiles in every GitHub repo you pick, finds each project with an affected github.com/openchoreo/openchoreo, and gives you the command that fixes it.
More advisories for github.com/openchoreo/openchoreo
- LowCVE-2026-113727OpenChoreo: Authorization bypass on WorkflowRun update allows cross-project takeover of workflow runs in github.com/openchoreo/openchoreo · 5 Nov 2026
- HighCVE-2026-113727OpenChoreo: Authorization bypass on WorkflowRun update allows cross-project takeover of workflow runs · 21 Oct 2026
- LowCVE-2026-73667OpenChoreo: Authenticated OS command injection via OpenChoreo Workflow Plane templates enables code execution in privileged pods in github.com/openchoreo/openchoreo · 10 Sept 2026
- LowCVE-2026-73841OpenChoreo: Cross-project command execution and wirelog view access via OpenChoreo openchoreo-api exec and wirelogs endpoints in github.com/openchoreo/openchoreo · 10 Sept 2026
- LowCVE-2026-73840OpenChoreo: Unauthenticated build/workflow trigger via git-provider confusion (webhook signature bypass) in github.com/openchoreo/openchoreo · 10 Sept 2026
- LowCVE-2026-73843OpenChoreo: Unauthenticated access to data-plane operations via OpenChoreo cluster-gateway management APIs in github.com/openchoreo/openchoreo · 10 Sept 2026
References
- Linkgithub.com/openchoreo/openchoreo/security/advisories/GHSA-rh53-xvx2-j327
- Advisorynvd.nist.gov/vuln/detail/CVE-2026-73842
- Linkgithub.com/openchoreo/openchoreo/pull/4256
- Linkgithub.com/openchoreo/openchoreo/pull/4258
- Linkgithub.com/openchoreo/openchoreo/pull/4259
- Linkgithub.com/openchoreo/openchoreo/commit/50fcae3f1753fd0ac3ae655a3fc080a761c49c04
- Linkgithub.com/openchoreo/openchoreo/commit/93e6f10953cfc249af2222ddb6730d4b0a729129
- Linkgithub.com/openchoreo/openchoreo/commit/e3da3c63dcf0895c693cb17ce142ef95e959b62a
- Packagegithub.com/openchoreo/openchoreo
- Linkgithub.com/openchoreo/openchoreo/releases/tag/v1.0.3
- Linkgithub.com/openchoreo/openchoreo/releases/tag/v1.1.3
- Linkgithub.com/openchoreo/openchoreo/releases/tag/v1.2.0-rc.2
Advisory data from OSV.dev (opens OSV.dev in a new tab), refreshed daily.