How severe is GHSA-8wq8-6859-qx77?

GHSA-8wq8-6859-qx77 has a CVSS score of 4.4/10, rated MEDIUM. Review your exposure and patch according to your risk tolerance.

Which packages are affected by GHSA-8wq8-6859-qx77?

GHSA-8wq8-6859-qx77 affects the following packages: @backstage/plugin-scaffolder-backend (npm). Ecosystems affected: npm.

How do I fix GHSA-8wq8-6859-qx77?

Update @backstage/plugin-scaffolder-backend to 3.1.5 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-8wq8-6859-qx77 is resolved across your whole dependency graph.

How do I detect GHSA-8wq8-6859-qx77 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-8wq8-6859-qx77 if there is no patch (or I can't update yet)?

Assume what was exposed is already known: rotate any credential, token or key that the affected component could return, restrict the endpoint to callers that genuinely need it, and strip sensitive fields from responses and error output at the boundary rather than relying on the client not to read them.

Is GHSA-8wq8-6859-qx77 actively exploited in the wild?

No public exploit code has been indexed for GHSA-8wq8-6859-qx77 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-8wq8-6859-qx77?

GHSA-8wq8-6859-qx77 has an EPSS (Exploit Prediction Scoring System) score of 0.3%, placing it in the 21th 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-8wq8-6859-qx77?

GHSA-8wq8-6859-qx77 is classified as Information Exposure (CWE-200). This weakness type describe the underlying flaw category, which helps determine the potential impact and the right class of mitigation.

When was GHSA-8wq8-6859-qx77 published, and has it been updated?

GHSA-8wq8-6859-qx77 was published on March 12, 2026 and was last updated on March 14, 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/plugin-scaffolder-backend: Possible exposure of defaultEnvironment secrets using dry-run endpointGHSA-8wq8-6859-qx77

MEDIUMFix: backstage/backstage@3b62dd2

GHSA-8wq8-6859-qx77 is a medium-severity (CVSS 4.4) Information Exposure 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-32237

Published

Mar 12, 2026

Updated

Mar 14, 2026

Affected

1 pkg

Patched

1 / 1

Exploits

None indexed

Exploitation data as of Nov 7, 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-8wq8-6859-qx77.

EPSS Exploitation Probability

via FIRST.org ↗

0.3%probability of exploitation in next 30 days

Lower Risk+0.03%

Lower risk than most CVEs21th percentile — riskier than 21% of all scored CVEsHighest risk

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

How urgent is this, really

Where this sits among everything scored

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

217Kdownloads / week

Description

Impact

Authenticated users with permission to execute scaffolder dry-runs can gain access to server-configured environment secrets through the dry-run API response. Secrets are properly redacted in log output but not in all parts of the response payload.

Deployments that have configured scaffolder.defaultEnvironment.secrets are affected.

Patches

This is patched in @backstage/plugin-scaffolder-backend version 3.1.5

Workarounds

Remove or empty the scaffolder.defaultEnvironment.secrets configuration from app-config.yaml. Alternatively, restrict access to the scaffolder dry-run functionality via the permissions framework.

References

Backstage Scaffolder Backend documentation

Affected Packages

1 total 1 fixed

Ecosystem	Package	Vulnerable range	Fix
📦npm	`@backstage/plugin-scaffolder-backend`	≥ 3.1.0&&< 3.1.5	3.1.5`npm install @backstage/plugin-scaffolder-backend@3.1.5`

Affected Products

1 product · 1 configurations

Application

backstage\/plugin-scaffolder-backendlinuxfoundation

≥ 3.1.0 && < 3.1.5

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 3.1.5 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-8wq8-6859-qx77 is resolved across your whole dependency graph.
Workarounds
Assume what was exposed is already known: rotate any credential, token or key that the affected component could return, restrict the endpoint to callers that genuinely need it, and strip sensitive fields from responses and error output at the boundary rather than relying on the client not to read them.

Fixing This On Your OS

If you run this on a Linux distribution, patch through your package manager against the distro's own security advisory below — it tracks the exact backported fix for your release, which can ship on a different timeline (and sometimes a different severity) than the upstream project.

Red HatModerate

Workaround published by Red Hat

Mitigation for this issue is either not available or the currently available options do not meet the Red Hat Product Security criteria comprising ease of use and deployment, applicability to widespread installation base or stability.

Source: Red Hat security advisory for GHSA-8wq8-6859-qx77 (CC BY 4.0)

Frequently Asked Questions

### Impact Authenticated users with permission to execute scaffolder dry-runs can gain access to server-configured environment secrets through the dry-run API response. Secrets are properly redacted in log output but not in all parts of the response payload.