CVE-2026-75521
Miren Runtime: Authentication bypass in RPC layer: unverified TLS client certificates grant cluster superuser access
Description
Miren Runtime provides the runtime component for the Miren application platform. Prior to 0.11.1, the QUIC/HTTP3 RPC server on the default port 8443 uses tls.RequestClientCert and does not verify that presented certificates chain to the configured cluster certificate authority. The RPC authenticators derive a caller identity from PeerCertificates[0].Subject.CommonName without requiring a non-empty VerifiedChains value, and certificate identities bypass all RBAC checks. A network attacker who can reach the listener can present a self-signed certificate with an issuer distinguished name matching the public cluster CA subject and gain cluster superuser access, allowing disclosure, modification, or disruption of applications, sandboxes, disks, credentials, and other managed resources. This issue is fixed in version 0.11.1.
INFO
Published Date :
Nov. 18, 2026, 6:51 p.m.
Last Modified :
Nov. 18, 2026, 6:51 p.m.
Remotely Exploit :
No
Source :
GitHub_M
Solution
- Update Miren Runtime to version 0.11.1.
- Verify certificate verification is enforced.
We scan GitHub repositories to detect new proof-of-concept exploits. Following list is a collection of public exploits and proof-of-concepts, which have been published on GitHub (sorted by the most recently updated).
Results are limited to the first 15 repositories due to potential performance issues.
The following list is the news that have been mention
CVE-2026-75521 vulnerability anywhere in the article.