How severe is CVE-2026-106510?

CVE-2026-106510 has a CVSS score of 7.7/10, rated HIGH. Immediate patching is strongly recommended.

Which packages are affected by CVE-2026-106510?

CVE-2026-106510 affects the following packages: @backstage/plugin-techdocs-node (npm). Ecosystems affected: npm.

How do I fix CVE-2026-106510?

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 CVE-2026-106510 is resolved across your whole dependency graph.

How do I detect CVE-2026-106510 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 CVE-2026-106510 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 CVE-2026-106510 actively exploited in the wild?

No public exploit code has been indexed for CVE-2026-106510 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 CVE-2026-106510?

CVE-2026-106510 has an EPSS (Exploit Prediction Scoring System) score of 0.5%, placing it in the 38th 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 CVE-2026-106510?

CVE-2026-106510 is classified as CWE-183 (CWE-183), CWE-470 (CWE-470). These weakness types describe the underlying flaw category, which helps determine the potential impact and the right class of mitigation.

When was CVE-2026-106510 published, and has it been updated?

CVE-2026-106510 was published on October 7, 2026 and was last updated on October 21, 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

CVE-2026-106510 — @backstage/plugin-techdoc…

HIGHFix: backstage/backstage@02cd7cd

CVE-2026-106510 is a high-severity (CVSS 7.7) CWE-183 vulnerability in @backstage/plugin-techdocs-node. A fix is available for @backstage/plugin-techdocs-node — see the affected versions and patch details below.

Backstage: Remote code execution via crafted markdown_extensions in TechDocs mkdocs.yml

Also known asGHSA-4488-j8vj-vqqv

Published

Oct 7, 2026

Updated

Oct 21, 2026

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 CVE-2026-106510.

EPSS Exploitation Probability

via FIRST.org ↗

0.5%probability of exploitation in next 30 days

Lower Risk0.00%

Lower risk than most CVEs38th percentile — riskier than 38% of all scored CVEsHighest risk

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

How urgent is this, really

CVE-2026-106510 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, 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

99Kdownloads / week

Description

Impact

An authenticated user who can register catalog entities can provide a crafted mkdocs.yml causing arbitrary OS command execution on the TechDocs build host when the docs are built.

Patches

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

Workarounds

If you cannot upgrade immediately:

Switch to techdocs.builder: external to isolate TechDocs builds in a container.
Restrict who can register catalog entities with TechDocs annotations.
Audit existing catalog entities for suspicious markdown_extensions values in their mkdocs.yml files.

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 CVE-2026-106510 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 HatImportant

This vulnerability is rated as Important because authenticated users permitted to register catalog entities can trigger arbitrary system commands on the backend build host. In Red Hat Developer Hub and Ansible Automation Platform environments utilizing in-tree TechDocs generation, an attacker can leverage malicious…

Workaround published by Red Hat

To mitigate this vulnerability, implement the following operational and configuration controls: 1. Isolate documentation builds: Configure TechDocs to delegate builds to an external pipeline rather than executing them locally on the portal host. In `app-config.yaml`, set: ```yaml techdocs: builder: 'external' ``` Warning: Applying configuration changes to `app-config.yaml` requires restarting or redeploying the service to take effect. Delegating to external builders requires generating documentation through external CI/CD pipelines or dedicated build runners. 2. Restrict catalog registration: Restrict catalog registration privileges to authorized administrators through role-based access…

Source: Red Hat security advisory for CVE-2026-106510 (CC BY 4.0)

Frequently Asked Questions

### Impact An authenticated user who can register catalog entities can provide a crafted `mkdocs.yml` causing arbitrary OS command execution on the TechDocs build host when the docs are built. ### Patches Patched in `@backstage/plugin-techdocs-node`, version `1.15.4`. ### Workarounds If you cannot upgrade immediately: - Switch to `techdocs.builder: external` to isolate TechDocs builds in a container. - Restrict who can register catalog entities with TechDocs annotations. - Audit existing catalog entities for suspicious `markdown_extensions` values in their `mkdocs.yml` files.