Sign in Sign up
JA · EN · FR
SecPulse
Categories
CVE-2026-106561 medium CVSS 5.0

Information Disclosure in @backstage/plugin-kubernetes-backend (CVE-2026-106561)

Summary

Vulnerability in @backstage/plugin-kubernetes-backend (CVE-2026-106561). Risk of unauthorized operations or information disclosure. Exploitable via kubernetes.resources.read. Mitigation: upgrade to 0.21.9 or later.

Original description

The description as published by the source.

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.

Source: NIST National Vulnerability Database NVD GitHub Advisory

Auto-generated summary

Assembled by SecPulse from the source data (CVSS, CWE, affected versions) using templates — no AI involved. Check the original description and references below for exact details.

A vulnerability tracked as CVE-2026-106561 has been found in @backstage/plugin-kubernetes-backend.
Attackers can target a specific entry point like kubernetes.resources.read over the network to misuse the product.
Risk of unauthorized operations or information disclosure. CVSS score: 5.0/10.
What to do: upgrade @backstage/plugin-kubernetes-backend to 0.21.9 or later.
If unsure, ask your IT team or search "@backstage/plugin-kubernetes-backend CVE-2026-106561" on the vendor's site.

CVE-2026-106561 (@backstage/plugin-kubernetes-backend) — CWE-200 / CVSS v3 5.0
Attack vector: remote (network-reachable) / no user interaction
Attack surface: kubernetes.resources.read / ClusterRole
Patched: 0.21.9 — apply immediately
Plan: 1) Audit SBOM/dependencies, 2) Stage→prod upgrade, 3) Add WAF/proxy monitoring on affected endpoints, 4) Hunt IOCs in logs.
Refs: see the GHSA / vendor advisory / patched release linked on this page.

❓ What is the problem

Information disclosure (CWE-200) exists in @backstage/plugin-kubernetes-backend. Attackers reach the vulnerable code path via kubernetes.resources.read.

📍 Affected scope

Check the vendor advisory for the affected versions of @backstage/plugin-kubernetes-backend. Attack surface: kubernetes.resources.read / ClusterRole.

🔥 Severity

Severity: Medium (CVSS 5.0/10). Risk of unauthorized operations or information disclosure.

🔧 How to fix

Update to 0.21.9.

🛡️ Workaround

Until the patch is applied: disable the affected feature, apply WAF rules, or restrict access via network ACLs.

🔍 Detection

Search webserver/proxy logs for unusual request patterns matching this CVE's known IOCs. Run grep -r '@backstage/plugin-kubernetes-backend' . against your dependency files (package-lock.json, requirements.txt, go.sum) to find affected services.

Response actions

Concrete steps and command examples for SOC/SRE teams to execute in order

  1. 1
    Identify exposure identify 
    grep -r '@backstage/plugin-kubernetes-backend' . | grep -v node_modules

    リポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で @backstage/plugin-kubernetes-backend を grep し、稼働しているサービス・バージョンを把握する。

  2. 2
    Apply patch patch 
    Upgrade @backstage/plugin-kubernetes-backend to 0.21.9

    ステージング環境で 0.21.9 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスを含めること。

  3. 3
    Post-deployment verification verify 
    Confirm patched version is live in production

    パッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番ではアクセスログ・WAF でアラート再発が無いか継続監視。

Affected packages

npm @backstage/plugin-kubernetes-backend
[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0.21.9"}]}]

References

We use cookies for analytics and ad measurement. This setting applies to all Game co., Ltd. sites. Details