Threat Feed

CVE-2026-75521: mirendev runtime · Authentication bypass

Exploitation: None known · CVSS 10.0 Critical · Unauthenticated · Published 2026-11-18

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.

Enclave's analysis

Miren Runtime's RPC control-plane port (QUIC/HTTP3, default 8443) accepts any self-signed TLS client certificate whose issuer name matches the cluster CA's public subject string, without ever checking the certificate actually chains to that CA. The server then treats the certificate's CommonName as an authenticated identity and skips all RBAC checks, handing the connecting party cluster superuser rights. No credentials, prior session, or user interaction are needed — just network reach to the port, which the vendor's own setup docs tell operators to open to the internet for normal CLI/dashboard use. Patch to 0.11.1; the vendor also recommends rotating all exposed credentials and redeploying apps since pre-patch access can't be audited after the fact.

Fix

Upgrade mirendev/runtime to 0.11.1. No fixed version is listed for runtime; follow the vendor advisory.

Affected versions

ProductVulnerableFixed in
runtime< 0.11.1Not listed
mirendev/runtime< 0.11.10.11.1

Seen in 2 sources