Is CVE-2026-106563 exploited in the wild?

No. Junglewise Threat Intelligence has no report of CVE-2026-106563 being exploited in the wild.

How severe is CVE-2026-106563?

Medium severity, with a CVSS score of 5.3, published 7 October 2026.

Which products and versions are affected?

Backstage Plugin-Kubernetes-Backend < 0.21.8; @backstage/plugin-kubernetes-backend (npm) < 0.21.8, SEMVER:introduced=0,fixed=0.21.8.

How is CVE-2026-106563 attacked?

It is attacked over the network.

Am I affected by CVE-2026-106563?

Check whether you run Backstage Plugin-Kubernetes-Backend, Linuxfoundation Backstage\, Linuxfoundation Plugin-Kubernetes-Backend or one of the others listed at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

CVE-2026-106563: Backstage improper entity validation in Kubernetes services endpoint

Q: Is there a fix for CVE-2026-106563?

Yes. @backstage/plugin-kubernetes-backend (npm): upgrade to 0.21.8 or later. Until then: Disable the deprecated /services/:serviceId route by deploying a custom Kubernetes router that omits it, or restrict access to the kubernetes.resources.read permission to limit which users can reach the endpoint. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.

Q: How is CVE-2026-106563 attacked?

It is attacked over the network.

Q: Am I affected by CVE-2026-106563?

Check whether you run Backstage Plugin-Kubernetes-Backend, Linuxfoundation Backstage\, Linuxfoundation Plugin-Kubernetes-Backend or one of the others listed at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

CVE-2026-106563 · Severity: medium · CVSS 5.3 · Published 2026-10-07

Backstage is an open platform for building internal developer portals. An authenticated user with read access to Kubernetes could exploit improper validation in a deprecated endpoint to view Kubernetes workload metadata beyond their intended scope, gaining unauthorized visibility into container and infrastructure details across clusters.

Technologies: Linuxfoundation Backstage\, @backstage/plugin-kubernetes-backend (npm). Vendors: Backstage, Linuxfoundation, npm.

Quick answers

Is CVE-2026-106563 exploited in the wild?: No. Junglewise Threat Intelligence has no report of CVE-2026-106563 being exploited in the wild.
How severe is CVE-2026-106563?: Medium severity, with a CVSS score of 5.3, published 7 October 2026.
Which products and versions are affected?: Backstage Plugin-Kubernetes-Backend < 0.21.8; @backstage/plugin-kubernetes-backend (npm) < 0.21.8, SEMVER:introduced=0,fixed=0.21.8.
Is there a fix for CVE-2026-106563?: Yes. @backstage/plugin-kubernetes-backend (npm): upgrade to 0.21.8 or later. Until then: Disable the deprecated /services/:serviceId route by deploying a custom Kubernetes router that omits it, or restrict access to the kubernetes.resources.read permission to limit which users can reach the endpoint. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
How is CVE-2026-106563 attacked?: It is attacked over the network.
Am I affected by CVE-2026-106563?: Check whether you run Backstage Plugin-Kubernetes-Backend, Linuxfoundation Backstage\, Linuxfoundation Plugin-Kubernetes-Backend or one of the others listed at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

How to fix

@backstage/plugin-kubernetes-backend (npm): upgrade to 0.21.8 or later
```
npm install @backstage/plugin-kubernetes-backend@0.21.8
```

Disable the deprecated /services/:serviceId route by deploying a custom Kubernetes router that omits it, or restrict access to the kubernetes.resources.read permission to limit which users can reach the endpoint.

Technical details

The vulnerability exists in the deprecated /services/:serviceId endpoint of the Kubernetes plugin backend, where insufficient entity validation allows an authenticated attacker to supply crafted entity data to access Kubernetes object metadata across configured clusters. The attack requires network access, authentication, and low privileges (kubernetes.resources.read permission), but has high attack complexity. The exposure is limited to read-only metadata access with no data modification or availability impact.

Affected products

Backstage plugin-kubernetes-backend < 0.21.8

Identifiers

CVE-2026-106563
GHSA-r9ph-3637-55px

Timeline

2026-08-28: disclosed
2026-10-07: advisory

References

https://github.com/backstage/backstage/security/advisories/GHSA-r9ph-3637-55px

This page as Markdown. Free to reuse under CC BY 4.0 with a link back.