How severe is GHSA-7hfw-grcm-cqm6?

GHSA-7hfw-grcm-cqm6 has a CVSS score of 4.3/10, rated MEDIUM. Review your exposure and patch according to your risk tolerance.

Which packages are affected by GHSA-7hfw-grcm-cqm6?

GHSA-7hfw-grcm-cqm6 affects the following packages: @backstage/plugin-scaffolder-backend (npm). Ecosystems affected: npm.

How do I fix GHSA-7hfw-grcm-cqm6?

Update @backstage/plugin-scaffolder-backend to 4.1.0 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-7hfw-grcm-cqm6 is resolved across your whole dependency graph.

How do I detect GHSA-7hfw-grcm-cqm6 in my npm dependencies?

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

How do I mitigate GHSA-7hfw-grcm-cqm6 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-7hfw-grcm-cqm6 actively exploited in the wild?

No public exploit code has been indexed for GHSA-7hfw-grcm-cqm6 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-7hfw-grcm-cqm6?

GHSA-7hfw-grcm-cqm6 has an EPSS (Exploit Prediction Scoring System) score of 0.2%, placing it in the 8th 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-7hfw-grcm-cqm6?

GHSA-7hfw-grcm-cqm6 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-7hfw-grcm-cqm6 published, and has it been updated?

GHSA-7hfw-grcm-cqm6 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: Incorrect authorization in scaffolder task listingGHSA-7hfw-grcm-cqm6

MEDIUMFix: backstage/backstage@0253c50

GHSA-7hfw-grcm-cqm6 is a medium-severity (CVSS 4.3) CWE-863 vulnerability in @backstage/plugin-scaffolder-backend. A fix is available for @backstage/plugin-scaffolder-backend — see the affected versions and patch details below.

Also known asCVE-2026-106461

Published

Oct 7, 2026

Updated

Oct 7, 2026

Affected

1 pkg

Patched

1 / 1

Exploits

None indexed

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

EPSS Exploitation Probability

via FIRST.org ↗

0.2%probability of exploitation in next 30 days

Lower Risk0.00%

Lower risk than most CVEs8th percentile — riskier than 8% of all scored CVEsHighest risk

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

How urgent is this, really

GHSA-7hfw-grcm-cqm6 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

How broadly this vulnerability is actually deployed: weekly install volume shows current usage, and reverse-dependency count shows how many other packages break if it stays unpatched.

69other npm packages depend on this — each one inherits the vulnerability until it's patched upstream

@backstage/plugin-scaffolder-backendnpm

68Kdownloads / week

Description

Impact

An authenticated internal user may be able to view metadata for scaffolder tasks outside the visibility intended by a deployment's permission policy. Stored task secrets are not included in the affected response, and no integrity or availability impact was identified.

Patches

Patched in @backstage/plugin-scaffolder-backend version 4.1.0

Workarounds

Restrict the scaffolder task-list endpoint at the ingress or authenticating proxy to users who are permitted to view all tasks.
Avoid placing sensitive values in template input parameters until the patched package is deployed.

Affected Packages

1 total 1 fixed

Ecosystem	Package	Vulnerable range	Fix
📦npm	`@backstage/plugin-scaffolder-backend`	all versions	4.1.0`npm install @backstage/plugin-scaffolder-backend@4.1.0`

Affected Products

2 products · 2 configurations

Application

backstagelinuxfoundation

< 1.54.6

range

Application

backstage\/plugin-scaffolder-backendlinuxfoundation

< 4.1.0

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-scaffolder-backend, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update @backstage/plugin-scaffolder-backend to 4.1.0 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-7hfw-grcm-cqm6 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 An authenticated internal user may be able to view metadata for scaffolder tasks outside the visibility intended by a deployment's permission policy. Stored task secrets are not included in the affected response, and no integrity or availability impact was identified. ### Patches Patched in `@backstage/plugin-scaffolder-backend` version `4.1.0` ### Workarounds - Restrict the scaffolder task-list endpoint at the ingress or authenticating proxy to users who are permitted to view all tasks. - Avoid placing sensitive values in template input parameters until the patched package is

O3 Security · Impact-Aware SCA

Is GHSA-7hfw-grcm-cqm6 in your dependencies?

Find it across npm, including transitive dependencies.

Scan my dependencies How O3 SCA works

CVSS Score

4.3/10CVSS v3 base

Vector breakdown

Attack Vector

Network

Attack Complexity

Low

Privileges Required

Low

User Interaction

None

Scope

Unchanged

Confidentiality

Low

Integrity

None

Availability

None

Raw vector

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

CWE Classification

CWE-863CWE-863

Weaponization

No known public exploit tooling found.

OpenSSF Scorecard

Package health score

backstage

6.5/10

Maintained10/10

Dependency-Update-Tool10/10

Code-Review10/10

Vulnerabilities0/10

Branch-Protection8/10

Assessed Oct 23, 2026

Timeline

Disclosed

Oct 7, 2026

Identifiers

GHSA-7hfw-grcm-cqm6

References

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

Related vulnerabilities

This CVE is medium severity; 8 of 8 other CVEs affecting @backstage/plugin-scaffolder-backend are rated as high or higher (top: critical).

CVE-2026-106462CVE-2026-106504CVE-2026-106461CVE-2026-106502CVE-2026-106501CVE-2026-106503CVE-2026-106499CVE-2026-106506

Provenance

Sources

OSV.devNVDFIRST.org (EPSS)

Last verifiedOct 7, 2026