OpenChoreo: Unauthenticated build/workflow trigger via git-provider confusion (webhook signature bypass)
Published 2 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-rc.2
- Fixed in
- 1.2.0-rc.2
go get github.com/openchoreo/openchoreo@v1.2.0-rc.2Details
Summary
The OpenChoreo autobuild webhook endpoint (POST /api/v1alpha1/autobuild) selected the git provider used to authenticate an incoming webhook from a client-supplied request header rather than from the target component's configuration, and its Bitbucket provider accepted requests without a valid signature. A caller could set the X-Event-Key header to be treated as a Bitbucket webhook, bypassing the HMAC secret that otherwise protects GitHub and GitLab webhooks, and trigger a component build without authenticating.
Impact
An attacker who can reach the autobuild webhook endpoint and knows the repository URL and branch configured for an auto-build component can trigger a build for that component without authenticating — including components configured for GitHub or GitLab, since the provider used or verification is chosen by the caller rather than by the component's configuration. The triggered build runs against a commit SHA supplied by the attacker, and the component lookup is not scoped to a tenant or namespace, so any auto-build component across the cluster matching the given repository and branch is affected. This can result in unauthorized builds — and, where auto-deploy is configured, unauthorized deployment of attacker-influenced code — and can be used to exhaust build resources through repeated unauthenticated triggering.
The exposure applies to any component with spec.autoBuild: true, regardless of which git provider it declares, wherever the autobuild webhook endpoint is network-reachable.
Patches
Fixed in 1.0.3, 1.1.3, and 1.2.0-rc.2. The fix validates Bitbucket webhooks with HMAC-SHA256 against the configured secret using the same verification path as GitHub, requires a configured, non-empty secret for every provider (a missing secret now rejects the request instead of skipping validation), and requires the authenticated provider to match the git provider configured for the matched component. Upgrading is non-disruptive — no component or webhook configuration changes are required beyond the standard upgrade. Upgrade path: 1.1.x → 1.1.3, 1.0.x and earlier → 1.0.3, 1.2 line → 1.2.0-rc.2 or later.
Is GHSA-c5f6-2rm9-2w8g 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-73843OpenChoreo: Unauthenticated access to data-plane operations via OpenChoreo cluster-gateway management APIs in github.com/openchoreo/openchoreo · 10 Sept 2026
- LowCVE-2026-73842OpenChoreo: cluster-gateway internal proxy performs no caller authentication and is not read-only — data-plane Secret disclosure and arbitrary Kubernetes mutation in github.com/openchoreo/openchoreo · 10 Sept 2026
References
- Linkgithub.com/openchoreo/openchoreo/security/advisories/GHSA-c5f6-2rm9-2w8g
- Advisorynvd.nist.gov/vuln/detail/CVE-2026-73840
- Linkgithub.com/openchoreo/openchoreo/pull/4239
- Linkgithub.com/openchoreo/openchoreo/pull/4252
- Linkgithub.com/openchoreo/openchoreo/pull/4253
- Linkgithub.com/openchoreo/openchoreo/commit/268efd9b762a3f4f72b55d9c1b13dfc55122127b
- Linkgithub.com/openchoreo/openchoreo/commit/8af4a3fc8725fc2d8a9de9611e77278a5c48f978
- Linkgithub.com/openchoreo/openchoreo/commit/f540553db7143141b73bb37fae02102e6f082a34
- 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.