@backstage/plugin-kubernetes-backend
Affected
- introduced
0, fixed0.21.9(semver)
Fixed versions
0.21.9
Fix
- Fixed version
0.21.9npm install @backstage/[email protected]
Advisory
Also known as: CVE-2026-106561
Backstage has a sensitive information disclosure in Kubernetes resource queries
Impact
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.
Patches
Fixed in @backstage/plugin-kubernetes-backend version 0.21.9
One behavior change is worth noting for adopters who expose custom resources: a custom resource whose list kind is reported by the API server as SecretList now has the values of its data field masked, matching how core Kubernetes Secrets have always been handled on other query paths.
Workarounds
kubernetes.resources.read to trusted users.ClusterRole in the Kubernetes plugin configuration documentation does not grant this access.Medium Basis: The source's own band: MODERATE
0, fixed 0.21.9 (semver)0.21.9
0.21.9npm install @backstage/[email protected]Fix commands are the export's own generic commands. Ojuju never runs them. Check them against your setup first.
Check your own computer: guard packages check
Source: GitHub Advisory Database (reviewed advisories) · CC BY 4.0