<?xml version='1.0' encoding='UTF-8'?>
<?xml-stylesheet href="/static/style.xsl" type="text/xsl"?>
<feed xmlns="http://www.w3.org/2005/Atom" xml:lang="en">
  <id>https://vulnerability.circl.lu/rss/recent/all/10</id>
  <title>Most recent entries from all</title>
  <updated>2026-10-08T05:57:45.333593+00:00</updated>
  <author>
    <name>Vulnerability-Lookup</name>
    <email>info@circl.lu</email>
  </author>
  <link href="https://vulnerability.circl.lu" rel="alternate"/>
  <generator uri="https://lkiesow.github.io/python-feedgen" version="1.0.0">python-feedgen</generator>
  <subtitle>Contains only the most 10 recent entries.</subtitle>
  <entry>
    <id>https://vulnerability.circl.lu/vuln/fkie_cve-2026-106563</id>
    <title>fkie_cve-2026-106563</title>
    <updated>2026-10-08T05:57:45.339460+00:00</updated>
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml">
        <p>Backstage is an open framework for building developer portals. Prior to 0.21.8, the @backstage/plugin-kubernetes-backend package is affected by improper entity validation in deprecated kubernetes services endpoint. 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. This issue is fixed in version 0.21.8.</p>
      </div>
    </content>
    <link href="https://vulnerability.circl.lu/vuln/fkie_cve-2026-106563"/>
  </entry>
  <entry>
    <id>https://vulnerability.circl.lu/vuln/ghsa-r9ph-3637-55px</id>
    <title>GHSA-r9ph-3637-55px — Backstage: Improper entity validation in deprecated Kubernetes services endpoint</title>
    <updated>2026-10-08T05:57:45.339619+00:00</updated>
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml"><p><strong>Affected:</strong> npm: @backstage/plugin-kubernetes-backend</p>
<p>### Impact</p>
<p>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.</p>
<p>### Patches</p>
<p>Patched in `@backstage/plugin-kubernetes-backend` version 0.21.8.</p>
<p>### Workarounds</p>
<p>- 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.</p></div>
    </content>
    <link href="https://vulnerability.circl.lu/vuln/ghsa-r9ph-3637-55px"/>
  </entry>
</feed>
