Sign in Sign up
JA · EN · FR
SecPulse
Categories
CVE-2026-73843 critical CVSS 9.6

Vulnerability in github.com/openchoreo/openchoreo (CVE-2026-73843)

Summary

Vulnerability in github.com/openchoreo/openchoreo (CVE-2026-73843). Successful exploitation can lead to full system takeover. Mitigation: upgrade to 1.1.2 or later.

Original description

The description as published by the source.

Summary

The OpenChoreo control-plane cluster-gateway served its caller-facing management APIs on the same network listener that accepts data-plane agent connections. In the multi-cluster topology that listener is published outside the cluster, and the management APIs did not authenticate the calling client. A party able to reach the listener could therefore invoke privileged data-plane operations without authenticating and without passing through the OpenChoreo API server's authorization.

Impact

An attacker who can reach the externally published cluster-gateway endpoint can perform data-plane operations normally restricted to the OpenChoreo API server and gated by its authorization — including proxying the data plane's Kubernetes API and executing commands inside workload pods. This can result in full compromise of workloads on the affected data plane (disclosure, tampering, and denial of service).

The exposure applies to the multi-cluster / remote data-plane topology, where the cluster-gateway is published outside the cluster so remote data-plane agents can connect. That same externally reachable listener also served the caller-facing management APIs, which did not authenticate the caller. Deployments that do not publish the cluster-gateway outside the cluster are not affected.

Patches

Fixed in 1.0.2, 1.1.2, and 1.2.0. The fix moves the caller-facing management APIs onto a separate internal listener that is not published outside the cluster, le…

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-73843 has been found in github.com/openchoreo/openchoreo.
Successful exploitation can lead to full system takeover. CVSS score: 9.6/10.
What to do: upgrade github.com/openchoreo/openchoreo to 1.1.2 or later.
If unsure, ask your IT team or search "github.com/openchoreo/openchoreo CVE-2026-73843" on the vendor's site.

CVE-2026-73843 (github.com/openchoreo/openchoreo) — CWE-306 / CVSS v3 9.6
Attack vector: adjacent-network / unauthenticated / no user interaction
Patched: 1.1.2 — 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

A vulnerability (CWE-306) exists in github.com/openchoreo/openchoreo.

📍 Affected scope

Check the vendor advisory for the affected versions of github.com/openchoreo/openchoreo.

🔥 Severity

Severity: Critical (CVSS 9.6/10). Successful exploitation can lead to full system takeover.

🔧 How to fix

Update to 1.1.2.

🛡️ 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 request patterns matching this CVE's known IOCs. 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
    Apply patch patch 
    Upgrade github.com/openchoreo/openchoreo to 1.1.2

    ステージング環境で 1.1.2 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスを含めること。

  3. 3
    Post-deployment verification verify 
    Confirm patched version is live in production

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

Affected packages

go github.com/openchoreo/openchoreo
[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"1.1.2"}]}]

References

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