GHSA-H53X-HJX6-25GR

Vulnerability from github – Published: 2026-10-07 18:01 – Updated: 2026-10-07 18:01
VLAI
Summary
Backstage: Unsupported catalog cluster authentication mode in kubernetes backend
Details

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.
Show details on source website

{
  "affected": [
    {
      "package": {
        "ecosystem": "npm",
        "name": "@backstage/plugin-kubernetes-backend"
      },
      "ranges": [
        {
          "events": [
            {
              "introduced": "0"
            },
            {
              "fixed": "0.21.10"
            }
          ],
          "type": "ECOSYSTEM"
        }
      ]
    }
  ],
  "aliases": [
    "CVE-2026-106487"
  ],
  "database_specific": {
    "cwe_ids": [
      "CWE-441"
    ],
    "github_reviewed": true,
    "github_reviewed_at": "2026-10-07T18:01:08Z",
    "nvd_published_at": "2026-10-06T21:17:17Z",
    "severity": "LOW"
  },
  "details": "### Impact\n\nDeployments 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.\n\n### Patches\n\nPatched in `@backstage/plugin-kubernetes-backend` version `0.21.10`\n\n### Workarounds\n\n- Do not configure service account authentication through catalog-provided clusters; use the supported static configuration method when service account authentication is required.\n- Restrict catalog ingestion so untrusted users cannot create or alter Kubernetes cluster Resource entities.",
  "id": "GHSA-h53x-hjx6-25gr",
  "modified": "2026-10-07T18:01:08Z",
  "published": "2026-10-07T18:01:08Z",
  "references": [
    {
      "type": "WEB",
      "url": "https://github.com/backstage/backstage/security/advisories/GHSA-h53x-hjx6-25gr"
    },
    {
      "type": "ADVISORY",
      "url": "https://nvd.nist.gov/vuln/detail/CVE-2026-106487"
    },
    {
      "type": "WEB",
      "url": "https://github.com/backstage/backstage/commit/c14f8be6908f0f719b16356e5492352311e28946"
    },
    {
      "type": "PACKAGE",
      "url": "https://github.com/backstage/backstage"
    },
    {
      "type": "WEB",
      "url": "https://github.com/backstage/backstage/releases/tag/v1.54.6"
    }
  ],
  "schema_version": "1.4.0",
  "severity": [
    {
      "score": "CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:C/C:L/I:N/A:N",
      "type": "CVSS_V3"
    }
  ],
  "summary": "Backstage: Unsupported catalog cluster authentication mode in kubernetes backend"
}



Log in or create an account to share your comment.




Tags
Taxonomy of the tags.


Loading…

Loading…

Loading…

Forecast uses a logistic model when the trend is rising, or an exponential decay model when the trend is falling. Fitted via linearized least squares.

Sightings

Author Source Type Date Other

Nomenclature

  • Seen: The vulnerability was mentioned, discussed, or observed by the user.
  • Confirmed: The vulnerability has been validated from an analyst's perspective.
  • Published Proof of Concept: A public proof of concept is available for this vulnerability.
  • Exploited: The vulnerability was observed as exploited by the user who reported the sighting.
  • Patched: The vulnerability was observed as successfully patched by the user who reported the sighting.
  • Not exploited: The vulnerability was not observed as exploited by the user who reported the sighting.
  • Not confirmed: The user expressed doubt about the validity of the vulnerability.
  • Not patched: The vulnerability was not observed as successfully patched by the user who reported the sighting.

Loading…

Loading…

Loading…

Related by attack behaviour

Vulnerabilities whose description is nearest to this one in the vector space of the CIRCL/vulnerability-attack-technique-biencoder model. This is a similarity search over the bi-encoder space (plain cosine), not a classification, and it has no measured accuracy.


Loading…