CVE
Runtime authentication bypass in RPC layer via forged client certs
Affects Miren Runtime clusters with a cluster CA configured, where the RPC listener requests client certificates without verifying them. Fixed in 0.11.1.
- Exploited
- No known exploitation
- Fix
- Fixed in 0.11.1
- Who is exposed
- Not reported
Do first: Upgrade to a fixed version: 0.11.1.
Summary
Miren Runtime, the runtime component of the Miren application platform, has an authentication bypass in its QUIC/HTTP3 RPC server on the default port 8443. A remote attacker who can reach that listener, without logging in, can present a forged client certificate and gain cluster superuser access, which allows them to view, change, or disrupt applications, sandboxes, disks, credentials, and other managed resources.
Original 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.
Who should check
Anyone running mirendev runtime before 0.11.1 with a cluster CA configured, including deployments that expose RPC port 8443 beyond a trusted network.
Not fixed by: Upgrading without restarting the server does not apply the fix.
“The Miren Runtime RPC server (QUIC/HTTP3, default port :8443 ) requested TLS”
cve.now Index
- Exploitation?/40Unknown. No CISA SSVC exploitation rating yet
- Exposure17/25No login or user action needed, reachable over the network without a login · Unknown: Advisories don't say whether default setups are affected
- Reach?/20Unknown. No tracked technology or package matched
- Severity10/10CVSS 10.0
- No patch0/5No signal
What would change the score
- Would score about 72 if added to CISA KEV
- Would score about 67 if CISA's SSVC rates exploitation active
- Would score about 32 if advisories confirm default setups are exposed
What to do
Upgrade to a fixed version: 0.11.1.
Workaround: Restrict network access to the RPC port 8443 so it is not reachable from untrusted networks, removing any 0.0.0.0/0 ingress.
Check your systems with an agent
Paste this into a coding or ops agent. It checks your systems read-only and reports a table per asset.
Check whether my systems are affected by CVE-2026-75521 (Miren Runtime: Authentication bypass in RPC layer: unverified TLS client certificates grant cluster superuser access), using the cve.now data below.
Rules: work read-only. Do not run exploit code, proof-of-concept scripts or scanners that send attack payloads, and do not change any configuration, package, image or deployment. Report findings only.
What cve.now has for CVE-2026-75521 (entry last updated 2026-11-18):
Affected:
- mirendev runtime: fixed in 0.11.1
Fixed versions: 0.11.1.
Conditions (all must be true for the bug to be hit):
- A cluster CA is configured, so the RPC listener requests client certificates. (source: https://github.com/mirendev/runtime/security/advisories/GHSA-8fh7-7q4q-cq52)
Setup: unknown whether the bug needs a non-default feature or setting. Check the advisory.
Attacker needs: network access, no login, no user action.
Workaround: Restrict network access to the RPC port 8443 so it is not reachable from untrusted networks, removing any 0.0.0.0/0 ingress. (source: https://github.com/mirendev/runtime/releases/tag/v0.11.1)
CISA KEV: CVE-2026-75521 is not listed as of cve.now's last read.
This KEV status is for CVE-2026-75521 only. If you also check another CVE, look up its own KEV status; never assume it from this one.
How to check:
- Installed software: check what is actually running, not what a repo declares. Read the version from each host, container image and Kubernetes node (the binary's version output, the OS package database, image layers), and check whether the conditions above hold there. Distribution packages may carry a backported fix under an older version number; confirm against the distribution's own advisory.
Verify against the linked advisories before concluding, and cite the date you read each one:
- https://github.com/mirendev/runtime/security/advisories/GHSA-8fh7-7q4q-cq52
- https://github.com/mirendev/runtime/commit/e2159c8c8559da3f1c1485b463c794d656cd2fe4
- https://github.com/mirendev/runtime/releases/tag/v0.11.1
Do not conclude an asset is unaffected unless you checked it and the evidence covers both its version and the conditions above. If you could not check something, mark it unknown and say what is missing.
Report a table with one row per asset and these columns: Asset | Version or build | Status (affected, fixed, not applicable, unknown) | Compensating controls | Exposure (internet-facing, internal, none) | Evidence | Next action.
Entry: https://cve.now/CVE-2026-75521
For follow-up questions, use the cve.now MCP server at https://mcp.cve.now/mcp (no authentication), for example execute with name cve.get and arguments {"id": "CVE-2026-75521"}.Timeline
- CVE published
- First seen by cve.now
- Posted on X by cve.now
Affected versions
- mirendev runtime
fixed in 0.11.1
Evidence 5
| Kind | Source |
|---|---|
| Vendor advisory 1Establishes: Affected and fixed versions. | |
| Advisory | GitHub · mirendev/runtime · Advisory GHSA-8fh7-7q4q-cq52 |
| CVE record 2Establishes: The identifier and description. | |
| Record | CVE List · CVE-2026-75521 |
| Record | NVD · CVE-2026-75521 |
| Other links 2 | |
| Repository | GitHub · mirendev/runtime · Commit e2159c8c |
| Repository | GitHub · mirendev/runtime · Release v0.11.1 |
Corrections
None so far.
Something wrong on this page? Report an error. Every fix is listed here.
Questions about CVE-2026-75521
Is CVE-2026-75521 being exploited?
It is not in CISA's Known Exploited Vulnerabilities catalog, and CISA's SSVC assessment does not mark exploitation as active. That does not mean it has not been attacked: vendors and researchers can report attacks before CISA lists them. No public exploit code is tracked.Source: cve.now feed data
What does this mean?
The RPC layer accepts TLS client certificates without verifying them, so a client that can reach the RPC port gains full cluster superuser access. That access covers reading or changing apps, sandboxes, disks, credentials and other cluster resources.Source: github.com, github.com
Which versions are affected by CVE-2026-75521?
runtime: before 0.11.1.Source: cve.now feed data
Am I affected, and how do I check?
The issue involves Miren Runtime versions before 0.11.1 in clusters where a cluster CA is configured, so the RPC listener requests client certificates. Check the installed runtime version and whether a cluster CA is set up on the RPC listener.Source: github.com, github.com
How do I fix CVE-2026-75521?
Upgrade Miren Runtime to 0.11.1, the fixed version named in the release notes.Source: github.com, github.com