All vulnerabilities
CVE-2026-106487GHSA-h53x-hjx6-25gr

@backstage/plugin-kubernetes-backend: Backstage: Unsupported catalog cluster authentication mode in kubernetes backend

backstage @backstage/plugin-kubernetes-backendnpmContainers & cloud
Open in ThreatlineRecord JSON
CVSS
3.5Low
ExploitationNo known exploitationNot in CISA KEV, which does not prove it is unexploitedCISA KEV
Exploit odds (EPSS)0.26%Chance of exploitation activity in the next 30 days, higher than 17% of CVEs. Scored 23 Oct 2026FIRST EPSS
Fixed in0.21.10Fixed versionGitHub
Published6 Oct 2026Updated 9 Oct 2026CVE List

What fixes it

  • 0.21.10@backstage/plugin-kubernetes-backend, npmGitHubnpm install @backstage/plugin-kubernetes-backend@0.21.10

A fixed version on one release line is not the upgrade target for every line. Check your exact version and any vendor backports.

Description

Impact

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.

Patches

Patched in @backstage/plugin-kubernetes-backend version 0.21.10

Workarounds

  • Do not configure service account authentication through catalog-provided clusters; use the supported static configuration method when service account authentication is required.
  • Restrict catalog ingestion so untrusted users cannot create or alter Kubernetes cluster Resource entities.

Text from GitHub Advisory Database

Affected versions 4

  • @backstage/plugin-kubernetes-backend, npm< 0.21.10GitHub
  • backstageaffected: < 1.54.6CVE List
  • plugin-kubernetes-backendaffected: < 0.21.10CVE List
  • @backstage/plugin-kubernetes-backend, npmfrom first release, fixed in 0.21.10OSV

References 5