Runtime
Miren Runtime: Authentication bypass in RPC layer: unverified TLS client certificates grant cluster superuser access
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.
Affected versions and mitigation
From the CVE record and the vendor's references.Affected
- < 0.11.1
Fixed in 0.11.1
Mitigation
Upgrade runtime to 0.11.1 or later.
References
- Vendor advisory github.com/mirendev/runtime/security/advisorie…
- Patch github.com/mirendev/runtime/commit/e2159c8c855…
- Release notes github.com/mirendev/runtime/releases/tag/v0.11…
Timeline
Days relative to CVE publicationFirst public PoC 9 h after publication; not in CISA KEV. First PoC: LLCForge/CVE-2026-75521 (created 19 Nov 2026, found by us: 19 Nov 2026).
PoC repositories
Found on GitHub.1 PoCs
PoCs 1
| Repository | Created | Found by us | Stars | Assessment |
|---|---|---|---|---|
| LLCForge/CVE-2026-75521 | 19 Nov 2026 +9 h | 19 Nov 2026 | 0 | PoC
Flags · score 15
Below the suspicion threshold (50); does not change the assessment. |
Only PoCs count toward the first-PoC date and the characteristics below. Do not run PoC code from unknown sources.