How severe is GHSA-gp6m-x9vw-5c5x?

GHSA-gp6m-x9vw-5c5x has a CVSS score of 5.4/10, rated MEDIUM. Review your exposure and patch according to your risk tolerance.

Which packages are affected by GHSA-gp6m-x9vw-5c5x?

GHSA-gp6m-x9vw-5c5x affects the following packages: @backstage/plugin-catalog-backend-module-gitlab (npm). Ecosystems affected: npm.

How do I fix GHSA-gp6m-x9vw-5c5x?

Update @backstage/plugin-catalog-backend-module-gitlab to 0.8.7 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-gp6m-x9vw-5c5x is resolved across your whole dependency graph.

How do I detect GHSA-gp6m-x9vw-5c5x in my npm dependencies?

Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for @backstage/plugin-catalog-backend-module-gitlab, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.

How do I mitigate GHSA-gp6m-x9vw-5c5x if there is no patch (or I can't update yet)?

Put an independent control in front of the weakness: restrict the affected endpoint or interface to trusted networks, require an additional authentication factor or proxy-level check, and invalidate existing sessions and credentials in case the flaw has already been used.

Is GHSA-gp6m-x9vw-5c5x actively exploited in the wild?

No public exploit code has been indexed for GHSA-gp6m-x9vw-5c5x yet. This does not mean the vulnerability cannot be exploited — absence of public exploits does not imply safety. Apply the recommended fix and use O3 Security to monitor your exposure.

What is the EPSS score for GHSA-gp6m-x9vw-5c5x?

GHSA-gp6m-x9vw-5c5x has an EPSS (Exploit Prediction Scoring System) score of 0.2%, placing it in the 6th percentile of all CVEs. EPSS is maintained by FIRST.org and estimates the probability that a vulnerability will be exploited in the wild within the next 30 days. This score indicates relatively lower exploitation probability, though the CVSS severity should still guide your patching priority.

What type of vulnerability is GHSA-gp6m-x9vw-5c5x?

GHSA-gp6m-x9vw-5c5x is classified as CWE-863 (CWE-863). This weakness type describe the underlying flaw category, which helps determine the potential impact and the right class of mitigation.

When was GHSA-gp6m-x9vw-5c5x published, and has it been updated?

GHSA-gp6m-x9vw-5c5x was published on October 7, 2026 and was last updated on October 7, 2026. Advisory data evolves as severity scores, affected ranges, and exploit intelligence are revised — always check the latest version of the advisory before acting.

📦

📦 npm

Not in CISA KEV

MEDIUM severity

Backstage has improper authorization in GitLab organizational user ingestionGHSA-gp6m-x9vw-5c5x

MEDIUMFix: backstage/backstage@c211b4b

GHSA-gp6m-x9vw-5c5x is a medium-severity (CVSS 5.4) CWE-863 vulnerability in @backstage/plugin-catalog-backend-module-gitlab. A fix is available for @backstage/plugin-catalog-backend-module-gitlab — see the affected versions and patch details below.

Also known asCVE-2026-106463

Published

Oct 7, 2026

Updated

Oct 7, 2026

Affected

1 pkg

Patched

1 / 1

Exploits

None indexed

Exploitation data as of Oct 22, 2026 · OSV.dev, NVD, FIRST.org (EPSS)

Exploitation Status

No confirmed exploitation observed yet

CISA’s own triage has not observed active exploitation or public proof-of-concept code for this CVE as of its last assessment.

Exploitation and automatability from CISA’s SSVC triage for GHSA-gp6m-x9vw-5c5x.

EPSS Exploitation Probability

via FIRST.org ↗

0.2%probability of exploitation in next 30 days

Lower Risk0.00%

Lower risk than most CVEs6th percentile — riskier than 6% of all scored CVEsHighest risk

Probability of exploitation in the next 30 days, from FIRST.org EPSS.

How urgent is this, really

GHSA-gp6m-x9vw-5c5x by exploitation likelihood (EPSS) against impact (CVSS). Outside the shaded patch-first corner.

Where this sits among everything scored

Of 394,803 CVEs with a current EPSS score, this one falls in the < 10% band (highlighted). Counts from FIRST.org, log-scaled.

Real-World Exposure

1 pkg affected

📦@backstage/plugin-catalog-backend-module-gitlab

Real-time download stats are indexed for npm and PyPI packages. This vulnerability affects npm packages — download data is not available via public APIs for these ecosystems.

Description

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 Packages

1 total 1 fixed

Ecosystem	Package	Vulnerable range	Fix
📦npm	`@backstage/plugin-catalog-backend-module-gitlab`	all versions	0.8.7`npm install @backstage/plugin-catalog-backend-module-gitlab@0.8.7`

Affected Products

2 products · 2 configurations

Application

backstagelinuxfoundation

< 1.54.6

range

Application

backstage\/plugin-catalog-backend-module-gitlablinuxfoundation

< 0.8.7

range

Detection & mitigation playbook

Open-source dependency

Detect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for @backstage/plugin-catalog-backend-module-gitlab, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update @backstage/plugin-catalog-backend-module-gitlab to 0.8.7 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-gp6m-x9vw-5c5x is resolved across your whole dependency graph.
Workarounds
Put an independent control in front of the weakness: restrict the affected endpoint or interface to trusted networks, require an additional authentication factor or proxy-level check, and invalidate existing sessions and credentials in case the flaw has already been used.

Frequently Asked Questions

### 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

O3 Security · Impact-Aware SCA

Is GHSA-gp6m-x9vw-5c5x in your dependencies?

Find it across npm, including transitive dependencies.

Scan my dependencies How O3 SCA works

CVSS Score

5.4/10CVSS v3 base

Vector breakdown

Attack Vector

Network

Attack Complexity

Low

Privileges Required

Low

User Interaction

None

Scope

Unchanged

Confidentiality

Low

Integrity

Low

Availability

None

Raw vector

CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:L/A:N

CWE Classification

CWE-863CWE-863

Weaponization

No known public exploit tooling found.

OpenSSF Scorecard

Package health score

backstage

6.5/10

Dependency-Update-Tool10/10

Maintained10/10

Code-Review10/10

Branch-Protection8/10

Vulnerabilities0/10

Assessed Oct 22, 2026

Timeline

Disclosed

Oct 7, 2026

Identifiers

GHSA-gp6m-x9vw-5c5x

References

Advisorynvd.nist.gov Webgithub.com Webgithub.com Webgithub.com Packagegithub.com

Related vulnerabilities

This CVE is medium severity; 8 of 8 other CVEs with CWE-863 are rated as high or higher (top: critical).

CVE-2026-77362CVE-2026-115883CVE-2026-115477CVE-2026-77366CVE-2026-77361GHSA-cxf3-9h37-7rr8GHSA-mhf7-xp6r-6qrcCVE-2026-73049Browse all CWE-863

Provenance

Sources

OSV.devNVDFIRST.org (EPSS)

Last verifiedOct 7, 2026