Advisory

GHSA-p795-mqf2-36mf

Also known as: CVE-2026-106561

Summary

Backstage has a sensitive information disclosure in Kubernetes resource queries

Details

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

  • Enable the permission framework and restrict kubernetes.resources.read to trusted users.
  • Scope the RBAC of the service account used to reach each cluster so that it cannot read sensitive resource types. The recommended ClusterRole in the Kubernetes plugin configuration documentation does not grant this access.

Severity

Medium Basis: The source's own band: MODERATE

Dates

Published
2026-10-07 18:02 UTC
Modified
2026-10-07 18:15 UTC

Affected packages and fixes

@backstage/plugin-kubernetes-backend

npm · All systems

Affected

  • introduced 0, fixed 0.21.9 (semver)

Fixed versions

0.21.9

Fix

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

View this record on OSV.dev

Source

Source: GitHub Advisory Database (reviewed advisories) · CC BY 4.0

Sources & licences