# CVE-2026-73842: OpenChoreo: cluster-gateway internal proxy performs no caller authentication and is not read-only — data-plane Secret disclosure and arbitrary Kubernetes mutation

> Unauthenticated access to internal proxy endpoints allows attackers to read Kubernetes Secrets and execute arbitrary commands across data planes.

- **Severity:** Critical 9.0 (`CVSS:3.1/AV:A/AC:L/PR:L/UI:N/S:C/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 13 Aug 2026
- **Updated:** 18 Aug 2026
- **Also known as:** GHSA-rh53-xvx2-j327, GO-2026-6428

## What is CVE-2026-73842?

CVE-2026-73842 is a critical missing authorization vulnerability in openchoreo, published on 13 Aug 2026. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

OpenChoreo is a complete, open-source developer platform for Kubernetes. Prior to 1.0.3, 1.1.3, and 1.2.0-rc.2, internal/cluster-gateway/server.go exposed /api/proxy/, /api/exec/, and /api/wirelogs/ on an internal listener without requiring a client certificate or token, allowing any network-reachable caller to read tenant Kubernetes Secrets, mutate workloads, and execute commands across connected data planes. This issue is fixed in versions 1.0.3, 1.1.3, and 1.2.0-rc.2.

Weakness: CWE-862 (Missing Authorization), CWE-306 (Missing Authentication for Critical Functionality), CWE-269 (Improper Privilege Management)

## Which versions are affected by CVE-2026-73842?

7 open source packages ship an affected version, including github.com/openchoreo/openchoreo.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `github.com/openchoreo/openchoreo` | Go | All versions | 1.0.3, 1.1.3, 1.2.0 |
| `github.com/openchoreo/openchoreo` | Go | All versions | 1.0.3 |
| `github.com/openchoreo/openchoreo` | Go | All versions | 1.0.3 |
| `github.com/openchoreo/openchoreo` | Go | From 1.1.0 | 1.1.3 |
| `github.com/openchoreo/openchoreo` | Go | From 1.1.0 | 1.1.3 |
| `github.com/openchoreo/openchoreo` | Go | From 1.2.0-rc.1 | 1.2.0 |
| `github.com/openchoreo/openchoreo` | Go | From 1.2.0-rc.1 | 1.2.0 |

## How do I fix CVE-2026-73842?

Upgrade github.com/openchoreo/openchoreo to a fixed version for your release line: 1.0.3, 1.1.3 or 1.2.0.

## Is CVE-2026-73842 being exploited?

There is no known exploitation of CVE-2026-73842 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-73842 and fix it if it is affected.

What it is: CVE-2026-73842 is a critical missing authorization vulnerability in openchoreo, published on 13 Aug 2026. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-73842 in the wild and no public exploit code.

Affected packages and fixed versions:
- github.com/openchoreo/openchoreo (Go): affected all versions; fixed in 1.0.3, 1.1.3, 1.2.0
- github.com/openchoreo/openchoreo (Go): affected all versions; fixed in 1.0.3
- github.com/openchoreo/openchoreo (Go): affected all versions; fixed in 1.0.3
- github.com/openchoreo/openchoreo (Go): affected from 1.1.0; fixed in 1.1.3
- github.com/openchoreo/openchoreo (Go): affected from 1.1.0; fixed in 1.1.3
- github.com/openchoreo/openchoreo (Go): affected from 1.2.0-rc.1; fixed in 1.2.0
- github.com/openchoreo/openchoreo (Go): affected from 1.2.0-rc.1; fixed in 1.2.0

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-73842/ (Markdown: https://insights.sbomify.com/CVE-2026-73842/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-73842
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-73842
- OSV: https://osv.dev/vulnerability/CVE-2026-73842

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-73842/
Summaries are generated and may contain mistakes; the official description above is the record.