CVE-2026-73841: OpenChoreo openchoreo-api authorization bypass in exec and wirelogs endpoints

CVE-2026-73841 · Severity: high · CVSS 8.8 · Published 2026-08-13

OpenChoreo's API server allows authenticated users to execute commands and read logs on components owned by other projects in the same namespace. A low-privilege user with access to just one project can exploit this to run arbitrary commands on any other project's workloads, exposing sensitive data like database credentials and API keys. The vulnerability fundamentally breaks project isolation within a namespace.

Technologies: github.com/openchoreo/openchoreo (Go). Vendors: Go, OpenChoreo.

Quick answers

Is CVE-2026-73841 exploited in the wild?
No. Junglewise Threat Intelligence has no report of CVE-2026-73841 being exploited in the wild.
How severe is CVE-2026-73841?
High severity, with a CVSS score of 8.8, published 13 August 2026.
Which products and versions are affected?
github.com/openchoreo/openchoreo (Go) SEMVER:introduced=0,fixed=1.1.6,introduced=1.2.0-m.1,fixed=1.2.3, SEMVER:introduced=1.2.0-m.1,fixed=1.2.3.
Is there a fix for CVE-2026-73841?
Yes. github.com/openchoreo/openchoreo (Go): upgrade to 1.2.3 or later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
How is CVE-2026-73841 attacked?
It is attacked over the network.
Am I affected by CVE-2026-73841?
Check whether you run github.com/openchoreo/openchoreo (Go) or OpenChoreo API at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

How to fix

  • github.com/openchoreo/openchoreo (Go): upgrade to 1.2.3 or later
    go get github.com/openchoreo/openchoreo@v1.2.3

Technical details

The vulnerability is an authorization bypass (CWE-639, CWE-863) in the openchoreo-api exec and wirelogs endpoints. The flaw stems from the authorization engine evaluating access control against the caller-supplied project query parameter rather than the actual owning project of the target component. Target components are resolved by name only, and the system never checks the component's real owning project (comp.Spec.Owner.ProjectName). An authenticated user with project-scoped component:exec or wirelogs:view permissions on any single project can use this to execute arbitrary commands or read logs for any component in the same namespace. Attack vectors include both the network-accessible API endpoints, with low attack complexity and low privilege requirements. The blast radius is limited to the same namespace (not cross-namespace), but encompasses all components within it. Patches are available in versions 1.2.3 and 1.1.6, with the fix properly validating authorization against the component's real owning project instead of the caller-supplied parameter.

Affected products

  • OpenChoreo openchoreo-api >=1.2.0-m.1, <1.2.3; <1.1.6

Identifiers

  • CVE-2026-73841
  • GHSA-52gf-6rpq-fgmx
  • GO-2026-6358

Timeline

  • 2026-07-27: disclosed: Initial advisory publication
  • 2026-08-13: patched: Fixed in versions 1.2.3 and 1.1.6
  • 2026-09-02: advisory: GitHub Advisory Database update

References

This page as Markdown. Free to reuse under CC BY 4.0 with a link back.