<?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-08T01:48:05.913190+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-106562</id>
    <title>fkie_cve-2026-106562</title>
    <updated>2026-10-08T01:48:05.915290+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 2.1.6 in @backstage/plugin-search-backend and 1.8.7 in @backstage/plugin-search-backend-module-elasticsearch, search engine permission filtering could return documents denied by policy. An authenticated Backstage user subject to a DENY policy for search document types could receive unauthorized results in deployments with permission.enabled set to true and an Elasticsearch or OpenSearch backend. This issue is fixed in @backstage/plugin-search-backend 2.1.6 and @backstage/plugin-search-backend-module-elasticsearch 1.8.7.</p>
      </div>
    </content>
    <link href="https://vulnerability.circl.lu/vuln/fkie_cve-2026-106562"/>
  </entry>
  <entry>
    <id>https://vulnerability.circl.lu/vuln/ghsa-9325-vq29-gp3v</id>
    <title>GHSA-9325-vq29-gp3v — Backstage has incorrect authorization in search engine permission filtering</title>
    <updated>2026-10-08T01:48:05.915375+00:00</updated>
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml"><p><strong>Affected:</strong> npm: @backstage/plugin-search-backend, npm: @backstage/plugin-search-backend-module-elasticsearch</p>
<p>### Impact</p>
<p>An authenticated Backstage user subject to a `DENY` policy for search document types could receive search results they were not authorized to view. This affects deployments with `permission.enabled: true` and an Elasticsearch or OpenSearch search backend.</p>
<p>### Patches</p>
<p>- Upgrade `@backstage/plugin-search-backend` to 2.1.6
- Upgrade `@backstage/plugin-search-backend-module-elasticsearch` to 1.8.7</p>
<p>### Workarounds</p>
<p>If you are unable to upgrade immediately:</p>
<p>- Temporarily modify permission policies to use `CONDITIONAL` decisions with per-result filtering rather than blanket `DENY` for search document types
- Restrict Elasticsearch/OpenSearch index access at the cluster level so that the search service account can only reach expected Backstage indices, limiting the blast radius if the authorization bypass is triggered.</p></div>
    </content>
    <link href="https://vulnerability.circl.lu/vuln/ghsa-9325-vq29-gp3v"/>
  </entry>
</feed>
