Your RSA-2048 keys break in 2030. Find every one of them before attackers do.
📦
📦 npm
Not in CISA KEV
HIGH severity

Backstage: Improper repository path validation in a Scaffolder backend moduleGHSA-2cmg-v53w-8xfp

HIGHFix: backstage/backstage@5f0000c

GHSA-2cmg-v53w-8xfp is a high-severity (CVSS 7.1) Path Traversal vulnerability in @backstage/plugin-scaffolder-backend-module-confluence-to-markdown. A fix is available for @backstage/plugin-scaffolder-backend-module-confluence-to-markdown — see the affected versions and patch details below.

Also known asCVE-2026-106560
Published
Updated
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-2cmg-v53w-8xfp.

EPSS Exploitation Probability

via FIRST.org ↗
0.3%probability of exploitation in next 30 days
Lower Risk0.00%
Lower risk than most CVEs23th percentile — riskier than 23% of all scored CVEsHighest risk

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

How urgent is this, really

GHSA-2cmg-v53w-8xfp 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, a proxy for how much of the ecosystem is exposed.

@backstage/plugin-scaffolder-backend-module-confluence-to-markdownnpm
915downloads / week

Description

Impact

An authenticated user who can execute an affected template and control its repository file location may cause generated content to be written outside the task workspace, within locations writable by the Backstage backend process.

Patches

Patched in @backstage/plugin-scaffolder-backend-module-confluence-to-markdown version 0.3.25

Workarounds

  • Restrict execution of templates using the affected action to trusted users.
  • Remove or disable the affected action until the patched package is deployed.

Affected Packages

1 total 1 fixed
EcosystemPackageVulnerable rangeFix
📦npm@backstage/plugin-scaffolder-backend-module-confluence-to-markdownall versions0.3.25npm install @backstage/plugin-scaffolder-backend-module-confluence-to-markdown@0.3.25

Affected Products

2 products · 2 configurations
Application
backstagelinuxfoundation
< 1.54.6
range
Application
backstage\/plugin-scaffolder-backend-module-confluence-to-markdownlinuxfoundation
< 0.3.25
range

Detection & mitigation playbook

Open-source dependency
  1. Detect

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

  2. Fix

    Update @backstage/plugin-scaffolder-backend-module-confluence-to-markdown to 0.3.25 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-2cmg-v53w-8xfp is resolved across your whole dependency graph.

  3. Workarounds

    Resolve every user-supplied path to its canonical form and reject anything that escapes the intended directory, and run the component under an account that has no read or write access outside the directory it legitimately serves.

Frequently Asked Questions

### Impact An authenticated user who can execute an affected template and control its repository file location may cause generated content to be written outside the task workspace, within locations writable by the Backstage backend process. ### Patches Patched in `@backstage/plugin-scaffolder-backend-module-confluence-to-markdown` version `0.3.25` ### Workarounds - Restrict execution of templates using the affected action to trusted users. - Remove or disable the affected action until the patched package is deployed.
O3 Security · Impact-Aware SCA

Is GHSA-2cmg-v53w-8xfp in your dependencies?

Find it across npm, including transitive dependencies.

Backstage: Improper repository path validation in a…