Skip to main content
VulnerabilityPublished

CVE-2026-75521: mirendev runtime · Improper Certificate Validation

Affects mirendev runtimeSource CVE Database V5

0
Compare

Not known to be exploited · CVSS 10.0 Critical : upgrade to 0.11.1 as a priority.

Data as of 18 Nov 2026, 19:06 UTC

CVSS 4.0 base score
10.0Critical
How severe the flaw is on the 0–10 CVSS scale.

Thin evidence

One scorer or none
CVSS scores by source
CNA (GitHub_M)CVSS 4.010.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:H

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 18 Nov 2026

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponized: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq 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 17 Nov 2026.

What to do

Upgrade mirendev runtime to 0.11.1.

Affected software

ProductAffectedFixed in
mirendevruntimeAffected
  • <0.11.1
Fixed in
  • 0.11.1

AI-suggested

Upgrade Miren Runtime to version 0.11.1 or later, where the improper certificate validation issue is fixed. No other mitigations are indicated by the vendor advisory.

Description

Miren Runtime versions prior to 0.11.1 contain an improper certificate validation vulnerability in the QUIC/HTTP3 RPC server. The server accepts client certificates without verifying that they chain to the configured cluster certificate authority, allowing an attacker to present a self-signed certificate with a matching issuer distinguished name. This flaw enables the attacker to bypass RBAC checks and gain cluster superuser access, risking disclosure, modification, or disruption of managed resources. The issue is fixed in version 0.11.1.

References

Community reviews

Loading reviews…