@backstage/plugin-catalog-backend-module-bitbucket-server
Affected
- introduced
0.4.0, fixed0.5.15(semver)
Fixed versions
0.5.15
Fix
- Fixed version
0.5.15npm install @backstage/[email protected]
Advisory
Also known as: CVE-2026-106458
Backstage: Inconsistent repository filtering in Bitbucket Server catalog event updates
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
Medium Basis: The source's own band: MODERATE
0.4.0, fixed 0.5.15 (semver)0.5.15
0.5.15npm install @backstage/[email protected]Fix commands are the export's own generic commands. Ojuju never runs them. Check them against your setup first.
Check your own computer: guard packages check
Source: GitHub Advisory Database (reviewed advisories) · CC BY 4.0