How severe is GHSA-p75x-jh7p-ppcx?

GHSA-p75x-jh7p-ppcx has a CVSS score of 7.7/10, rated HIGH. Immediate patching is strongly recommended.

Which packages are affected by GHSA-p75x-jh7p-ppcx?

GHSA-p75x-jh7p-ppcx affects the following packages: @backstage/plugin-techdocs-node (npm). Ecosystems affected: npm.

How do I fix GHSA-p75x-jh7p-ppcx?

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

How do I detect GHSA-p75x-jh7p-ppcx 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-p75x-jh7p-ppcx 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-p75x-jh7p-ppcx actively exploited in the wild?

No public exploit code has been indexed for GHSA-p75x-jh7p-ppcx 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-p75x-jh7p-ppcx?

GHSA-p75x-jh7p-ppcx has an EPSS (Exploit Prediction Scoring System) score of 0.3%, placing it in the 22th 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-p75x-jh7p-ppcx?

GHSA-p75x-jh7p-ppcx is classified as CWE-426 (CWE-426), CWE-436 (CWE-436). These weakness types describe the underlying flaw category, which helps determine the potential impact and the right class of mitigation.

When was GHSA-p75x-jh7p-ppcx published, and has it been updated?

GHSA-p75x-jh7p-ppcx 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

HIGH severity

Backstage: Bypass of MkDocs configuration sanitizer in TechDocs backendGHSA-p75x-jh7p-ppcx

HIGHFix: backstage/backstage@a7d995f

GHSA-p75x-jh7p-ppcx is a high-severity (CVSS 7.7) CWE-426 vulnerability in @backstage/plugin-techdocs-node. A fix is available for @backstage/plugin-techdocs-node — see the affected versions and patch details below.

Also known asCVE-2026-106505

Published

Oct 7, 2026

Updated

Oct 7, 2026

Affected

1 pkg

Patched

1 / 1

Exploits

None indexed

Exploitation data as of Oct 10, 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-p75x-jh7p-ppcx.

EPSS Exploitation Probability

via FIRST.org ↗

0.3%probability of exploitation in next 30 days

Lower Risk0.00%

Lower risk than most CVEs22th percentile — riskier than 22% of all scored CVEsHighest risk

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

How urgent is this, really

GHSA-p75x-jh7p-ppcx by exploitation likelihood (EPSS) against impact (CVSS). Outside the shaded patch-first corner.

Where this sits among everything scored

Of 385,386 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.

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

@backstage/plugin-techdocs-nodenpm

200Kdownloads / week

Description

Impact

Users with the ability to commit changes to a repository that uses TechDocs can circumvent the MkDocs configuration file sanitizer introduced in response to CVE-2026-25153 and execute arbitrary code on the TechDocs backend host during documentation generation.

Patches

Patched in@backstage/plugin-techdocs-node version 1.15.4

Workarounds

If you cannot upgrade immediately:

Use Docker mode with restricted access: Configure TechDocs with runIn: docker instead of runIn: local. This provides container isolation, though it does not fully mitigate the risk.
Limit repository write access to trusted parties, since exploitation requires the ability to commit files to a repository with TechDocs enabled.
Review incoming changes to MkDocs configuration files as part of your code review process.

Affected Packages

1 total 1 fixed

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

Affected Products

2 products · 9 configurations

Application

backstagelinuxfoundation

≥ 1.51.1 && < 1.54.6

1 version

1.51.0

Application

backstage plugin-techdocs-nodelinuxfoundation

≥ 1.15.0 && < 1.15.4

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-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.15.4 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-p75x-jh7p-ppcx 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.

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

This vulnerability is rated as Moderate because successful exploitation requires authenticated access and commit permissions to integrated documentation repositories, limiting the threat scope to authorized users. In affected Red Hat Developer Hub and Ansible Automation Platform environments where documentation…

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-p75x-jh7p-ppcx (CC BY 4.0)

Frequently Asked Questions

### Impact Users with the ability to commit changes to a repository that uses TechDocs can circumvent the MkDocs configuration file sanitizer introduced in response to CVE-2026-25153 and execute arbitrary code on the TechDocs backend host during documentation generation. ### Patches Patched in`@backstage/plugin-techdocs-node` version `1.15.4` ### Workarounds If you cannot upgrade immediately: - Use Docker mode with restricted access: Configure TechDocs with `runIn: docker` instead of `runIn: local`. This provides container isolation, though it does not fully mitigate the risk. - Limit re