miren.dev/runtime · Miren Runtime: Authentication bypass
Affects miren.dev/runtimeSource GCVE Database
Not known to be exploited · CVSS 10.0 Critical : upgrade to 0.11.1 as a priority.
Data as of 19 Nov 2026, 01:50 UTC
Thin evidence
One scorer or none| CNA (GitHub_M) | CVSS 4.0 | 10.0 |
|---|
- Patch
- Available – fixed in 0.11.1
CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:H/VA:H/SC:H/SI:H/SA:HExploitation evidence
Disclosed: evidence found.
CVE published 18 Nov 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponized: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors
A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 18 Nov 2026.
What to do
Upgrade miren.dev/runtime to 0.11.1.
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| Gomiren.dev/runtime | Affected
| Fixed in
|
Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.
AI-suggested
A patch is available in Miren Runtime version 0.11.1 that fixes the vulnerability by verifying client certificate chains before trusting them. Users should upgrade to version 0.11.1 or later and restart the server to apply the fix. Until the patch is deployed, restrict network access to the RPC port (:8443) to trusted management networks only, removing any 0.0.0.0/0 ingress rules. This network restriction is a containment measure and does not fix the underlying vulnerability. Additionally, Miren recommends redeploying all applications and rotating any credentials referenced in environment variables due to the inability to detect unauthorized RPC access. A read-only audit script is available to assist with reviewing access and secrets rotation.
Description
Miren Runtime versions prior to 0.11.1 contain a critical authentication bypass vulnerability in the RPC server's TLS client certificate verification. The server requests client certificates but fails to verify that they chain to the cluster's Certificate Authority. This flaw allows an attacker who can reach the RPC port (default :8443) to present a forged, self-signed certificate with a matching issuer Distinguished Name and gain cluster superuser access without valid credentials. The vulnerability enables full control over the cluster, including manipulation of entities, applications, and resources. A patch is available in version 0.11.1 that enforces proper client certificate chain verification. Until patched, restricting network access to the RPC port to trusted networks is recommended.
References
- github.com/mirendev/runtime/security/advisories/GHSA-8fh7-7q4q-cq52 (opens in a new tab)
- nvd.nist.gov/vuln/detail/CVE-2026-75521 (opens in a new tab)
- github.com/mirendev/runtime/commit/e2159c8c8559da3f1c1485b463c794d656cd2fe4 (opens in a new tab)
- github.com/mirendev/runtime (opens in a new tab)
- github.com/mirendev/runtime/releases/tag/v0.11.1 (opens in a new tab)