CVE-2026-106557: @backstage/plugin-techdocs-node Improper Input Validation in TechDocs Markdown Extension

Summary

07/10/2026
Yes i
High
7.7

CVE-2026-106557: Backstage has improper input validation in TechDocs Markdown extension configuration. Affects @backstage/plugin-techdocs-node versions < 1.15.4. Fixed in 1.15.4. How to fix ↓

Free scan

Check if this vulnerability affects your application

Upload a manifest or SBOM and we'll show whether you're affected, plus every other risky package in the same scan.

Check my app free

No signup required · Results in about 60 seconds

Upload your dependency manifest or SBOM

Drag & drop your file here or

Java Javascript PHP Python Go Rust Ruby Dart C/C++ Elixir CycloneDX SPDX

Upload a supported dependency manifest or SBOM. No installation or source-code access required.

See supported files and SBOM formats
SBOM sbom.json · bom.json · bom.xml · *.spdx.json · *.cdx.json · *.cdx.xml
Java pom.xml · gradle.lockfile · buildscript-gradle.lockfile
Javascript package-lock.json · yarn.lock · pnpm-lock.yaml
PHP composer.lock
Python poetry.lock · requirements.txt · Pipfile.lock
Go go.mod
Rust Cargo.lock
Ruby Gemfile.lock
Dart pubspec.lock
C/C++ conan.lock
Elixir mix.lock
Enter your work email to receive your report link.

Verify your email to view the full report and start 30 days of continuous monitoring. No credit card required.

Sponsored Devnack Your last release was probably never penetration tested Manual testing by engineers who build software, not an auditor's checklist. Trusted by teams at Swift and Google Talk to Devnack

Background

The @backstage/plugin-techdocs-node package is a vital component of the Backstage platform, which facilitates the creation and management of technical documentation. It allows users to generate documentation from various sources, enhancing collaboration and knowledge sharing within organizations. However, this package is susceptible to a vulnerability that can lead to unauthorized access to sensitive resources.

Vulnerability Detail

The vulnerability arises from improper input validation in the TechDocs Markdown extension configuration. An authenticated user with the ability to register or modify documentation sources can manipulate a TechDocs build to access resources beyond the intended documentation boundary. This could potentially expose sensitive backend-host data or internal network resources, depending on the deployment configuration.

How To Fix

Latest published version: 2.1.0 as of 23 Oct 2026

npm install @backstage/plugin-techdocs-node@2.1.0

Upgrading to it may include breaking changes; the version below is the minimum fixed release for this vulnerability.

If you need the minimum change

1.15.4

This is the first release that contains the fix.

npm install @backstage/plugin-techdocs-node@1.15.4

Tip — Not sure which version your app runs? Vulert can match this fix to it. Scan free →

Workaround

To mitigate the risk until the patch is applied, consider the following workarounds: 1. Generate TechDocs only from trusted repositories with reviewed MkDocs configurations. 2. Use isolated build environments with restricted filesystem access and network egress. 3. Prefer externally generated TechDocs with appropriately sandboxed CI.

Conclusion

In summary, CVE-2026-106557 is a significant vulnerability in the @backstage/plugin-techdocs-node package that can lead to unauthorized access to sensitive resources. It is crucial for users to update to the patched version and consider the provided workarounds to mitigate risks.

See every vulnerability recorded for @backstage/plugin-techdocs-node →

Share this vulnerability

FAQ

CVE-2026-106557 is a vulnerability in the @backstage/plugin-techdocs-node package that allows unauthorized access to sensitive resources due to improper input validation.

You can use the Vulert playground at Vulert Scanner to check if your application is affected by this vulnerability without requiring any signup.

The CVSS score of this vulnerability is 7.7, indicating a high severity level.

If immediate updates are not possible, implement the suggested workarounds to minimize risk until the patch can be applied.

Exploitation of this vulnerability could lead to exposure of sensitive backend data or internal network resources, posing significant security risks.

Related vulnerabilities

Recent vulnerabilities recorded for @backstage/plugin-techdocs-node.

How To Fix

Latest published version: 2.1.0 as of 23 Oct 2026

npm install @backstage/plugin-techdocs-node@2.1.0

Upgrading to it may include breaking changes; the version below is the minimum fixed release for this vulnerability.

If you need the minimum change

1.15.4

This is the first release that contains the fix.

npm install @backstage/plugin-techdocs-node@1.15.4

Tip — Not sure which version your app runs? Vulert can match this fix to it. Scan free →

Subscribe to Vulert on Telegram
Daily digest of new CVEs, critical and high severity, affected packages and fixes — plus a weekly roundup.
Join the channel →
Help improve this record
Report an issue or send feedback