External risk intelligence

Backstage TechDocs Node RCE via MkDocs Hooks

CVE advisorySeverity: CRITICAL (CVSS 9.1)

CVE-2026-25153

The vulnerability exists within a build-time component (TechDocs) of a developer portal framework. Exploitation requires the ability to modify repository configuration files processed by the build server. While the platform may be network-accessible, the attack surface is limited to users with write access to documentation repositories, making public internet-facing exploitation an uncommon deployment scenario.

Code Injection

Linuxfoundation Backstage\/plugin Techdocs Node

before 1.13.111.14.0 to before 1.14.1

Halo Surface Signal: 2 out of 5 — less likely to be public-facing.

External exposure likelihood

Horizon Alert

Summary of the vulnerability and why it matters

This advisory addresses a vulnerability in the Backstage developer portal's TechDocs component, specifically affecting how it processes documentation configuration. If not properly configured, an attacker with the ability to modify certain configuration files could execute arbitrary code on the build server. The main concern is confirming relevance and exposure, as exploitation requires specific access.

  • Code execution risk in documentation builds.
  • Matters for secure developer portal operations.
  • Confirm relevance and exposure for internal systems.

Attack Path

How an attacker could exploit the issue

An attacker with the ability to modify a repository's `mkdocs.yml` file can execute arbitrary Python code on the TechDocs build server. This occurs when TechDocs is configured to run locally, allowing malicious Python code embedded in MkDocs hooks to be run.

  • Attacker modifies repository configuration.
  • Malicious code executes via MkDocs hooks.
  • Arbitrary code execution on build server.

Live Threat

Current exploitation, exposure, and threat context

When TechDocs is configured to run locally, a malicious actor who can submit or modify a repository's `mkdocs.yml` file could execute arbitrary Python code on the TechDocs build server. This could affect the integrity and availability of the build server.

  • Build server code execution.
  • Malicious `mkdocs.yml` submitted.
  • Compromised build server.

Operational Fix

Recommended remediation, mitigation, and detection steps

The `@backstage/plugin-techdocs-node` component, used for building developer documentation, is vulnerable when configured to run locally. Teams responsible for the Backstage platform and the individual application or service repositories that TechDocs processes should prioritize this. The immediate first step is to identify all instances of TechDocs running in local mode, confirm their exposure and criticality, and locate the accountable owners before planning remediation.

  • Platform and application owners should own.
  • Verify local run mode and repository write access.
  • Plan upgrade or isolate the build environment.

Supplementary metadata

Validate whether this threat affects your internet-facing exposure.

Halo Threat Intelligence helps prioritize remediation with Halo Surface Signal and H/A/L/O context. Start exposure validation with a free external attack surface trial.

Frequently asked questions

What is the Backstage plugin-techdocs-node component?

It is a specialized module for Backstage, an open-source framework used by engineering teams to build centralized developer portals. This specific component handles the backend logic for TechDocs, a service that converts documentation files—like those written in Markdown—into accessible web pages. It manages the build process that transforms repository documentation into your portal's readable format.

What does CWE-94 mean for CVE-2026-25153?

CWE-94 refers to improper control of generation of code, often called Code Injection. In this vulnerability, the system incorrectly processes configuration files without sufficient validation. This flaw allows an attacker to inject and execute their own arbitrary Python code directly on the server responsible for building your documentation, rather than just performing the intended document generation tasks.

How can an attacker trigger this vulnerability?

An attacker needs to gain the ability to submit or modify the mkdocs.yml configuration file within a documentation repository that your TechDocs instance processes. If the system is set to run in 'local' mode, it will execute the settings defined in that file, including unauthorized hooks that trigger the malicious code. The bug is not triggered if TechDocs is not configured to run in local mode or if the attacker lacks write access to those specific configuration files.

Is my organization at risk according to Halo Surface Signal?

Halo Surface Signal indicates that exploitation is unlikely for most public-facing systems. Because this component operates during the documentation build phase rather than as a public web service, the attack surface is restricted. The primary risk exists for organizations where unauthorized users already have write access to the documentation repositories that the build server processes.

What are the first steps to secure my TechDocs setup?

Start by identifying all instances where TechDocs is configured to run in local mode. If possible, transition these to containerized environments like 'docker' for better isolation. Simultaneously, verify your repository permissions to ensure only trusted contributors can modify mkdocs.yml files. Finally, plan to upgrade the @backstage/plugin-techdocs-node package to the fixed versions to enable the new safety filters for configuration keys.

References