cve.bz

CVE-2026-106505 linuxfoundation: Untrusted Search Path

8.5 highEPSS 0.3%Fix available

High (8.5) in linuxfoundation. EPSS 0.3% estimated probability of exploitation activity in the next 30 days. Fixed in @backstage/plugin-techdocs-node 1.15.4.

On this page
Backstage is an open framework for building developer portals. Prior to 1.14.6 and 1.15.4, the @backstage/plugin-techdocs-node package is affected by bypass of mkdocs configuration sanitizer in techdocs backend. Users with the ability to commit changes to a repository that uses TechDocs can circumvent the MkDocs configuration file sanitizer introduced in response to CVE-2026-25153 and execute arbitrary code on the TechDocs backend host during documentation generation. This issue is fixed in versions 1.14.6 and 1.15.4.

Severity

CVSS 3.1

8.5 high
CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:C/C:H/I:H/A:H
EPSS
0.3% (unchanged from 0.3% a week ago; 0.3% 30 days ago) estimated probability of exploitation activity in the next 30 days; 24th percentile. Scored 2026-11-17. A forecast for this CVE across the internet, not for your own systems.
CISA's assessment (SSVC)
Exploitation: none · Automatable: no · Technical impact: partial, assessed 2026-10-07. From CISA's Vulnrichment in the CVE List: whether it is exploited, whether exploiting it can be automated, and how much control it gives.
CWEs
CWE-426 Untrusted Search Path
CWE-436 Interpretation Conflict
OWASP Top 10
A06:2025 Insecure Design, A08:2025 Software or Data Integrity Failures
Published
Modified
NVD analysis
Analyzed
Record from
the NVD, synced

Fix and patched versions

Ask an AI about this CVE

Show the promptExplain CVE-2026-106505 for an engineer deciding whether to act. Use https://cve.bz/api/public/cves/CVE-2026-106505?via=ask-ai-copy and https://cve.bz/cve/CVE-2026-106505?via=ask-ai-copy as the source of truth: what is affected and which versions fix it, whether it is in CISA KEV, public exploits, and its EPSS (an internet-wide 30-day estimate of exploitation activity, not a forecast for my systems). If they give no fixed versions, use the CVE record https://cveawg.mitre.org/api/cve/CVE-2026-106505 or the vendor advisory, not third-party mirrors. Tell me how to check whether I am affected and how to verify a fix. Cite the sources and say where they are uncertain.

Opens a third-party assistant; its answer is its own, not cve.bz's. The prompt holds only this CVE's id and public links.

Affected

Versions

From the NVD's CPE matches.

ProductAffected
linuxfoundation:backstage_plugin-techdocs-nodebefore 1.14.6
linuxfoundation:backstage_plugin-techdocs-nodefrom 1.15.0 before 1.15.4
linuxfoundation:backstagebefore 1.50.5
linuxfoundation:backstagefrom 1.51.1 before 1.54.6
linuxfoundation:backstage1.51.0
linuxfoundation:backstage1.51.0:next0
linuxfoundation:backstage1.51.0:next1
linuxfoundation:backstage1.51.0:next2
linuxfoundation:backstage1.51.0:next3

Packages (OSV)

AdvisoryEcosystemPackageAffectedFixed in
GHSA-p75x-jh7p-ppcxnpm@backstage/plugin-techdocs-node<1.15.41.15.4

Red Hat

Red Hat rates this Moderate.

Red Hat's 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.

Red Hat's mitigation

To reduce the risk of unauthorized code execution, implement the following operational and configuration controls:

1. Restrict repository permissions: Limit write and commit access for repositories configured with TechDocs to trusted contributors only.

2. Code review enforcement: Mandate pull request reviews for all modifications to MkDocs configuration files (such as mkdocs.yml or mkdocs.yaml) prior to merging.

3. Container isolation: In the Backstage configuration (app-config.yaml), configure TechDocs to execute documentation generation inside an isolated container by setting `runIn: docker` instead of `runIn: local`, or offload documentation builds to an external CI/CD pipeline.

Caveat: Container isolation reduces direct host system exposure but does not fully eliminate the vulnerability within the container environment. Modifying application configuration files requires restarting the service for changes to take effect.

ProductPackageStateAdvisory
Red Hat Developer Hub 1rhdh/rhdh-hub-rhel9Fix deferred
Self-service automation portal 2ansible-automation-platform/automation-portalAffected
Self-service automation portal 2ansible-automation-platform/bootc-automation-portal-rhel9Affected

Contains Red Hat Security Data © Red Hat, Inc., licensed under CC BY 4.0. Source: https://access.redhat.com/security/data. Modified: reformatted. Red Hat's page for CVE-2026-106505.

Attack patterns (CAPEC)

  • CAPEC-38 Leveraging/Manipulating Configuration File Search Paths Likelihood: High · Severity: Very High
  • CAPEC-34 HTTP Response Splitting Likelihood: Medium · Severity: High
  • CAPEC-105 HTTP Request Splitting Likelihood: Medium · Severity: High
  • CAPEC-273 HTTP Response Smuggling Likelihood: Medium · Severity: High

The attack patterns MITRE's CAPEC relates to this record's weaknesses, as MITRE names them. Credits.

References

Check your stackJSON