How severe is GHSA-4jqc-jvh2-pxg9?

No CVSS score has been assigned to GHSA-4jqc-jvh2-pxg9 yet. Review the advisory details and affected package list to assess your exposure.

Which packages are affected by GHSA-4jqc-jvh2-pxg9?

GHSA-4jqc-jvh2-pxg9 affects the following packages: @backstage/plugin-techdocs-node (npm), @backstage/techdocs-common (npm). Ecosystems affected: npm.

How do I fix GHSA-4jqc-jvh2-pxg9?

Update @backstage/plugin-techdocs-node to 1.1.2 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-4jqc-jvh2-pxg9 is resolved across your whole dependency graph.

How do I detect GHSA-4jqc-jvh2-pxg9 in my npm dependencies?

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

How do I mitigate GHSA-4jqc-jvh2-pxg9 if there is no patch (or I can't update yet)?

If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.

Is GHSA-4jqc-jvh2-pxg9 actively exploited in the wild?

No public exploit code has been indexed for GHSA-4jqc-jvh2-pxg9 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.

When was GHSA-4jqc-jvh2-pxg9 published, and has it been updated?

GHSA-4jqc-jvh2-pxg9 was published on June 17, 2022. 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

Path traversal for local publishers in TechDocs backendGHSA-4jqc-jvh2-pxg9

Fix: backstage/backstage@429c9f9

GHSA-4jqc-jvh2-pxg9 is a security vulnerability in @backstage/plugin-techdocs-node. A fix is available for @backstage/plugin-techdocs-node — see the affected versions and patch details below.

Published

Jun 17, 2022

Updated

Jun 17, 2022

Affected

2 pkgs

Patched

2 / 2

Exploits

None indexed

Exploitation data as of Jun 17, 2022 · OSV.dev, FIRST.org (EPSS)

Real-World Exposure

2 pkgs 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.

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

@backstage/plugin-techdocs-nodenpm

288Kdownloads / week

@backstage/techdocs-commonnpm

1Kdownloads / week

Description

Impact

A malicious actor with the ability to register entities in the Software Catalog is able to write files to arbitrary paths on the techdocs backend host instance when techdocs.publisher.type is set to local.

This vulnerability is mitigated by the fact that the Software Catalog must be configured with non-standard field format validators and/or non-standard entity policies.

Patches

Those affected are advised to upgrade to @backstage/plugin-techdocs-node version 1.1.2 or higher.

Workarounds

If patching or upgrading is not possible, it would be sufficient to update any custom Catalog field format validators and/or custom entity policies to disallow entity names, kinds, and namespaces containing ..

For more information

If you have any questions or comments about this advisory:

Open an issue in the Backstage repository
Visit our chat, linked to in the Backstage README

Affected Packages

2 total 2 fixed

Ecosystem	Package	Vulnerable range	Fix
📦npm	`@backstage/plugin-techdocs-node`	all versions	1.1.2`npm install @backstage/plugin-techdocs-node@1.1.2`
📦npm	`@backstage/techdocs-common`	all versions	0.11.16`npm install @backstage/techdocs-common@0.11.16`

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-techdocs-node, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update @backstage/plugin-techdocs-node to 1.1.2 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-4jqc-jvh2-pxg9 is resolved across your whole dependency graph.
Workarounds
If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.

Frequently Asked Questions

### Impact A malicious actor with the ability to register entities in the Software Catalog is able to write files to arbitrary paths on the techdocs backend host instance when `techdocs.publisher.type` is set to `local`. This vulnerability is mitigated by the fact that the Software Catalog must be configured with non-standard field format validators and/or non-standard entity policies. ### Patches Those affected are advised to upgrade to `@backstage/plugin-techdocs-node` version `1.1.2` or higher. ### Workarounds If patching or upgrading is not possible, it would be sufficient to update any

O3 Security · Impact-Aware SCA

Is GHSA-4jqc-jvh2-pxg9 in your dependencies?

Find it across npm, including transitive dependencies.

Scan my dependencies How O3 SCA works