CVE Intelligence

@backstage Plugin-kubernetes-backend vulnerabilities

🔔 Create alert RSS Version checker

Published CVEs affecting @backstage Plugin-kubernetes-backend: 3 record(s), with affected versions and fixes.

CVE-2026-106563 Medium · 5.3 CWE-20 Oct 7, 2026
Backstage: Improper entity validation in deprecated Kubernetes services endpoint
Backstage is an open framework for building developer portals. Prior to 0.21.8, the @backstage/plugin-kubernetes-backend package is affected by improper entity validation in deprecated kubernetes services endpoint. An authenticated user with Kubernetes read permissions could access Kubernetes workload data beyond their intended scope by supplying crafted entity data to the deprecated services endpoint. The exposure is limited to read-only access to Kubernetes object metadata across configured clusters. This issue is fixed in version 0.21.8.
CVE-2026-106561 Medium · 5.0 CWE-200 Oct 7, 2026
Backstage: Sensitive information disclosure in Kubernetes resource queries
Backstage is an open framework for building developer portals. Prior to 0.21.9, the @backstage/plugin-kubernetes-backend package is affected by sensitive information disclosure in kubernetes resource queries. An authenticated user holding the standard Kubernetes resource read permission could retrieve sensitive values that the Kubernetes plugin is designed to mask, potentially exposing credentials and other confidential material held in the connected clusters. Exposure is limited to resources that the Backstage service account is permitted to read and that match the targeted catalog entity's namespace and label selector. Deployments whose cluster credentials do not grant read access to these resources are unaffected. This issue is fixed in version 0.21.9.
CVE-2026-106487 Low · 3.5 CWE-441 Oct 6, 2026
Backstage: Unsupported catalog cluster authentication mode in kubernetes backend
Backstage is an open framework for building developer portals. Prior to 0.21.10, the @backstage/plugin-kubernetes-backend package is affected by unsupported catalog cluster authentication mode in kubernetes backend. Deployments using catalog cluster discovery may be affected when catalog contributors can create or modify kubernetes-cluster Resource entities. With the required endpoint permissions and pod RBAC, the backend can use its local in-cluster identity, potentially exposing Kubernetes resources readable by that identity. The credential is used only with the local in-cluster API endpoint and is not sent to the catalog-supplied endpoint. This issue is fixed in version 0.21.10.