CVE-2026-106505
Description
A flaw was found in the plugin-techdocs-node component of Backstage. This vulnerability allows an attacker with permission to commit changes to a repository utilizing TechDocs to bypass the MkDocs configuration sanitizer. By supplying a crafted configuration file, the attacker can achieve arbitrary code execution on the backend host during documentation generation.
Statement
This vulnerability is rated as Moderate because successful exploitation requires authenticated access and commit permissions to integrated documentation repositories, limiting the threat scope to authorized users. In affected Red Hat Developer Hub and Ansible Automation Platform environments where documentation generation is handled directly by the portal backend, an untrusted configuration file can evade filtering controls. Although command execution occurs on the underlying service host, the prerequisite of write privileges on documentation branches mitigates widespread, unauthenticated exposure.
Mitigation
Mitigation for this issue is either not available or the currently available options do not meet the Red Hat Product Security criteria comprising ease of use and deployment, applicability to widespread installation base, or stability.
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.3 | 8.5 | 7.7 |
| Attack Vector | Network | Network | Network |
| Attack Complexity | Low | High | High |
| Privileges Required | Low | Low | Low |
| User Interaction | None | None | None |
| Scope | Unchanged | Changed | Changed |
| Confidentiality | Low | High | High |
| Integrity Impact | Low | High | Low |
| Availability Impact | Low | High | Low |
Vector
Red Hat: CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:L/A:L
NVD: CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:C/C:H/I:H/A:H
cve.org: CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:C/C:H/I:L/A:L
Understanding the Weakness (CWE)
Access Control
Technical Impact: Bypass Protection Mechanism
In some cases, injectable code controls authentication; this may lead to a remote vulnerability.
Access Control
Technical Impact: Gain Privileges or Assume Identity
Injected code can access resources that the attacker is directly prevented from accessing.
Integrity,Confidentiality,Availability
Technical Impact: Execute Unauthorized Code or Commands
When a product allows a user's input to contain code syntax, it might be possible for an attacker to craft the code in such a way that it will alter the intended control flow of the product. As a result, code injection can often result in the execution of arbitrary code. Code injection attacks can also lead to loss of data integrity in nearly all cases, since the control-plane data injected is always incidental to data recall or writing.
Non-Repudiation
Technical Impact: Hide Activities
Often the actions performed by injected control code are unlogged.
Frequently Asked Questions
Not sure what something means? Check out our Security Glossary.
Want to get errata notifications? Sign up here.
