/

CVE-2026-88064

Severity:

HIGH RISK

(8.8)

Improper Input Validation (CWE-20) in Backstage TechDocs

CVE-2026-88064

Analyzed

Vulnerability type

Category:

Improper Input Validation

CWE:

CWE-20, CWE-1336

Impact:

Unintended Code Execution

Severity:

HIGH RISK

(8.8)

CVSS version:

3.1

Catch this CVE while code is being written

Detect vulnerable code directly in pull requests, so CVEs are fixed before merge.

Summary

Backstage TechDocs insufficiently validates user-controlled mkdocs.yml configuration before passing it to the documentation generator. An authenticated user who can register or modify a TechDocs source may cause unintended code execution, limited by the permissions and resources available to the TechDocs backend or build container.

Affected context

The vulnerability occurs in Backstage deployments using the @backstage/plugin-techdocs-node package when authenticated users can register or modify TechDocs sources. Risk is present when configuration values such as YAML tags, Markdown extensions, theme options, or extra templates are accepted without sufficiently restrictive validation before documentation generation.

Exploit preconditions

  • Attack surface: TechDocs source registration or modification and the associated documentation build process
  • Required access: Authenticated access with permission to register or modify a TechDocs source
  • Trigger point: Processing of the supplied mkdocs.yml by the TechDocs documentation generator
  • Why exploitation is possible: Several configuration fields can influence parser, extension, theme, or template behavior without adequate validation, allowing supplied configuration to reach execution-sensitive processing paths

Why this happens

The underlying issue is insufficient validation of configuration data that is treated as trusted by the TechDocs generator. Values controlling YAML parsing, Markdown extensions, themes, and templates are not constrained to an appropriately safe schema or allowlist before processing.

This maps primarily to CWE-20: Improper Input Validation. The behavior also relates to CWE-1336: Improper Neutralization of Special Elements Used in a Template Engine, because user-controlled template-related configuration can influence processing in ways that may cause unintended code execution.

Potential impact

  • The TechDocs backend or build container may execute unintended code
  • Application credentials accessible to the affected process could be exposed
  • Files available to the backend or container may be read, modified, or deleted
  • Network-accessible services may be contacted from the compromised execution context
  • Documentation build integrity or downstream development workflows could be affected

General mitigation guidance

Mitigation generally focuses on reducing trust in user-supplied documentation configuration and limiting the privileges of the documentation generation environment.

Common defensive patterns include:

  • Enforcing a strict schema and allowlist for YAML tags, extensions, theme options, and template-related values
  • Using safe YAML parsing behavior that does not construct arbitrary objects
  • Rejecting unsupported or execution-sensitive configuration before invoking the documentation generator
  • Separating user-controlled documentation builds from sensitive backend services and credentials
  • Running build containers with least privilege, restricted filesystem access, and constrained network permissions
  • Treating generated documentation and source configuration as untrusted artifacts

How teams detect issues like this

Detection approaches can include:

  • Static analysis rules for unsafe YAML loading and dynamic configuration evaluation
  • Code review checks for user-controlled values reaching Markdown extensions, themes, templates, or generator plugins
  • Schema-validation tests covering every configurable mkdocs.yml field
  • Runtime monitoring for unexpected child processes, filesystem access, or outbound connections from TechDocs workers
  • Policy enforcement that restricts documentation build containers from accessing unnecessary credentials and network resources
  • Automated security review tools that flag configuration values crossing trust boundaries without validation

Sources

SourceLink
github.comgithub.com/backstage/backstage/commit/017ace52d9b327ededc6704cf17799c875ae0f29
github.comgithub.com/backstage/backstage/commit/02cd7cdbb18b687446277b5602adaee7f1d53cbb
github.comgithub.com/backstage/backstage/commit/25125ee727a3de3418a8fa6a9e458cd5b73ecf26
github.comgithub.com/backstage/backstage/commit/a7d995f11a5d27f0efbdbe8bb6c21b06988c79c9
github.comgithub.com/backstage/backstage/commit/a900a9953c8f7ad3ba1906d1d257725a9996cc9d
github.comgithub.com/backstage/backstage/releases/tag/v1.50.5
github.comgithub.com/backstage/backstage/releases/tag/v1.54.6
github.comgithub.com/backstage/backstage/security/advisories/GHSA-292q-8mf5-h6g3

Frequently asked

questions

An authenticated user generally needs permission to register or modify a TechDocs source. The practical scope depends on Backstage authorization and how documentation builds are isolated.

Not typically. Exploitation requires access to a configuration-management path exposed by TechDocs, although weak authorization or trusted automation could broaden the affected user population.

Validate mkdocs.yml against a strict, allowlisted schema and use safe parsing and rendering behaviors that prevent user-controlled configuration from selecting execution-capable features.

Treat documentation configuration as untrusted input, test all generator options at trust boundaries, and run TechDocs builds with minimal filesystem, credential, and network privileges.

Find out what's already
exploitable in your codebase.