CVE-2026-73841: OpenChoreo Cross-project Command Execution And Wirelog Vulnerability

HIGH
Advisory Identifier: GHSA-52gf-6rpq-fgmx
CVSS 8.8
CWE-639 CWE-863
Published
Advisory Summary

CVE-2026-73841 is a HIGH (CVSS 8.8) cross-project command execution and wirelog vulnerability (CWE-639: Authorization Bypass Through User-Controlled Key) affecting OpenChoreo libraries in the Go ecosystem. The issue involves cross-project command execution and wirelog view access via openchoreo openchoreo-api exec and wirelogs endpoints. Remediation is available by upgrading affected packages to version 1.2.3, 1.1.6.

CVE-2026-73841 at a Glance

CVE Identifier CVE-2026-73841
GHSA Identifier GHSA-52gf-6rpq-fgmx
Severity HIGH
CVSS v3.1 Base Score 8.8
CWE Classification CWE-639: Authorization Bypass Through User-Controlled Key
Affected Product OpenChoreo
Package Ecosystem Go
Published Date
Last Updated

Security Impact

CVSS: 8.8

The security impact metrics below are parsed directly from the CVSS v3.1 vector string (CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H).

Attack Vector Network (AV:N)
Attack Complexity Low (AC:L)
Privileges Required Low (PR:L)
User Interaction None (UI:N)
Scope Unchanged (S:U)
Confidentiality High (C:H)
Integrity High (I:H)
Availability High (A:H)

How to Fix CVE-2026-73841

To remediate this vulnerability, upgrade all affected OpenChoreo dependencies to a patched release. Both direct and transitive dependencies should be checked, as frameworks or security libraries may pull in vulnerable versions transitively.

github.com/openchoreo/openchoreo fixed: 1.2.3
Upgrade github.com/openchoreo/openchoreo to 1.2.3
github.com/openchoreo/openchoreo fixed: 1.1.6
Upgrade github.com/openchoreo/openchoreo to 1.1.6
Verify Direct and Transitive Dependencies

Run the following command in your project directory to verify that all resolved dependencies use the patched release:

inspect dependencies for github.com/openchoreo/openchoreo

How to Check if You Are Affected

To determine whether your application is affected by CVE-2026-73841, inspect your project dependencies for OpenChoreo:

inspect dependencies for github.com/openchoreo/openchoreo

Analyze the terminal output to locate any version of OpenChoreo in your dependency tree. If any resolved version matches the vulnerable ranges listed in the table below (for example, versions earlier than 1.2.3), your application is affected.

Note: Verify declared build manifests and deployed runtime container environments.

Technical Details

Vulnerability Mechanism & Technical Analysis

This vulnerability is classified under CWE-639: Authorization Bypass Through User-Controlled Key, where the system's authorization functionality does not prevent one user from gaining access to another user's data or record by modifying the key value identifying the data. In OpenChoreo, software state validation or input boundaries are circumvented during processing. Review the official source advisory statement below for specific affected components, classes, and reproduction details.

Source Advisory Statement

### 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 does not cross namespace boundaries. In effect this is a cross-project (cross-team) remote command-execution and data-access primitive available to any low-privileged tenant. ### Patches Fixed in **1.2.3** and **1.1.6**. The fix aligns the exec and wirelogs endpoints with the pattern already used by other first-class component operations: the target component is fetched first and authorization is evaluated against its real owning project (`comp.Spec.Owner.ProjectName`) instead of the caller-supplied `project` query parameter. ### Workarounds If you cannot upgrade immediately: - Restrict `component:exec` and `wirelogs:view` grants to trusted operators only. Any holder of such a grant on any project can reach every component in the same namespace. - Where stronger isolation is required, separate sensitive components into their own namespaces, since the flaw does not cross namespace boundaries. ### Related advisories - `GHSA-rh53-xvx2-j327` — the cluster-gateway internal proxy applies no caller authorization, so this API-layer authorization bypass reaches the data-plane Kubernetes API with no compensating control: https://github.com/openchoreo/openchoreo/security/advisories/GHSA-rh53-xvx2-j327 - `GHSA-c5f6-2rm9-2w8g` — reported together as part of the same review.

CVE-2026-73841 Affected OpenChoreo Versions

2 component(s)
Fixed Versions:
1.2.31.1.6
Product / Package Ecosystem Affected Versions Fixed Version
github.com/openchoreo/openchoreo
Go
≥ 1.2.0-m.1
< 1.2.3
1.2.3
github.com/openchoreo/openchoreo
Go
< 1.1.6
1.1.6

References

Frequently Asked Questions

What is CVE-2026-73841?
CVE-2026-73841 is a security vulnerability in OpenChoreo involving Cross-project command execution and wirelog view access via OpenChoreo openchoreo-api exec and wirelogs endpoints under CWE-639: Authorization Bypass Through User-Controlled Key.
Which OpenChoreo versions are affected?
Affected versions include releases prior to 1.2.3, 1.1.6 across affected packages: github.com/openchoreo/openchoreo.
What version fixes CVE-2026-73841?
Upgrading to 1.2.3, 1.1.6 (or the latest patched release for your respective branch) resolves the vulnerability.
Is github.com/openchoreo/openchoreo affected?
Yes, github.com/openchoreo/openchoreo is affected in releases prior to 1.2.3, 1.1.6. Upgrade your dependency to 1.2.3, 1.1.6 or later.
What is the CVSS score of CVE-2026-73841?
CVE-2026-73841 has a CVSS v3.1 base score of 8.8 (HIGH) with vector string CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H.
What CWE is associated with CVE-2026-73841?
CVE-2026-73841 is classified under CWE-639: Authorization Bypass Through User-Controlled Key (The system's authorization functionality does not prevent one user from gaining access to another user's data or record by modifying the key value identifying the data.).
How can I check Go dependencies for CVE-2026-73841?
Run the dependency tree command: 'inspect dependencies for github.com/openchoreo/openchoreo'. This command lists direct and transitive dependencies in your build configuration so you can verify if a vulnerable version is resolved.
Machine-readable OSV JSON OSV v1.5 Schema
Normalized schema output
{
  "schema_version" : "1.4.0",
  "id" : "GHSA-52gf-6rpq-fgmx",
  "modified" : "2026-09-02T23:44:51Z",
  "published" : "2026-09-02T23:44:51Z",
  "aliases" : [ "CVE-2026-73841" ],
  "summary" : "OpenChoreo: Cross-project command execution and wirelog view access via OpenChoreo openchoreo-api exec and wirelogs endpoints",
  "details" : "### Summary\n\nThe 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.\n\n### Impact\n\nAn 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.\n\nThe 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 does not cross namespace boundaries. In effect this is a cross-project (cross-team) remote command-execution and data-access primitive available to any low-privileged tenant.\n\n### Patches\n\nFixed in **1.2.3** and **1.1.6**. The fix aligns the exec and wirelogs endpoints with the pattern already used by other first-class component operations: the target component is fetched first and authorization is evaluated against its real owning project (`comp.Spec.Owner.ProjectName`) instead of the caller-supplied `project` query parameter.\n\n### Workarounds\n\nIf you cannot upgrade immediately:\n\n- Restrict `component:exec` and `wirelogs:view` grants to trusted operators only. Any holder of such a grant on any project can reach every component in the same namespace.\n- Where stronger isolation is required, separate sensitive components into their own namespaces, since the flaw does not cross namespace boundaries.\n\n### Related advisories\n\n- `GHSA-rh53-xvx2-j327` — the cluster-gateway internal proxy applies no caller authorization, so this API-layer authorization bypass reaches the data-plane Kubernetes API with no compensating control: https://github.com/openchoreo/openchoreo/security/advisories/GHSA-rh53-xvx2-j327\n- `GHSA-c5f6-2rm9-2w8g` — reported together as part of the same review.",
  "severity" : [ {
    "type" : "CVSS_V3",
    "score" : "CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H"
  } ],
  "affected" : [ {
    "package" : {
      "ecosystem" : "Go",
      "name" : "github.com/openchoreo/openchoreo"
    },
    "ranges" : [ {
      "type" : "ECOSYSTEM",
      "events" : [ {
        "introduced" : "1.2.0-m.1"
      }, {
        "fixed" : "1.2.3"
      } ]
    } ]
  }, {
    "package" : {
      "ecosystem" : "Go",
      "name" : "github.com/openchoreo/openchoreo"
    },
    "ranges" : [ {
      "type" : "ECOSYSTEM",
      "events" : [ {
        "introduced" : "0"
      }, {
        "fixed" : "1.1.6"
      } ]
    } ]
  } ],
  "references" : [ {
    "type" : "WEB",
    "url" : "https://github.com/openchoreo/openchoreo/security/advisories/GHSA-52gf-6rpq-fgmx"
  }, {
    "type" : "ADVISORY",
    "url" : "https://nvd.nist.gov/vuln/detail/CVE-2026-73841"
  }, {
    "type" : "WEB",
    "url" : "https://github.com/openchoreo/openchoreo/pull/4251"
  }, {
    "type" : "WEB",
    "url" : "https://github.com/openchoreo/openchoreo/pull/4516"
  }, {
    "type" : "WEB",
    "url" : "https://github.com/openchoreo/openchoreo/pull/4538"
  }, {
    "type" : "WEB",
    "url" : "https://github.com/openchoreo/openchoreo/commit/4d372eaf1f07525663dcca5257062f4b051b9820"
  }, {
    "type" : "WEB",
    "url" : "https://github.com/openchoreo/openchoreo/commit/9d77b64f747eba89247c47ebfeffec591c4cd2d8"
  }, {
    "type" : "WEB",
    "url" : "https://github.com/openchoreo/openchoreo/commit/c9390e4fcb9953f43b07cb48197576182301593d"
  }, {
    "type" : "PACKAGE",
    "url" : "https://github.com/openchoreo/openchoreo"
  }, {
    "type" : "WEB",
    "url" : "https://github.com/openchoreo/openchoreo/releases/tag/v1.1.6"
  }, {
    "type" : "WEB",
    "url" : "https://github.com/openchoreo/openchoreo/releases/tag/v1.2.3"
  } ],
  "database_specific" : {
    "cwe_ids" : [ "CWE-639", "CWE-863" ],
    "severity" : "HIGH",
    "github_reviewed" : true,
    "github_reviewed_at" : "2026-09-02T23:44:51Z",
    "nvd_published_at" : "2026-08-13T22:17:28Z"
  }
}