Skip to content
Patch Next
Sign inAdd to your agent

← Actionable
Critical, CVSS 9.6amended

OpenChoreo: Unauthenticated access to data-plane operations via OpenChoreo cluster-gateway management APIs

CVE-2026-73843GHSA-qh9r-j7rp-4x2m

What to do

Vendor fix available. Upgrade each affected package to the fixed version on its release line (github.com/openchoreo/openchoreo 1.1.2, 1.0.2), redeploy, then verify what is actually installed.

This page has no inventory attached, so it cannot say whether you are affected. A vendor fix is not proof that your deployment is fixed.

Add to your agent

Affected packages

Sources

Severity and exploitation
Exploitation
No confirmed exploitation recorded. Patch Next marks exploitation only from CISA KEV.
CVSS
9.6 · CVSS:3.1/AV:A/AC:L/PR:N/UI:N/S:C/C:H/I:H/A:H
EPSS
  • CVE-2026-73843: 0.48% estimated exploitation activity in the next 30 days; percentile 41.62 (FIRST EPSS, 2026-11-03). This is a model estimate, not proof of exploitation or customer exposure.
Source description

As published by the source; long descriptions are shortened.

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…

Dates and revisions
Published by the source
Last modified by the source
Source last checked
  1. Revision 3 · amended ·

    Amended from ghsa record GHSA-qh9r-j7rp-4x2m

  2. Revision 2 · amended ·

    Amended from osv record GO-2026-6362

  3. Revision 1 · created ·

    Published from osv record GHSA-qh9r-j7rp-4x2m

Agent brief

Preview the exact text before you copy it. Commands are read-only suggestions; review them before running anything.

# Patch Next advisory brief: CVE-2026-73843

Advisory: OpenChoreo: Unauthenticated access to data-plane operations via OpenChoreo cluster-gateway management APIs
IDs: CVE-2026-73843, GHSA-qh9r-j7rp-4x2m
Record: https://patchnext.com/advisories/cve-2026-73843 (revision 3, source checked 26 Oct 2026, 15:29 UTC)
Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected.
Severity: Critical (CVSS 9.6)
Exploitation: no confirmed exploitation recorded. Patch Next confirms exploitation only from CISA KEV.
Vendor response: Vendor fix available; fixed versions by package: github.com/openchoreo/openchoreo 1.1.2, 1.0.2. A vendor fix does not mean a deployment is fixed.

## Affected components
- Go github.com/openchoreo/openchoreo: affected < 1.0.2; >= 1.1.0, < 1.1.2; fixed in 1.1.2, 1.0.2

## Suggested inspection (read-only)
- Go github.com/openchoreo/openchoreo: check the installed version with your package manager.

## Supported action
Upgrade each affected component to a fixed version on its release line. For a transitive dependency, upgrade the parent package or add an override or constraint, then regenerate the lockfile. Redeploy every environment that ran an affected version.

## Required regression checks
- Run the test suite and a production build.
- Exercise the features that depend on github.com/openchoreo/openchoreo.
- Repeat the inspection and confirm that only fixed versions remain installed.

## Rollback considerations
- Keep the previous lockfile and deployment artifact. Rolling back reinstates the vulnerable version, so apply any documented mitigation while you fix forward.

## Unresolved questions
- Which deployments run an affected version?
- Exploitation status can change. Check again before lowering the priority.
- Mark the work resolved only after the fixed version is verified in production.

## Sources
- Verified: https://osv.dev/vulnerability/GHSA-qh9r-j7rp-4x2m (OSV record GHSA-qh9r-j7rp-4x2m lists affected ranges: Go github.com/openchoreo/openchoreo >=0 =1.1.0 <1.1.2 (fixed))
- Verified: https://osv.dev/vulnerability/GO-2026-6362 (OSV record GO-2026-6362 lists affected ranges: Go github.com/openchoreo/openchoreo >=0 =1.1.0 <1.1.2 (fixed))
- Verified: https://github.com/advisories/GHSA-qh9r-j7rp-4x2m (GitHub-reviewed advisory GHSA-qh9r-j7rp-4x2m lists affected ranges: Go github.com/openchoreo/openchoreo >=0 =1.1.0 <1.1.2)

Commands are suggestions: review each one before running it.

Loading voting…