CVE-2026-75521

waiting for further signalsZero needs more public information before it can validate it.

GHSA-8fh7-7q4q-cq52 ↗EUVD-2026-129146 ↗

no check availablenot proven exploitable
cve.orgpublic pocExploit code has been published by someone. Source signals can also carry a PoC (Proof of Concept).kevAttacks confirmed in the real world.
go:miren.dev/runtime < 0.11.1
fixed in 0.11.1
ETK-2026-4867Zero's internal tracking ID, independent of the CVE number., permanent identifier
pkg:golang/miren.dev/runtime
47msince last run
52mAI analysisAnalysis: how long the AI spent reversing this signal.
timeline
0 = cve.org publication
trigger signal (cve.org) +0hwaiting for further signals+7h13m
0
+2h
+4h
+6h
+8h
+10h
+12h

description

Miren Runtime releases before 0.11.1 can trust client certificate identities without confirming that the certificate is issued by the configured cluster CA. An attacker able to connect to the RPC listener can obtain cluster-wide privileged access and alter or view managed resources.

mitigation

Upgrade miren.dev/runtime to version 0.11.1 or later and restart the RPC server. Until upgraded, limit access to port 8443 to trusted management networks.

fixed in 0.11.1

check
no
exploit
no
automationDeterministic: a check that runs on its own, the same request on every target. Contextual: an agentic technique that needs to be applied per target, for bugs that depend on contextual flows.
–
auth requiredWhether an attacker needs an account first, based on the CVSS vector's Privileges Required.
no
EPSSEstimate of the chance this CVE is exploited in the next 30 days. Refreshed daily.
–
agent run time
52m
cve.org record, t = 0The moment cve.org publishes the CVE in full.
2026-11-18 18:51Z
Δ to public pocExploit code has been published by someone. Source signals can also carry a PoC (Proof of Concept).
–
Δ to kevAttacks confirmed in the real world.
–

outcome

No artifact: an exploit or check was attempted but could not be produced at this moment.

source signals

Public signals that triggered or updated the pipeline. These are inputs for the deltas above.

  1. 2026-11-18 18:51Z
    ghsa: trigger signal, started the run
  2. 2026-11-18 18:51Z

this entry in the feed

GET /api/v1/feed/CVE-2026-75521

{
  "etk_id": "ETK-2026-4867",
  "cve_id": "CVE-2026-75521",
  "display_id": "CVE-2026-75521",
  "ghsa_id": "GHSA-8fh7-7q4q-cq52",
  "euvd_id": "EUVD-2026-129146",
  "status": "published",
  "anchor_state": "anchored",
  "title": "Miren Runtime RPC client-certificate authentication bypass",
  "summary": "Miren Runtime releases before 0.11.1 can trust client certificate identities without confirming that the certificate is issued by the configured cluster CA. An attacker able to connect to the RPC listener can obtain cluster-wide privileged access and alter or view managed resources.",
  "mitigation": "Upgrade miren.dev/runtime to version 0.11.1 or later and restart the RPC server. Until upgraded, limit access to port 8443 to trusted management networks.",
  "vendor": "go",
  "product": "go:miren.dev/runtime",
  "affected": [
    {
      "affected_notes": [],
      "affected_ranges": [
        "< 0.11.1"
      ],
      "ecosystem": "go",
      "fixed_versions": [
        "0.11.1"
      ],
      "package_name": "miren.dev/runtime",
      "purl": "pkg:golang/miren.dev/runtime"
    }
  ],
  "cwes": null,
  "cvss_score": 10,
  "cvss_src": "cna_vendor",
  "cvss_vector": "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",
  "epss_score": null,
  "epss_percentile": null,
  "epss_asof": null,
  "automation": "deterministic",
  "check": false,
  "check_confidence_basis": null,
  "exploit": false,
  "pipeline_minutes": 51.882827416666665,
  "t0_at": "2026-11-18T18:51:17.521000+00:00",
  "signals": {
    "trigger_signal": {
      "at": "2026-11-18T18:51:17.521000+00:00",
      "days": 0,
      "is_lower_bound": false,
      "measured_at": "2026-11-18T18:51:17.521000+00:00",
      "url": "https://github.com/advisories/GHSA-8fh7-7q4q-cq52"
    }
  }
}

published 2026-11-19 01:12Z
last change 2026-11-19 02:14Z

Need the technical details behind an entry?

Every entry here shows what we attempted and when. The technical details, the generated exploit that fired it and the evidence behind the verdict are not public. Tell us about your use case and we’ll get back to you about extended API access.