EM-20261119-KX6N
VulnerabilityCritical severity
Critical Miren Runtime Vulnerability (CVE-2026-75521)
CVE-2026-75521
Status
Developing
Since : signals keep joining.
- First Signal
- Nov 18 19:18 UTCC6 NVD CVE API 2.0
- Page Born
- Nov 19 00:45 UTCsecond source joined
- Last Signal
- Nov 19 00:45 UTC30 hours before snapshot
- Sources
- 20 official · 2 research, news or crowd
- Open For
- 8 hoursso far
Life Of This Page
- 1BornA second, independent source names it.
- 2Developing · NowNew signals join; severity can move.
- 3ConfirmedNot yetCISA KEV lists it, or exploitation in the wild is reported.
- 4ResolvedNot yetPast the fix deadline and 14 days with no new signal.
- 5ArchivedNot yet30 days after resolved. Read only; the link keeps working. Reopens if it comes back.
The ID never changes, and earlier addresses keep working. A correction is logged, never overwritten. If two pages turn out to be one incident, the later one points to the earlier.
Vulnerability Lifecycle
- Disclosed: reachedNov 18 19:18 UTCC6 NVD published
- Scored: reachedNov 18 19:18 UTCCVSS 10
- Exploited: not yetNot yetNo exploitation reported
- Advisories: not yetNot yetNone yet
- Vendor Response: not yetNot yetNone in sources yet
- Resolved: not yetNot yetAfter 14 quiet days
Timeline
Point at a mark to read it. Squares are signals, colored by severity; every one is also listed under Signals.
Signals
- GHSA-8fh7-7q4q-cq52 / CVE-2026-75521: Miren Runtime: Authentication bypass in RPC layer: unverified TLS client certificates grant cluster superuser access (opens source in a new tab) go:miren.dev/runtime Crit severityDatabaseC26 GitHub Advisory Database
- CVE-2026-75521 (CVSS 10) (opens source in a new tab) 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… Crit severityDatabaseC6 NVD CVE API 2.0