CVE-2026-75521
### 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 available at https://github.com/mirendev/runtime/tree/089582a132f7fc1e1d5b5c0aee1e0911535fed53/scripts/security/audit-exposure. ### Details Three independent factors combined to produce the bypass: 1. **The listener never verified the client-certificate chain.** When a cluster CA was configured, the RPC listener used `tls.RequestClientCert`, which requests a client certificate but does not verify it against the configured `ClientCAs`. `tls.ConnectionState
Properties
- Severity
- critical
- Summary
- Miren Runtime: Authentication bypass in RPC layer: unverified TLS client certificates grant cluster superuser access
- Nvd fetched at
- 2026-11-19T03:31:17.617109+00:00
- Cvss severity
- CRITICAL
- Cvss score
- 10
- Retrieved at
- 2026-11-19T03:32:39+00:00
- Ghsa published
- 2026-11-19T00:45:46Z
- Source url
- https://github.com/advisories/GHSA-8fh7-7q4q-cq52
- Ghsa updated
- 2026-11-19T00:45:46Z
- Ghsa id
- GHSA-8fh7-7q4q-cq52
- Last source
- GitHub Advisory Database
- Score
- 10
- Cvss version
- 4.0
- Cve id
- CVE-2026-75521
- Cvss 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/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X
- First seen by Signal
- 2026-11-18T19:25:45+00:00
- Name
- CVE-2026-75521
- Is ghsa only
- false
- 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/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X
- Published at
- 2026-11-18T19:18:08.200
Related Entities (3)
AFFECTS (1)
HAS_WEAKNESS (1)
VULNERABLE_TO (1)
Related research
Explore deeper with Ninja Signal's threat intelligence graph