How severe is GHSA-r9ph-3637-55px?

GHSA-r9ph-3637-55px has a CVSS score of 5.3/10, rated MEDIUM. Review your exposure and patch according to your risk tolerance.

Which packages are affected by GHSA-r9ph-3637-55px?

GHSA-r9ph-3637-55px affects the following packages: @backstage/plugin-kubernetes-backend (npm). Ecosystems affected: npm.

How do I fix GHSA-r9ph-3637-55px?

Update @backstage/plugin-kubernetes-backend to 0.21.8 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-r9ph-3637-55px is resolved across your whole dependency graph.

How do I detect GHSA-r9ph-3637-55px in my npm dependencies?

Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for @backstage/plugin-kubernetes-backend, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.

How do I mitigate GHSA-r9ph-3637-55px if there is no patch (or I can't update yet)?

Put an independent control in front of the weakness: restrict the affected endpoint or interface to trusted networks, require an additional authentication factor or proxy-level check, and invalidate existing sessions and credentials in case the flaw has already been used.

Is GHSA-r9ph-3637-55px actively exploited in the wild?

No public exploit code has been indexed for GHSA-r9ph-3637-55px yet. This does not mean the vulnerability cannot be exploited — absence of public exploits does not imply safety. Apply the recommended fix and use O3 Security to monitor your exposure.

What is the EPSS score for GHSA-r9ph-3637-55px?

GHSA-r9ph-3637-55px has an EPSS (Exploit Prediction Scoring System) score of 0.2%, placing it in the 12th percentile of all CVEs. EPSS is maintained by FIRST.org and estimates the probability that a vulnerability will be exploited in the wild within the next 30 days. This score indicates relatively lower exploitation probability, though the CVSS severity should still guide your patching priority.

What type of vulnerability is GHSA-r9ph-3637-55px?

GHSA-r9ph-3637-55px is classified as Improper Input Validation (CWE-20), CWE-862 (CWE-862). These weakness types describe the underlying flaw category, which helps determine the potential impact and the right class of mitigation.

When was GHSA-r9ph-3637-55px published, and has it been updated?

GHSA-r9ph-3637-55px was published on October 7, 2026 and was last updated on October 7, 2026. Advisory data evolves as severity scores, affected ranges, and exploit intelligence are revised — always check the latest version of the advisory before acting.

📦

📦 npm

Not in CISA KEV

MEDIUM severity

Backstage: Improper entity validation in deprecated Kubernetes services endpointGHSA-r9ph-3637-55px

MEDIUMFix: backstage/backstage@2d5d3e7

GHSA-r9ph-3637-55px is a medium-severity (CVSS 5.3) Improper Input Validation vulnerability in @backstage/plugin-kubernetes-backend. A fix is available for @backstage/plugin-kubernetes-backend — see the affected versions and patch details below.

Also known asCVE-2026-106563

Published

Oct 7, 2026

Updated

Oct 7, 2026

Affected

1 pkg

Patched

1 / 1

Exploits

None indexed

Exploitation data as of Oct 24, 2026 · OSV.dev, NVD, FIRST.org (EPSS)

Exploitation Status

No confirmed exploitation observed yet

CISA’s own triage has not observed active exploitation or public proof-of-concept code for this CVE as of its last assessment.

Exploitation and automatability from CISA’s SSVC triage for GHSA-r9ph-3637-55px.

EPSS Exploitation Probability

via FIRST.org ↗

0.2%probability of exploitation in next 30 days

Lower Risk0.00%

Lower risk than most CVEs12th percentile — riskier than 12% of all scored CVEsHighest risk

Probability of exploitation in the next 30 days, from FIRST.org EPSS.

How urgent is this, really

GHSA-r9ph-3637-55px by exploitation likelihood (EPSS) against impact (CVSS). Outside the shaded patch-first corner.

Where this sits among everything scored

Of 394,803 CVEs with a current EPSS score, this one falls in the < 10% band (highlighted). Counts from FIRST.org, log-scaled.

Real-World Exposure

1 pkg affected

How broadly this vulnerability is actually deployed: weekly install volume shows current usage, and reverse-dependency count shows how many other packages break if it stays unpatched.

9other npm packages depend on this — each one inherits the vulnerability until it's patched upstream

@backstage/plugin-kubernetes-backendnpm

49Kdownloads / week

Description

Impact

An authenticated user with Kubernetes read permissions could access Kubernetes workload data beyond their intended scope by supplying crafted entity data to the deprecated services endpoint. The exposure is limited to read-only access to Kubernetes object metadata across configured clusters.

Patches

Patched in @backstage/plugin-kubernetes-backend version 0.21.8.

Workarounds

Disable the deprecated /services/:serviceId route by deploying a custom Kubernetes router that omits it.
Restrict access to the kubernetes.resources.read permission to limit the set of users who can reach the endpoint.

Affected Packages

1 total 1 fixed

Ecosystem	Package	Vulnerable range	Fix
📦npm	`@backstage/plugin-kubernetes-backend`	all versions	0.21.8`npm install @backstage/plugin-kubernetes-backend@0.21.8`

Affected Products

2 products · 2 configurations

Application

backstagelinuxfoundation

< 1.54.1

range

Application

backstage\/plugin-kubernetes-backendlinuxfoundation

< 0.21.8

range

Detection & mitigation playbook

Open-source dependency

Detect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for @backstage/plugin-kubernetes-backend, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update @backstage/plugin-kubernetes-backend to 0.21.8 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-r9ph-3637-55px is resolved across your whole dependency graph.
Workarounds
Put an independent control in front of the weakness: restrict the affected endpoint or interface to trusted networks, require an additional authentication factor or proxy-level check, and invalidate existing sessions and credentials in case the flaw has already been used.

Frequently Asked Questions

### Impact An authenticated user with Kubernetes read permissions could access Kubernetes workload data beyond their intended scope by supplying crafted entity data to the deprecated services endpoint. The exposure is limited to read-only access to Kubernetes object metadata across configured clusters. ### Patches Patched in `@backstage/plugin-kubernetes-backend` version 0.21.8. ### Workarounds - Disable the deprecated `/services/:serviceId` route by deploying a custom Kubernetes router that omits it. - Restrict access to the `kubernetes.resources.read` permission to limit the set of user