Sign in Sign up
JA · EN · FR
SecPulse
Categories
CVE-2026-73840 medium CVSS 5.3

Authentication Bypass in github.com/openchoreo/openchoreo (CVE-2026-73840)

Summary

Authentication bypass in github.com/openchoreo/openchoreo (CVE-2026-73840). Risk of unauthorized operations or information disclosure. Exploitable via POST /api/v1alpha1/autobuild. Mitigation: upgrade to 1.0.3 or later.

Original description

The description as published by the source.

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 autobui…

Source: NIST National Vulnerability Database NVD GitHub Advisory

Auto-generated summary

Assembled by SecPulse from the source data (CVSS, CWE, affected versions) using templates — no AI involved. Check the original description and references below for exact details.

A vulnerability tracked as CVE-2026-73840 has been found in github.com/openchoreo/openchoreo.
Attackers can target a specific entry point like POST /api/v1alpha1/autobuild over the network to misuse the product.
Risk of unauthorized operations or information disclosure. CVSS score: 5.3/10.
What to do: upgrade github.com/openchoreo/openchoreo to 1.0.3 or later.
If unsure, ask your IT team or search "github.com/openchoreo/openchoreo CVE-2026-73840" on the vendor's site.

CVE-2026-73840 (github.com/openchoreo/openchoreo) — CWE-287 / CVSS v3 5.3
Attack vector: remote (network-reachable) / unauthenticated / no user interaction
Attack surface: POST /api/v1alpha1/autobuild
Patched: 1.0.3 — apply immediately
Plan: 1) Audit SBOM/dependencies, 2) Stage→prod upgrade, 3) Add WAF/proxy monitoring on affected endpoints, 4) Hunt IOCs in logs.
Refs: see the GHSA / vendor advisory / patched release linked on this page.

❓ What is the problem

Authentication bypass (CWE-287) exists in github.com/openchoreo/openchoreo. Attackers reach the vulnerable code path via POST /api/v1alpha1/autobuild without authentication.

📍 Affected scope

Check the vendor advisory for the affected versions of github.com/openchoreo/openchoreo. Attack surface: POST /api/v1alpha1/autobuild.

🔥 Severity

Severity: Medium (CVSS 5.3/10). Risk of unauthorized operations or information disclosure.

🔧 How to fix

Update to 1.0.3.

🛡️ Workaround

Until the patch is applied: disable the affected feature, apply WAF rules, or restrict access via network ACLs.

🔍 Detection

Search webserver/proxy logs for unusual POST /api/v1alpha1/autobuild requests with malformed payloads or SQL meta-characters. Run grep -r 'github.com/openchoreo/openchoreo' . against your dependency files (package-lock.json, requirements.txt, go.sum) to find affected services.

Response actions

Concrete steps and command examples for SOC/SRE teams to execute in order

  1. 1
    Identify exposure identify 
    grep -r 'github.com/openchoreo/openchoreo' . | grep -v node_modules

    リポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で github.com/openchoreo/openchoreo を grep し、稼働しているサービス・バージョンを把握する。

  2. 2
    Hunt for indicators of compromise detect 
    grep 'POST /api/v1alpha1/autobuild' /var/log/nginx/access.log | grep -E '(unusual_payload|sqli_pattern)'

    アクセスログで POST /api/v1alpha1/autobuild への異常なリクエスト (不正な認証ヘッダ・SQLメタ文字)を過去 30〜90日分捜索。WAF/SIEM があれば該当パスのアラート発火履歴を確認。

  3. 3
    Apply patch patch 
    Upgrade github.com/openchoreo/openchoreo to 1.0.3

    ステージング環境で 1.0.3 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスと、Step 2 で見つけた異常検知の続報チェックを含めること。

  4. 4
    Post-deployment verification verify 
    Replay attack against POST /api/v1alpha1/autobuild on staging to confirm patch closes the vector

    パッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番では Step 2 と同じログクエリでアラート再発が無いか継続監視。

Affected packages

go github.com/openchoreo/openchoreo
[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"1.2.0-rc.2"}]}]

References

We use cookies for analytics and ad measurement. This setting applies to all Game co., Ltd. sites. Details