Your RSA-2048 keys break in 2030. Find every one of them before attackers do.
📦
📦 npm
Not in CISA KEV
MEDIUM severity

Backstage has incorrect authorization in search engine permission filteringGHSA-9325-vq29-gp3v

MEDIUMFix: backstage/backstage@2d5d3e7

GHSA-9325-vq29-gp3v is a medium-severity (CVSS 4.3) CWE-754 vulnerability in @backstage/plugin-search-backend. A fix is available for @backstage/plugin-search-backend — see the affected versions and patch details below.

Also known asCVE-2026-106562
Published
Updated
Affected
2 pkgs
Patched
2 / 2
Exploits
None indexed
Exploitation data as of Oct 22, 2026 · OSV.dev, NVD, FIRST.org (EPSS)

EPSS Exploitation Probability

via FIRST.org ↗
0.2%probability of exploitation in next 30 days
Lower Risk0.00%
Lower risk than most CVEs9th percentile — riskier than 9% of all scored CVEsHighest risk

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

How urgent is this, really

GHSA-9325-vq29-gp3v by exploitation likelihood (EPSS) against impact (CVSS). Outside the shaded patch-first corner.

Where this sits among everything scored

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

Real-World Exposure

2 pkgs 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.

4other npm packages depend on this — each one inherits the vulnerability until it's patched upstream
@backstage/plugin-search-backendnpm
60Kdownloads / week
@backstage/plugin-search-backend-module-elasticsearchnpm
4Kdownloads / week

Description

Impact

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.

Patches

  • Upgrade @backstage/plugin-search-backend to 2.1.6
  • Upgrade @backstage/plugin-search-backend-module-elasticsearch to 1.8.7

Workarounds

If you are unable to upgrade immediately:

  • 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.

Affected Packages

2 total 2 fixed
EcosystemPackageVulnerable rangeFix
📦npm@backstage/plugin-search-backendall versions2.1.6npm install @backstage/plugin-search-backend@2.1.6
📦npm@backstage/plugin-search-backend-module-elasticsearchall versions1.8.7npm install @backstage/plugin-search-backend-module-elasticsearch@1.8.7

Affected Products

3 products · 3 configurations
Application
backstagelinuxfoundation
< 1.54.1
range
Application
backstage\/plugin-search-backendlinuxfoundation
< 2.1.6
range
Application
backstage\/plugin-search-backend-module-elasticsearchlinuxfoundation
< 1.8.7
range

Detection & mitigation playbook

Open-source dependency

  1. Detect

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

  2. Fix

    Update @backstage/plugin-search-backend to 2.1.6 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-9325-vq29-gp3v is resolved across your whole dependency graph.

  3. 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.

Fixing This On Your OS

If you run this on a Linux distribution, patch through your package manager against the distro's own security advisory below — it tracks the exact backported fix for your release, which can ship on a different timeline (and sometimes a different severity) than the upstream project.

Red HatModerate

This vulnerability is rated as Moderate because exploitation requires authenticated user credentials and specific environment configurations, specifically having authorization policies enabled alongside Elasticsearch or OpenSearch search indexing. In affected deployments, such as Red Hat Developer Hub or Ansible…

Workaround published by Red Hat
Mitigation for this issue is either not available or the currently available options do not meet the Red Hat Product Security criteria comprising ease of use and deployment, applicability to widespread installation base, or stability.
Source: Red Hat security advisory for GHSA-9325-vq29-gp3v (CC BY 4.0)

Frequently Asked Questions

### Impact 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. ### Patches - Upgrade `@backstage/plugin-search-backend` to 2.1.6 - Upgrade `@backstage/plugin-search-backend-module-elasticsearch` to 1.8.7 ### Workarounds If you are unable to upgrade immediately: - Temporarily modify permission policies to use `CONDITIONAL` decisions with per-result filtering rather than blanket `DENY` for
O3 Security · Impact-Aware SCA

Is GHSA-9325-vq29-gp3v in your dependencies?

Find it across npm, including transitive dependencies.

Scan my dependencies How O3 SCA works
Backstage has incorrect authorization in search engine…