How severe is GHSA-xvh9-35w9-42m4?

GHSA-xvh9-35w9-42m4 has a CVSS score of 3/10, rated LOW. Review your exposure and patch according to your risk tolerance.

Which packages are affected by GHSA-xvh9-35w9-42m4?

GHSA-xvh9-35w9-42m4 affects the following packages: @backstage/plugin-catalog-backend-module-azure (npm), @backstage/plugin-catalog-backend-module-aws (npm), @backstage/backend-defaults (npm). Ecosystems affected: npm.

How do I fix GHSA-xvh9-35w9-42m4?

Update @backstage/plugin-catalog-backend-module-azure to 0.3.21 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-xvh9-35w9-42m4 is resolved across your whole dependency graph.

How do I detect GHSA-xvh9-35w9-42m4 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-azure, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.

How do I mitigate GHSA-xvh9-35w9-42m4 if there is no patch (or I can't update yet)?

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.

Is GHSA-xvh9-35w9-42m4 actively exploited in the wild?

No public exploit code has been indexed for GHSA-xvh9-35w9-42m4 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-xvh9-35w9-42m4?

GHSA-xvh9-35w9-42m4 has an EPSS (Exploit Prediction Scoring System) score of 0.3%, placing it in the 17th 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-xvh9-35w9-42m4?

GHSA-xvh9-35w9-42m4 is classified as Path Traversal (CWE-22). This weakness type describe the underlying flaw category, which helps determine the potential impact and the right class of mitigation. This is a high-impact weakness class that often enables remote code execution or data exposure.

When was GHSA-xvh9-35w9-42m4 published, and has it been updated?

GHSA-xvh9-35w9-42m4 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

LOW severity

Backstage: Cloud storage catalog locations may cross configured storage boundariesGHSA-xvh9-35w9-42m4

LOWFix: backstage/backstage@47ddbd8

GHSA-xvh9-35w9-42m4 is a low-severity (CVSS 3) Path Traversal vulnerability in @backstage/plugin-catalog-backend-module-azure. A fix is available for @backstage/plugin-catalog-backend-module-azure — see the affected versions and patch details below.

Also known asCVE-2026-106493

Published

Oct 7, 2026

Updated

Oct 7, 2026

Affected

3 pkgs

Patched

3 / 3

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-xvh9-35w9-42m4.

EPSS Exploitation Probability

via FIRST.org ↗

0.3%probability of exploitation in next 30 days

Lower Risk0.00%

Lower risk than most CVEs17th percentile — riskier than 17% of all scored CVEsHighest risk

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

How urgent is this, really

GHSA-xvh9-35w9-42m4 by exploitation likelihood (EPSS) against impact (CVSS). Outside the shaded patch-first corner.

Where this sits among everything scored

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

Real-World Exposure

3 pkgs affected

📦@backstage/plugin-catalog-backend-module-azure📦@backstage/plugin-catalog-backend-module-aws📦@backstage/backend-defaults

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

Catalog entity providers for Azure Blob Storage and AWS S3 did not sufficiently validate storage object paths, which could allow catalog descriptors to be read from outside the intended storage boundary. Access is limited to locations reachable by the backend's configured credentials.

Patches

@backstage/plugin-catalog-backend-module-azure version 0.3.21
@backstage/plugin-catalog-backend-module-aws version 0.4.27
@backstage/backend-defaults version 0.7.18

Workarounds

Restrict blob and object creation or renaming in configured catalog storage sources to trusted principals.
Scope Backstage's Azure and AWS reader credentials and network access to the intended storage boundaries.
Disable an affected catalog provider if those restrictions cannot be enforced.

Affected Packages

3 total 3 fixed

Ecosystem	Package	Vulnerable range	Fix
📦npm	`@backstage/plugin-catalog-backend-module-azure`	all versions	0.3.21`npm install @backstage/plugin-catalog-backend-module-azure@0.3.21`
📦npm	`@backstage/plugin-catalog-backend-module-aws`	all versions	0.4.27`npm install @backstage/plugin-catalog-backend-module-aws@0.4.27`
📦npm	`@backstage/backend-defaults`	all versions	0.17.8`npm install @backstage/backend-defaults@0.17.8`

Affected Products

4 products · 4 configurations

Application

backstagelinuxfoundation

< 1.54.6

range

Application

backstage\/backend-defaultslinuxfoundation

< 0.17.8

range

Application

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

< 0.4.27

range

Application

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

< 0.3.21

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-azure, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update @backstage/plugin-catalog-backend-module-azure to 0.3.21 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-xvh9-35w9-42m4 is resolved across your whole dependency graph.
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 Catalog entity providers for Azure Blob Storage and AWS S3 did not sufficiently validate storage object paths, which could allow catalog descriptors to be read from outside the intended storage boundary. Access is limited to locations reachable by the backend's configured credentials. ### Patches - `@backstage/plugin-catalog-backend-module-azure` version `0.3.21` - `@backstage/plugin-catalog-backend-module-aws` version `0.4.27` - `@backstage/backend-defaults` version `0.7.18` ### Workarounds - Restrict blob and object creation or renaming in configured catalog storage sources t