Sign in Sign up
JA · EN · FR
SecPulse
Categories
CVE-2026-73841 high CVSS 8.8

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

Summary

Vulnerability in github.com/openchoreo/openchoreo (CVE-2026-73841). Successful exploitation can lead to full system takeover. Exploitable via comp.Spec.Owner.ProjectName. Mitigation: upgrade to 1.1.6 or later.

Original description

The description as published by the source.

Summary

The OpenChoreo API server (openchoreo-api) authorized requests to its exec and wirelogs endpoints against the project supplied by the caller in the request, rather than against the project that actually owns the target component. The target component was resolved by name only, and the authorization engine decided purely from the caller-supplied resource hierarchy — the component's real owning project was never checked. As a result, an authenticated user who holds a project-scoped exec or log-viewing grant on any single project could run commands in, and read the wirelogs of, components owned by other projects in the same namespace.

Impact

An authenticated tenant holding a project-scoped component:exec grant on just one project can execute arbitrary commands — including an interactive shell — inside the running pods of components owned by any other project in the same namespace. This exposes those workloads' environment variables and mounted Secrets (such as database credentials, API keys, and tokens), allows tampering with the workload, and enables further pivoting using the workload's own network position and credentials. The same flaw in the wirelogs endpoint lets a project-scoped wirelogs:view grant read any component's wirelogs in the namespace.

The blast radius is every component in the namespace, reachable from a single legitimate project grant. The boundary crossed is project-within-namespace: the request still pins the namespace, so the issue…

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-73841 has been found in github.com/openchoreo/openchoreo.
Attackers can target a specific entry point like comp.Spec.Owner.ProjectName over the network to misuse the product.
Successful exploitation can lead to full system takeover. CVSS score: 8.8/10.
What to do: upgrade github.com/openchoreo/openchoreo to 1.1.6 or later.
If unsure, ask your IT team or search "github.com/openchoreo/openchoreo CVE-2026-73841" on the vendor's site.

CVE-2026-73841 (github.com/openchoreo/openchoreo) — CWE-639 / CVSS v3 8.8
Attack vector: remote (network-reachable) / no user interaction
Attack surface: comp.Spec.Owner.ProjectName / project
Patched: 1.1.6 — 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-639) exists in github.com/openchoreo/openchoreo. Attackers reach the vulnerable code path via comp.Spec.Owner.ProjectName.

📍 Affected scope

Check the vendor advisory for the affected versions of github.com/openchoreo/openchoreo. Attack surface: comp.Spec.Owner.ProjectName / project.

🔥 Severity

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

🔧 How to fix

Update to 1.1.6.

🛡️ 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.6

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

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

References

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