mirendev · runtime · CWE-295 · published 2026-11-18
CVE-2026-75521Miren Runtime: Authentication bypass in RPC layer: unverified TLS client certificates grant cluster superuser access
Routine No exploitation evidence; EPSS 0.3%.
CVE-2026-75521 is not known to be exploited in the wild. EPSS estimates a 0.3% chance of exploitation in the next 30 days, higher than 21% of all CVEs. This runtime vulnerability: CVSS 10.0 (v4.0). Routine: patch when convenient.
Jump to: Remediation Exploit intelAffected versionsDescription
Remediation#
No fixed version is recorded here yet. Check the vendor advisory linked from the CVE record below.
Exploit intelligence#
| Signal | Value | Source |
|---|---|---|
| Known exploited | No | CISA KEV |
| Ransomware use | — | CISA KEV |
| EPSS (30-day exploitation probability) | 0.3% (22th pct) | FIRST EPSS v2026.06.15 |
| CVSS base score | 10.0 (v4.0)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 | CNA / CISA ADP |
| SSVC exploitation | — | CISA Vulnrichment |
| SSVC automatable | — | CISA Vulnrichment |
| SSVC technical impact | — | CISA Vulnrichment |
Weakness: CWE-295: Improper Certificate Validation
Affected versions (from the CVE record)#
- mirendev runtime
< 0.11.1(affected)
Description (from the CVE record)#
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.
Quoted from the CVE Program record.