{
  "affected": [
    {
      "ranges": [
        {
          "database_specific": {
            "extracted_events": [
              {
                "introduced": "1.38.0"
              },
              {
                "fixed": "1.55.0"
              }
            ],
            "source": [
              "AFFECTED_FIELD",
              "REFERENCES"
            ]
          },
          "events": [
            {
              "introduced": "1a85f9d7b8c2ae48bc8c2386ade4f0e9e5cb157b"
            },
            {
              "fixed": "989db63b6f87c8fc04d440f296ad89e10c79b363"
            },
            {
              "fixed": "23161ae67d0f064e97c60c4c62b86e94c43a383e"
            }
          ],
          "repo": "https://github.com/backstage/backstage",
          "type": "GIT"
        }
      ]
    }
  ],
  "aliases": [
    "GHSA-c36c-cf6r-ghgj"
  ],
  "database_specific": {
    "cna_assigner": "GitHub_M",
    "cwe_ids": [
      "CWE-863"
    ],
    "osv_generated_from": "https://github.com/CVEProject/cvelistV5/tree/main/cves/2026/106xxx/CVE-2026-106458.json",
    "unresolved_ranges": [
      {
        "extracted_events": [
          {
            "introduced": "0.4.0"
          },
          {
            "fixed": "0.5.15"
          }
        ],
        "source": "AFFECTED_FIELD"
      }
    ]
  },
  "details": "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.",
  "id": "CVE-2026-106458",
  "modified": "2026-10-09T02:30:36.955531150Z",
  "published": "2026-10-06T20:16:12.035Z",
  "references": [
    {
      "type": "WEB",
      "url": "https://github.com/backstage/backstage/releases/tag/v1.55.0"
    },
    {
      "type": "ADVISORY",
      "url": "https://github.com/CVEProject/cvelistV5/tree/main/cves/2026/106xxx/CVE-2026-106458.json"
    },
    {
      "type": "ADVISORY",
      "url": "https://github.com/backstage/backstage/security/advisories/GHSA-c36c-cf6r-ghgj"
    },
    {
      "type": "ADVISORY",
      "url": "https://nvd.nist.gov/vuln/detail/CVE-2026-106458"
    },
    {
      "type": "FIX",
      "url": "https://github.com/backstage/backstage/commit/989db63b6f87c8fc04d440f296ad89e10c79b363"
    }
  ],
  "schema_version": "1.9.0",
  "severity": [
    {
      "score": "CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:H/A:N",
      "type": "CVSS_V3"
    }
  ],
  "summary": "Backstage: Inconsistent repository filtering in Bitbucket Server catalog event updates"
}