Headline
GHSA-5qjg-9mjh-4r92: Karmada Dashboard API Unauthorized Access Vulnerability
Impact
This is an authentication bypass vulnerability in the Karmada Dashboard API. The backend API endpoints (e.g., /api/v1/secret, /api/v1/service) did not enforce authentication, allowing unauthenticated users to access sensitive cluster information such as Secrets and Services directly. Although the web UI required a valid JWT for access, the API itself remained exposed to direct requests without any authentication checks. Any user or entity with network access to the Karmada Dashboard service could exploit this vulnerability to retrieve sensitive data.
Patches
The issue has been fixed in Karmada Dashboard v0.2.0. This release enforces authentication for all API endpoints. Users are strongly advised to upgrade to version v0.2.0 or later as soon as possible.
Workarounds
If upgrading is not immediately feasible, users can mitigate the risk by:
- Restricting network access to the Karmada Dashboard service using Kubernetes Network Policies, firewall rules, or ingress controls.
- Placing the Dashboard behind a reverse proxy that enforces authentication (e.g., OAuth2 proxy) to add an additional layer of security.
References
- Karmada Dashboard v0.2.0 Release : https://github.com/karmada-io/dashboard/releases/tag/v0.2.0
- Fix PR #271
- Fix PR #280
- GitHub Advisory Database
- GitHub Reviewed
- CVE-2025-62714
Karmada Dashboard API Unauthorized Access Vulnerability
Critical severity GitHub Reviewed Published Oct 24, 2025 in karmada-io/dashboard • Updated Oct 24, 2025
Package
gomod github.com/karmada-io/dashboard (Go)
Affected versions
< 0.2.0
Impact
This is an authentication bypass vulnerability in the Karmada Dashboard API. The backend API endpoints (e.g., /api/v1/secret, /api/v1/service) did not enforce authentication, allowing unauthenticated users to access sensitive cluster information such as Secrets and Services directly. Although the web UI required a valid JWT for access, the API itself remained exposed to direct requests without any authentication checks. Any user or entity with network access to the Karmada Dashboard service could exploit this vulnerability to retrieve sensitive data.
Patches
The issue has been fixed in Karmada Dashboard v0.2.0. This release enforces authentication for all API endpoints. Users are strongly advised to upgrade to version v0.2.0 or later as soon as possible.
Workarounds
If upgrading is not immediately feasible, users can mitigate the risk by:
- Restricting network access to the Karmada Dashboard service using Kubernetes Network Policies, firewall rules, or ingress controls.
- Placing the Dashboard behind a reverse proxy that enforces authentication (e.g., OAuth2 proxy) to add an additional layer of security.
References
- Karmada Dashboard v0.2.0 Release : https://github.com/karmada-io/dashboard/releases/tag/v0.2.0
- Fix PR #271
- Fix PR #280
References
- GHSA-5qjg-9mjh-4r92
- karmada-io/dashboard#271
- karmada-io/dashboard#280
- https://github.com/karmada-io/dashboard/releases/tag/v0.2.0
Published to the GitHub Advisory Database
Oct 24, 2025
Last updated
Oct 24, 2025