Summary
The Miren Runtime RPC server requested TLS client certificates but did not verify that they chained to the cluster CA, so a self-signed certificate could authenticate as a superuser. It affects miren.dev/runtime before 0.11.1; the source rates it critical (CVSS 4.0: 10.0).
What happened
The RPC server (QUIC/HTTP3, default port :8443) requested client certificates but did not check that the chain led to the cluster CA. The RPC authenticators took the presented certificate's CommonName as the caller identity without checking that the chain had been verified, and the authorizer allowed everything for certificate-based identities, skipping RBAC checks. According to the source, an attacker can craft a self-signed certificate whose issuer DN matches the cluster CA's, and the vulnerable server accepts it as a superuser. The weakness is classified as CWE-295. Identifiers: CVE-2026-75521 and GHSA-8fh7-7q4q-cq52.
Why it matters
The source describes a complete authentication bypass against the cluster control plane: anyone who can reach the RPC port can perform any RPC operation with full privileges, including enumerating and manipulating entities, apps, sandboxes and disks, with full compromise of confidentiality, integrity and availability. Exposure depends only on network reachability: if :8443 is open beyond a trusted network (for example 0.0.0.0/0), it is remotely exploitable from the internet; if restricted to a trusted network, it is exploitable by any party with access to that network. The score is CVSS 4.0 10.0 (vector CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:H/VA:H/SC:H/SI:H/SA:H, source GHSA). CISA's KEV catalog does not list active exploitation of this vulnerability. According to the vendor, there is no way to detect whether the RPC was accessed without authorization.
Affected products and versions
miren.dev/runtime (Go ecosystem): versions before 0.11.1 (< 0.11.1). Fixed version: 0.11.1.
| Product | Versions | Fixed in |
|---|---|---|
| miren.dev/runtime | < 0.11.1 | 0.11.1 |
| mirendev runtime | < 0.11.1 | — |
Action recommended by the source
The vendor advises upgrading to the fixed version (0.11.1) and restarting the server so the new listener configuration takes effect. The fix makes the listener use tls.VerifyClientCertIfGiven when a CA is configured, so a presented certificate must chain to the CA, and makes both authenticators require a verified chain as defense in depth. As an interim measure, it recommends restricting network access to port :8443, removing any ingress from 0.0.0.0/0 and limiting it to trusted management networks; it describes this as containment. Because unauthorized access cannot be detected, Miren recommends redeploying all applications and rotating any credentials referenced in environment variables. The vendor provides a read-only script to review standing access, recent changes and the secrets to rotate at https://github.com/mirendev/runtime/tree/089582a132f7fc1e1d5b5c0aee1e0911535fed53/scripts/security/audit-exposure. Fixed release: https://github.com/mirendev/runtime/releases/tag/v0.11.1.
Fixed in: 0.11.1
Sources and references
- https://github.com/advisories/GHSA-8fh7-7q4q-cq52 — GHSA
- https://github.com/mirendev/runtime/security/advisories/GHSA-8fh7-7q4q-cq52 — GHSA
- https://nvd.nist.gov/vuln/detail/CVE-2026-75521 — GHSA
- https://github.com/mirendev/runtime/commit/e2159c8c8559da3f1c1485b463c794d656cd2fe4 — GHSA
- https://github.com/mirendev/runtime/releases/tag/v0.11.1 — GHSA
Weaknesses (CWE): CWE-295
Relevant change history
Published
Advisory published.