What is CVE-2026-106458?

CVE-2026-106458 is a medium-severity incorrect authorization vulnerability in @backstage/plugin-catalog-backend-module-bitbucket-server (npm), affecting versions >= 0.4.0, < 0.5.15. It is fixed in 0.5.15. The application does not correctly enforce access controls, allowing a principal to access resources or operations beyond their granted permissions.

How severe is CVE-2026-106458?

CVE-2026-106458 has a CVSS score of 6.5 (Medium). This score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether it represents real risk in your environment depends on whether the vulnerable code is present and reachable.

Is there a fix for CVE-2026-106458?

Yes. CVE-2026-106458 is fixed in 0.5.15. Upgrade to this version or later.

Is CVE-2026-106458 exploitable, and should I be worried?

Whether CVE-2026-106458 is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk.

What actually determines whether CVE-2026-106458 is exploitable, and how bad it is?

Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.

CVE-2026-106458

Q: How severe is CVE-2026-106458?

CVE-2026-106458 has a CVSS score of 6.5 (Medium). This score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether it represents real risk in your environment depends on whether the vulnerable code is present and reachable.

Q: Is there a fix for CVE-2026-106458?

Yes. CVE-2026-106458 is fixed in 0.5.15. Upgrade to this version or later.

Q: Is CVE-2026-106458 exploitable, and should I be worried?

Whether CVE-2026-106458 is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk.

Q: What actually determines whether CVE-2026-106458 is exploitable, and how bad it is?

Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.

Q: How do I fix CVE-2026-106458?

Upgrade @backstage/plugin-catalog-backend-module-bitbucket-server to 0.5.15 or later.

Summary

Backstage: Inconsistent repository filtering in Bitbucket Server catalog event updates

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.

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.

The application does not correctly enforce access controls, allowing a principal to access resources or operations beyond their granted permissions. Typical impact: unauthorized data access or execution of privileged operations.

CVE-2026-106458 has a CVSS score of 6.5 (Medium). The vector is network-reachable, low privileges required, and no user interaction. A CVSS score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether this affects your application depends on whether the vulnerable code is present and reachable in your environment. A fixed version is available (0.5.15); upgrading removes the vulnerable code path.

Affected versions

@backstage/plugin-catalog-backend-module-bitbucket-server (>= 0.4.0, < 0.5.15)

Security releases

@backstage/plugin-catalog-backend-module-bitbucket-server → 0.5.15 (npm)

Kodem intelligence

Severity tells you how bad this could be in the worst case. It does not tell you whether you are exposed. Exploitability and impact are functions of runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A vulnerable package can sit in your dependency tree and never run.

Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter. Kodem's runtime-powered SCA identifies whether this CVE is reachable in your applications.

Already deployed Kodem?

See it in your environment New to Kodem? Get a demo →

Remediation advice

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.

Frequently Asked Questions

What is CVE-2026-106458? CVE-2026-106458 is a medium-severity incorrect authorization vulnerability in @backstage/plugin-catalog-backend-module-bitbucket-server (npm), affecting versions >= 0.4.0, < 0.5.15. It is fixed in 0.5.15. The application does not correctly enforce access controls, allowing a principal to access resources or operations beyond their granted permissions.
How severe is CVE-2026-106458? CVE-2026-106458 has a CVSS score of 6.5 (Medium). This score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether it represents real risk in your environment depends on whether the vulnerable code is present and reachable.
Which versions of @backstage/plugin-catalog-backend-module-bitbucket-server are affected by CVE-2026-106458? @backstage/plugin-catalog-backend-module-bitbucket-server (npm) versions >= 0.4.0, < 0.5.15 is affected.
Is there a fix for CVE-2026-106458? Yes. CVE-2026-106458 is fixed in 0.5.15. Upgrade to this version or later.
Is CVE-2026-106458 exploitable, and should I be worried? Whether CVE-2026-106458 is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk. Get a demo
What actually determines whether CVE-2026-106458 is exploitable, and how bad it is? Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.
How do I fix CVE-2026-106458? Upgrade @backstage/plugin-catalog-backend-module-bitbucket-server to 0.5.15 or later.