CVE-2026-106563: Backstage · Improper entity validation in deprecated Kubernetes services endpoint
Affects @backstage/plugin-kubernetes-backendSource GCVE Database
Not known to be exploited · CVSS 5.3 Medium : upgrade to 0.21.8 when convenient.
Data as of 21 Nov 2026, 17:34 UTC
- EPSS
- 0.2% chance of exploitation in 30 days – higher than 13% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
- Patch
- Available – fixed in 0.21.8
CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:U/C:H/I:N/A:NExploitation evidence
Disclosed: evidence found.
CVE published 7 Oct 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponized: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors
A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 21 Nov 2026.
What to do
Upgrade @backstage/plugin-kubernetes-backend to 0.21.8.
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| npm@backstage/plugin-kubernetes-backend | Affected
| Fixed in
|
Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.
AI-suggested
A patch is available in @backstage/plugin-kubernetes-backend version 0.21.8 and should be applied to remediate this vulnerability. Alternatively, the deprecated /services/:serviceId route can be disabled by deploying a custom Kubernetes router that omits this endpoint. Additionally, restricting the kubernetes.resources.read permission to limit which users can access this endpoint can mitigate the risk.
Description
An improper entity validation vulnerability exists in the deprecated Kubernetes services endpoint of the @backstage/plugin-kubernetes-backend. Authenticated users with Kubernetes read permissions can exploit this flaw to access Kubernetes workload metadata beyond their intended scope. The exposure is limited to read-only access of Kubernetes object metadata across configured clusters. The issue is patched in version 0.21.8 of the plugin. Workarounds include disabling the deprecated endpoint or restricting read permissions.
References
- github.com/backstage/backstage/security/advisories/GHSA-r9ph-3637-55px (opens in a new tab)
- nvd.nist.gov/vuln/detail/CVE-2026-106563 (opens in a new tab)
- github.com/backstage/backstage/commit/2d5d3e77d630455d6d48cfa8f31fd3c126fd6f29 (opens in a new tab)
- github.com/backstage/backstage (opens in a new tab)
- github.com/backstage/backstage/releases/tag/v1.54.1 (opens in a new tab)