Miren Runtime RPC Auth Bypass: Forged TLS Client Certs Grant Cluster Superuser Access (CVE-2026-75521)
What happened
Miren disclosed a critical authentication bypass (GHSA-8fh7-7q4q-cq52 / CVE-2026-75521) in the Miren Runtime RPC server, which listens over QUIC/HTTP3 on :8443 by default. According to the advisory, the server requested TLS client certificates but never verified that a presented certificate actually chained to the cluster's Certificate Authority.
Three factors combined to produce the bypass. The listener used tls.RequestClientCert instead of verifying the chain. The RPC authenticator read the unverified certificate's CommonName as the caller identity. The authorizer granted a blanket RBAC bypass to any certificate-based identity. Go's TLS client only checks that an issuer Distinguished Name matches a publicly known, non-secret value. As a result, an attacker could mint a self-signed certificate with a byte-identical issuer DN and be authenticated as a cluster superuser. No valid CA signature or prior credential was needed.
Why it matters for defenders
Any network party able to reach the RPC port can obtain full, unauthenticated superuser access to the cluster. Per the advisory, exposure is gated purely by network reachability. Deployments exposing :8443 to 0.0.0.0/0 are remotely exploitable from the internet, and deployments restricted to an internal network are exploitable by anyone on that network. A superuser RPC session can enumerate and manipulate entities, apps, sandboxes, disks, and other orchestrated resources. This amounts to full compromise of confidentiality, integrity, and availability for everything the cluster runs.
Miren also states there is currently no reliable way to detect whether the RPC interface was accessed by an unauthorized party in the past. This raises the bar for incident response on any previously exposed cluster.
What defenders should do now
- Patch and restart: upgrade to the fixed Miren Runtime release, which switches the listener to
tls.VerifyClientCertIfGivenand requires both RPC authenticators to see a non-emptyVerifiedChainsbefore trusting a certificate-derived identity. A restart is required for the new listener configuration to take effect. - Contain exposure if you cannot patch yet: restrict network access to
:8443to trusted management networks only, and remove any broad or internet-facing ingress. The advisory states this is containment only and does not fix the underlying flaw. - Assume compromise and rotate: because unauthorized RPC access may be undetectable after the fact, Miren recommends redeploying applications and rotating any credentials referenced in environment variables.
- Use Miren's audit tooling: Miren has published a read-only script to help review standing access, recent changes, and the exact secrets to rotate. Run it against any cluster that may have had
:8443reachable from an untrusted network. - Hunting angle: review RPC and control-plane logs for client-certificate authentications with unexpected or unfamiliar
CommonNamevalues, and audit recent privileged RPC operations (entity, app, sandbox, and disk changes) for activity that does not correlate with known operator actions.
Developing intel
This is a same-day critical advisory and details may evolve as Miren and the community assess real-world exposure. Treat this writeup as a summary of the published advisory, not independent confirmation of exploitation in the wild. Exploit status is currently listed as theoretical. For full technical details, patch guidance, and the audit script, see the original GHSA advisory.