Backstage is an open framework for building developer portals. From 0.4.0 until 0.5.15, the @backstage/plugin-catalog-backend-module-bitbucket-server package is affected by inconsistent repository filtering in bitbucket server catalog event updates. 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 issue is fixed in version 0.5.15.
Fix
Patch, vendor advisory and mitigation references on NVD 3
- https://github.com/backstage/backstage/commit/989db63b6f87c8fc04d440f296ad89e10c79b363 Patch
- https://github.com/backstage/backstage/releases/tag/v1.55.0 Patch, Release Notes
- https://github.com/backstage/backstage/security/advisories/GHSA-c36c-cf6r-ghgj Mitigation, Vendor Advisory
Every line above is quoted from NVD, CISA, Microsoft, the vendor's own advisory or DISA; nothing is generated.
Change history 1
- First seenCVSS 6.5 · linuxfoundationNVD modified 2026-10-27 20:42
Affected (CPE criteria) 2
cpe:2.3:a:linuxfoundation:backstage\/plugin-catalog-backend-module-bitbucket-server:*:*:*:*:*:node.js:*:*cpe:2.3:a:linuxfoundation:backstage:*:*:*:*:*:*:*:*