Authorization Flaw in @backstage/plugin-catalog-backend-module-bitbucket-server (CVE-2026-106458)
Summary
Vulnerability in @backstage/plugin-catalog-backend-module-bitbucket-server (CVE-2026-106458). Data can be tampered with by attackers. Mitigation: upgrade to 0.5.15 or later.
Original description
The description as published by the source.
Impact
Deployments using event-driven updates in the Bitbucket Server catalog provider may ingest catalog locations from repositories that are excluded by the provider's configured project, repository, or archived-repository filters.
An authenticated Bitbucket Server user who can push to a filtered-out repository that remains readable by the configured Backstage integration can trigger a legitimate repository event. The affected event path may then add a Location for that repository even though scheduled discovery excludes it. This can cause catalog entities and metadata to be ingested from a repository that the operator did not intend to trust.
Deployments that do not enable event support for the Bitbucket Server catalog provider, do not configure repository filters, or whose integration credentials cannot read the filtered-out repositories are not affected.
Patches
Upgrade @backstage/plugin-catalog-backend-module-bitbucket-server to version 0.5.15 or later. The fixed package is available in Backstage v1.55.0.
Workarounds
- Disable event-driven updates for the Bitbucket Server catalog provider and rely on scheduled discovery until the patched package is deployed.
- Restrict the configured Bitbucket Server integration credentials so that they cannot read repositories that must remain outside the catalog trust boundary.
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-106458 has been found in @backstage/plugin-catalog-backend-module-bitbucket-server.
Data can be tampered with by attackers. CVSS score: 6.5/10.
What to do: upgrade @backstage/plugin-catalog-backend-module-bitbucket-server to 0.5.15 or later.
If unsure, ask your IT team or search "@backstage/plugin-catalog-backend-module-bitbucket-server CVE-2026-106458" on the vendor's site.
CVE-2026-106458 (@backstage/plugin-catalog-backend-module-bitbucket-server) — CWE-863 / CVSS v3 6.5
Attack vector: remote (network-reachable) / no user interaction
Patched: 0.5.15 — 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.
Incorrect authorization (CWE-863) exists in @backstage/plugin-catalog-backend-module-bitbucket-server.
Check the vendor advisory for the affected versions of @backstage/plugin-catalog-backend-module-bitbucket-server.
Severity: Medium (CVSS 6.5/10). Data can be tampered with by attackers.
Update to 0.5.15.
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-catalog-backend-module-bitbucket-server' . 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-catalog-backend-module-bitbucket-server' . | grep -v node_modulesリポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で
@backstage/plugin-catalog-backend-module-bitbucket-serverを grep し、稼働しているサービス・バージョンを把握する。 -
2Apply patch patch
Upgrade @backstage/plugin-catalog-backend-module-bitbucket-server to 0.5.15ステージング環境で 0.5.15 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスを含めること。
-
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