GHSA-gp6m-x9vw-5c5x: Medium severity npm/@backstage/plugin-catalog-backend-module-gitlab vulnerability

Published Oct 7, 2026
·
Updated

Impact

Deployments that enable GitLab organization event ingestion and rely on scoped catalog users as an access boundary may admit an unintended catalog identity. Depending on sign-in and permission configuration, this may allow unauthorized access with the permissions of a standard authenticated user.

Patches

- Upgrade @backstage/plugin-catalog-backend-module-gitlab to version 0.8.7.

Workarounds

- Disable event-driven GitLab organization ingestion and rely on scheduled discovery until upgrading. - Enforce organization membership independently at the authenticating proxy or sign-in resolver.

Affected Software

1 affected componentFixes available
npm/@backstage/plugin-catalog-backend-module-gitlab<0.8.7
0.8.7

Remediation

Recommended actions to resolve this vulnerability, in priority order.

  1. Upgrade

    Upgrade npm/@backstage/plugin-catalog-backend-module-gitlab to a version that resolves this vulnerability.

    Fixed in 0.8.7
  2. Upgrade

    Upgrade @backstage/plugin-catalog-backend-module-gitlab to a version that resolves this vulnerability.

    Fixed in 0.8.7
  3. Configuration

    Disable event-driven GitLab organization ingestion and rely on scheduled discovery until upgrading.

    Backstage GitLab organization ingestion event-driven GitLab organization ingestion = disabled
  4. Compensating control

    Enforce organization membership independently at the authenticating proxy or sign-in resolver.

Event History

Oct 7, 2026
Advisory Published
via GitHub·06:01 PM
Data Sourced
via GitHub·06:01 PM
DescriptionSeverityWeaknessAffected Software

Frequently Asked Questions

1

Which deployments are exposed to this issue?

Deployments that enable GitLab organization event ingestion and use scoped catalog users as an access boundary are affected. Exposure depends on the sign-in and permission configuration.

2

What access could an attacker gain?

An unintended catalog identity may be admitted, potentially giving unauthorized access with the permissions assigned to a standard authenticated user. Exploitation requires the ability to authenticate as a user; the advisory does not indicate anonymous access.

3

What should be done if upgrading cannot happen immediately?

Disable event-driven GitLab organization ingestion and use scheduled discovery instead. Also enforce organization membership separately through the authenticating proxy or sign-in resolver.

4

What version contains the fix?

Upgrade @backstage/plugin-catalog-backend-module-gitlab to version 0.8.7.

Contact

SecAlerts Pty Ltd.
132 Wickham Terrace
Fortitude Valley,
QLD 4006, Australia
info@secalerts.co
By using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.
© 2026 SecAlerts Pty Ltd.
ABN: 70 645 966 203, ACN: 645 966 203