Sign in Sign up
JA · EN · FR
SecPulse
Categories
CVE-2026-73842 critical CVSS 9.0

Privilege Escalation in github.com/openchoreo/openchoreo (CVE-2026-73842)

Summary

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

Original description

The description as published by the source.

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-system in 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): becau…

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-73842 has been found in github.com/openchoreo/openchoreo.
Successful exploitation can lead to full system takeover. CVSS score: 9.0/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-73842" on the vendor's site.

CVE-2026-73842 (github.com/openchoreo/openchoreo) — CWE-269 / CVSS v3 9.0
Attack vector: adjacent-network / no user interaction
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

A vulnerability (CWE-269) 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.0/10). Successful exploitation can lead to full system takeover.

🔧 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 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.0.3

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

  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.2.0"}]}]

References

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