← Back to results
Vulnerability record · public intelligence
CVE-2026-66795
CRITICAL

Managedcluster-import-controller: csr auto-approver does not validate certificate subject or signername (spoke→hub cluster-admin)

Published Aug 17, 2026 · Updated Nov 3, 2026

Severity · CVSSCRITICAL · Not scored
Known exploitationNot listed
EPSS / likelihood0.49%
QFinch risk scoreNot available

Original summary

Normalized public record · Updated Nov 3, 2026

Managedcluster-import-controller: csr auto-approver does not validate certificate subject or signername (spoke→hub cluster-admin)

Publisher and source text is retained separately from QFinch interpretation.

QFinch assessment

A flaw was found in the managedcluster-import-controller. The Certificate Signing Request (CSR) auto-approval logic improperly validates incoming CSRs, specifically by not inspecting the signer name or decoding the PEM-encoded x509 CSR. This vulnerability allows a privileged service account on a spoke cluster to submit a malicious CSR. Successful exploitation can lead to privilege escalation, enabling the attacker to obtain administrative credentials on the hub cluster.

Evidence: public source records

Affected products

Affected scope reported by the available public evidence
Affected package, product or rangeFix status
Consult the referenced vendor advisory for affected versions.Consult source advisory

Matching a version is only one part of assessing exposure. QFinch has not assessed your environment on this public page.

Remediation

Apply the vendor-supported fixed release or mitigation, then verify the affected component is no longer reachable.

  1. Confirm the affected product and reachable code path exist in your environment.
  2. Apply the vendor-supported patch or mitigation from the primary advisory.
  3. Rescan the exact deployed revision and retain verification evidence.
Review primary references

Evidence coverage

FIRST-EPSSCVE-LIST-V5
SSVC priority
MEDIUM
Confidence
Not available
Aliases
None reported

Scores appear only when corresponding evidence exists. Missing data is never interpreted as zero risk.

Sources and record history

  1. RHSA-2026:59556 ↗
  2. RHSA-2026:59557 ↗
  3. RHSA-2026:59558 ↗
  4. RHSA-2026:59559 ↗
  5. RHSA-2026:59579 ↗
  6. RHSA-2026:59593 ↗
  7. access.redhat.com ↗
  8. RHBZ#2507540 ↗

Record history

Published Aug 17, 2026 · Last refreshed Nov 3, 2026

Related intelligence
Browse all vulnerabilities →
CVE-2026-11165CRITICAL

CVE-2026-11165

Related through FIRST-EPSS and CVE-LIST-V5 evidence

Use after free in WebMIDI in Google Chrome on iOS prior to 149.0.7827.53 allowed a remote attacker to potentially perform a sandbox escape via a crafted HTML page. (Chromium security severity: Medium)

CVE-2026-11009CRITICAL

CVE-2026-11009

Related through FIRST-EPSS and CVE-LIST-V5 evidence

Use after free in USB in Google Chrome on Windows prior to 149.0.7827.53 allowed a remote attacker to potentially perform a sandbox escape via a crafted HTML page. (Chromium security severity: Medium)

CVE-2026-110130CRITICAL

Dockhand before 1.0.45 Authentication Bypass via Static-Asset Check

Related through FIRST-EPSS and CVE-LIST-V5 evidence

Dockhand before 1.0.45 Authentication Bypass via Static-Asset Check

CVE-2026-11047CRITICAL

CVE-2026-11047

Related through FIRST-EPSS and CVE-LIST-V5 evidence

Inappropriate implementation in Base in Google Chrome on Windows prior to 149.0.7827.53 allowed a remote attacker who had compromised the renderer process to potentially perform a sandbox escape via a crafted HTML page. (Chromium security severity: Medium)