CVE-2026-106557
Description
A flaw was found in @backstage/plugin-techdocs-node. Improper validation of TechDocs Markdown extension configurations allows an authenticated user who can register or modify documentation sources to access resources outside the intended documentation boundary during build operations. This issue can lead to information disclosure, potentially exposing sensitive backend host data or internal network resources.
Statement
A moderate-impact information disclosure flaw was found in the @backstage/plugin-techdocs-node package, which is shipped in Red Hat Developer Hub and Red Hat Ansible Automation Platform (automation-portal) container images. The package did not sufficiently validate TechDocs Markdown extension configuration. An authenticated user who can register or modify documentation sources can cause a TechDocs build to access resources outside the intended documentation boundary, potentially exposing sensitive backend-host data or internal network resources; the flaw affects confidentiality only, with no impact on integrity or availability. Red Hat rates this flaw MODERATE (CVSS 6.5, CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N), while the upstream Backstage advisory rates it HIGH (CVSS 7.7); the difference is the CVSS scope metric, as Red Hat assesses the impact as confined to the security authority of the TechDocs backend process rather than crossing into other components. The affected Red Hat Developer Hub and Red Hat Ansible Automation Platform streams are tracked as affected with delegated resolution, and a fix is being pursued through the corresponding product maintainers.
Mitigation
Workarounds recommended by the upstream project:
- Generate TechDocs only from trusted repositories with reviewed MkDocs configuration.
- Use isolated TechDocs build environments with restricted filesystem access and network egress.
- Prefer externally generated TechDocs produced in appropriately sandboxed CI.
Note that updating @backstage/plugin-techdocs-node alone does not fully remediate this issue: the upstream fix also requires pymdown-extensions 10.21.3 or later, normally obtained through mkdocs-techdocs-core 1.7.0 or later. For the affected Red Hat products, install fixed packages when they become available through the respective product update channels.
Common Vulnerability Scoring System (CVSS) Score Details
Info alert:Important note
CVSS scores for open source components depend on vendor-specific factors (e.g. version or build chain). Therefore, Red Hat's score and impact rating can be different from NVD and other vendors. Red Hat remains the authoritative CVE Naming Authority (CNA) source for its products and services (see Red Hat classifications).
The following CVSS metrics and score provided are preliminary and subject to review.
CVSS v3 Score Breakdown
| Red Hat | NVD | cve.org | |
|---|---|---|---|
| Base Score | 6.5 | N/A | 7.7 |
| Attack Vector | Network | N/A | Network |
| Attack Complexity | Low | N/A | Low |
| Privileges Required | Low | N/A | Low |
| User Interaction | None | N/A | None |
| Scope | Unchanged | N/A | Changed |
| Confidentiality | High | N/A | High |
| Integrity Impact | None | N/A | None |
| Availability Impact | None | N/A | None |
Vector
Red Hat: CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N
cve.org: CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:N/A:N
Understanding the Weakness (CWE)
Integrity,Confidentiality,Availability
Technical Impact: Execute Unauthorized Code or Commands
The attacker may be able to create or overwrite critical files that are used to execute code, such as programs or libraries.
Integrity
Technical Impact: Modify Files or Directories
The attacker may be able to overwrite or create critical files, such as programs, libraries, or important data. If the targeted file is used for a security mechanism, then the attacker may be able to bypass that mechanism. For example, appending a new account at the end of a password file may allow an attacker to bypass authentication.
Confidentiality
Technical Impact: Read Files or Directories
The attacker may be able to read the contents of unexpected files and expose sensitive data. If the targeted file is used for a security mechanism, then the attacker may be able to bypass that mechanism. For example, by reading a password file, the attacker could conduct brute force password guessing attacks in order to break into an account on the system.
Availability
Technical Impact: DoS: Crash, Exit, or Restart
The attacker may be able to overwrite, delete, or corrupt unexpected critical files such as programs, libraries, or important data. This may prevent the product from working at all and in the case of protection mechanisms such as authentication, it has the potential to lock out product users.
Frequently Asked Questions
Not sure what something means? Check out our Security Glossary.
Want to get errata notifications? Sign up here.
