- Severity: CRITICAL
- CVE: CVE-2026-75521
- Ecosystems: go
- Packages: miren.dev/runtime
### Summary
The Miren Runtime RPC server (QUIC/HTTP3, default port `:8443`) requested TLS
client certificates but never verified that a presented certificate chained to
the cluster Certificate Authority. Because a client-certificate identity is
granted a blanket RBAC bypass, any party able to reach the RPC listener could
present a forged, self-signed certificate and be authenticated as a cluster
**superuser** — no valid CA signature, credential, or prior authorization
required.
### Impact
This is a complete, unauthenticated authentication bypass against the cluster
control plane. An attacker who can reach the RPC port can perform any RPC
operation with full privileges: enumerate and manipulate entities, apps,
sandboxes, disks, and other cluster resources. This yields full compromise of
confidentiality, integrity, and availability of the cluster and everything it
orchestrates.
Exposure is network-reachability–gated only. Deployments that expose `:8443`
beyond a trusted network (e.g. `0.0.0.0/0`) are remotely exploitable from the
internet by anyone; deployments that restrict `:8443` to a trusted network are
exploitable by any party with access to that network.
Due to a lack of ability to detect if the RPC has been accessed unauthorized,
Miren recommends that all applications are redeployed and any credentials reference
in environment variables are rotated. A read-only script to help review standing access,
recent changes, and the exact secrets to rotate is…
Source: GitHub Security Advisories · 2026-11-19