Miren Runtime RPC auth bypass: unverified TLS client certs grant cluster superuser access (CVE-2026-75521)
Severity: critical · Patch status: patched · Since 2026-07-08 · CVE-2026-75521
Miren Runtime's RPC server, which listens on QUIC/HTTP3 port 8443 by default, asked clients for TLS certificates but never checked them against the cluster certificate authority. The authorizer also skipped role checks for any certificate identity. Anyone who can reach that port can present a self-signed certificate that copies the cluster CA's subject name and be accepted as a cluster superuser, with full control of entities, apps, sandboxes and disks. Exposure depends only on network reachability of the port. The GitHub advisory rates it critical, and NVD carries a CVSS v4.0 score of 10.0 from GitHub. Version 0.11.1 verifies the client-certificate chain and requires a verified chain before trusting a certificate identity. The vendor cannot detect past unauthorised access, so it recommends redeploying applications, rotating credentials kept in environment variables, and running its read-only audit script. No exploitation is reported in the sources checked.
What to do
- Upgrade miren.dev/runtime to 0.11.1 and restart the RPC server so the new listener TLS configuration takes effect
- Restrict network access to :8443 to trusted management networks and remove any 0.0.0.0/0 ingress immediately (containment if you cannot patch yet)
- Assume possible compromise: run the vendor's read-only audit script to review standing access, recent changes, and identify secrets to rotate
- Redeploy all applications running on the cluster
- Rotate all credentials referenced in environment variables
Fixed versions
Sources
All live incidents on Threat Watch