Vulnerability in @backstage/plugin-search-backend (CVE-2026-106562)
Summary
Vulnerability in @backstage/plugin-search-backend (CVE-2026-106562). Risk of unauthorized operations or information disclosure. Exploitable via DENY. Mitigation: upgrade to 2.1.6 or later.
Original description
The description as published by the source.
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-backendto 2.1.6 - Upgrade
@backstage/plugin-search-backend-module-elasticsearchto 1.8.7
Workarounds
If you are unable to upgrade immediately:
- Temporarily modify permission policies to use
CONDITIONALdecisions with per-result filtering rather than blanketDENYfor 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.
Source: NIST National Vulnerability Database NVD GitHub Advisory
Auto-generated summary
Assembled by SecPulse from the source data (CVSS, CWE, affected versions) using templates — no AI involved. Check the original description and references below for exact details.
A vulnerability tracked as CVE-2026-106562 has been found in @backstage/plugin-search-backend.
Attackers can target a specific entry point like DENY over the network to misuse the product.
Risk of unauthorized operations or information disclosure. CVSS score: 4.3/10.
What to do: upgrade @backstage/plugin-search-backend to 2.1.6 or later.
If unsure, ask your IT team or search "@backstage/plugin-search-backend CVE-2026-106562" on the vendor's site.
CVE-2026-106562 (@backstage/plugin-search-backend) — CWE-754 / CVSS v3 4.3
Attack vector: remote (network-reachable) / no user interaction
Attack surface: DENY / CONDITIONAL
Patched: 2.1.6 — apply immediately
Plan: 1) Audit SBOM/dependencies, 2) Stage→prod upgrade, 3) Add WAF/proxy monitoring on affected endpoints, 4) Hunt IOCs in logs.
Refs: see the GHSA / vendor advisory / patched release linked on this page.
A vulnerability (CWE-754) exists in @backstage/plugin-search-backend. Attackers reach the vulnerable code path via DENY.
Check the vendor advisory for the affected versions of @backstage/plugin-search-backend. Attack surface: DENY / CONDITIONAL.
Severity: Medium (CVSS 4.3/10). Risk of unauthorized operations or information disclosure.
Update to 2.1.6.
Until the patch is applied: disable the affected feature, apply WAF rules, or restrict access via network ACLs.
Search webserver/proxy logs for unusual request patterns matching this CVE's known IOCs. Run grep -r '@backstage/plugin-search-backend' . against your dependency files (package-lock.json, requirements.txt, go.sum) to find affected services.
Response actions
Concrete steps and command examples for SOC/SRE teams to execute in order
-
1Identify exposure identify
grep -r '@backstage/plugin-search-backend' . | grep -v node_modulesリポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で
@backstage/plugin-search-backendを grep し、稼働しているサービス・バージョンを把握する。 -
2Apply patch patch
Upgrade @backstage/plugin-search-backend to 2.1.6ステージング環境で 2.1.6 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスを含めること。
-
3Post-deployment verification verify
Confirm patched version is live in productionパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番ではアクセスログ・WAF でアラート再発が無いか継続監視。
Affected packages
References
- advisory nvd.nist.gov
- package github.com
- web github.com
- web github.com
- web github.com
- web github.com