CVE-2026-7163

Cluster admin access via exposed local JWT

Published Apr 30, 2026 · Updated Aug 16, 2026

Authorization flaw in assisted-service in Red Hat multicluster engine for Kubernetes allows remote authenticated users to read kubeadmin credentials. In AUTH_TYPE=local mode, the local authenticator grants full administrative access to any request bearing a valid JWT, and the cluster credentials and kubeconfig download endpoints apply no narrower per-endpoint authorization. On on-premises ACM and MCE hubs, any user who can read an InfraEnv object in a namespace can extract the plaintext JWT from InfraEnvStatus.ISODownloadURL and use it to retrieve kubeadmin passwords and kubeconfigs for arbitrary provisioned spoke clusters.

CVSS severity6.1
Medium
EPSS probability0.19%
Next 30 days · Sep 16, 2026
Known exploitationUnconfirmed
Based on sourced intelligence
Hinoki checkNot available
Coverage for this vulnerability

See if you're affected

Explore vulnerability checks for your environment with Hinoki.

Book a demo

Summary

What happened

Authorization flaw in assisted-service in Red Hat multicluster engine for Kubernetes allows remote authenticated users to read kubeadmin credentials. In AUTH_TYPE=local mode, the local authenticator grants full administrative access to any request bearing a valid JWT, and the cluster credentials and kubeconfig download endpoints apply no narrower per-endpoint authorization. On on-premises ACM and MCE hubs, any user who can read an InfraEnv object in a namespace can extract the plaintext JWT from InfraEnvStatus.ISODownloadURL and use it to retrieve kubeadmin passwords and kubeconfigs for arbitrary provisioned spoke clusters.

The record

CVE
CVE-2026-7163
Published
Apr 30, 2026
Updated
Aug 16, 2026
Vendor
389 Directory Server
Product
multicluster engine for Kubernetes 2.10
Classifications
CWE-312, T1552
Attack vector
adjacent
Privileges
authenticated

Timeline

How it unfolded

  1. Apr 30, 2026CVE publishedPublication date reported by the CVE source.
  2. Aug 16, 2026Record updatedLatest update available in the CVE record.

Exploitability

Present is not the same as exploitable

Compare your product and version with the public record. A matching version still requires validation against your environment.

Is a vulnerable build present?

Affected versions are unavailable in this record. Check the vendor advisory for version and patch details.

What conditions does exploitation require?

Attack vectoradjacent
Required privilegesauthenticated

What is affected?

389 Directory Server · multicluster engine for Kubernetes 2.10Affected versions are unavailable in this record.
389 Directory Server · multicluster engine for Kubernetes 2.7Affected versions are unavailable in this record.
389 Directory Server · multicluster engine for Kubernetes 2.9Affected versions are unavailable in this record.
389 Directory Server · multicluster engine for KubernetesAffected versions are unavailable in this record.

Published CVSS scores

6.1Red HatCVSS:3.1/AV:A/AC:L/PR:L/UI:R/S:C/C:H/I:N/A:N
5.5NVDCVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N

CVSS describes severity. EPSS estimates exploitation probability.

Attacks

What attackers are doing with it

Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.

Daily unique IPsNo honeypot observations are available for this CVE in the selected window.

No observations available

Sep 10, 2026Sep 16, 2026
Latest reporting daySep 16, 2026
Latest daily unique IPsUnavailable
Prior 30-day averageUnavailable
SourceShadowserver honeypots (KEV)
Vectoradjacent
Privilegesauthenticated
Known exploitationUnconfirmed
Public exploitUnconfirmed

Weakness, pattern, technique

CWE-312Cleartext Storage of Sensitive Information
T1552Unsecured Credentials

Public exploit references

No public exploit references are available in this record.

Labels summarize the accepted research assessment. They do not indicate a test against your environment.

Technologies

Your stack

See the directory against your own environment.

Your stack

Check the software in your environment

Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.

Book a demo