cve.bz

CVE-2026-106558 linuxfoundation: Deserialization of Untrusted Data

8.8 highEPSS 0.5%Fix available

High (8.8) in linuxfoundation. EPSS 0.5% 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.8, 1.15.6, and 2.0.1, the @backstage/plugin-techdocs-node package improperly validated mapping-style markdown_extensions configuration. An authenticated attacker who can register or influence an SCM-backed documentation source may bypass TechDocs sanitization and cause Python objects to be imported and instantiated in the generator runtime, leading to arbitrary code execution. Earlier fixes in versions 1.14.6 and 1.15.4 did not fully address the supported mapping representation of markdown_extensions. Impact is greatest when documentation generation runs with backend credentials, filesystem access, or internal network access. This issue is fixed in versions 1.14.8, 1.15.6, and 2.0.1.

Severity

CVSS 3.1

8.8 high
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
EPSS
0.5% (unchanged from 0.5% a week ago; 0.5% 30 days ago) estimated probability of exploitation activity in the next 30 days; 41st 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: total, assessed 2026-10-10. From CISA's Vulnrichment in the CVE List: whether it is exploited, whether exploiting it can be automated, and how much control it gives.
CWE
CWE-502 Deserialization of Untrusted Data
OWASP Top 10
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-106558 for an engineer deciding whether to act. Use https://cve.bz/api/public/cves/CVE-2026-106558?via=ask-ai-copy and https://cve.bz/cve/CVE-2026-106558?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-106558 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.8
linuxfoundation:backstage_plugin-techdocs-nodefrom 1.15.0 before 1.15.6
linuxfoundation:backstage_plugin-techdocs-nodefrom 2.0.0 before 2.0.1
linuxfoundation:backstagebefore 1.50.7
linuxfoundation:backstagefrom 1.51.1 before 1.54.8
linuxfoundation:backstagefrom 1.55.1 before 1.55.2
linuxfoundation:backstage1.51.0
linuxfoundation:backstage1.51.0:next0
linuxfoundation:backstage1.51.0:next1
linuxfoundation:backstage1.51.0:next2
linuxfoundation:backstage1.51.0:next3
linuxfoundation:backstage1.55.0
linuxfoundation:backstage1.55.0:next0
linuxfoundation:backstage1.55.0:next1
linuxfoundation:backstage1.55.0:next2

Packages (OSV)

AdvisoryEcosystemPackageAffectedFixed in
GHSA-qmw3-745m-w99gnpm@backstage/plugin-techdocs-node<1.15.41.15.4

Red Hat

Red Hat rates this Moderate.

Red Hat's statement

A flaw of Moderate severity was found in the Backstage @backstage/plugin-techdocs-node package, which is shipped in Red Hat Developer Hub and Red Hat Ansible Automation Platform. The package improperly validates the mapping-style markdown_extensions configuration used by TechDocs. An authenticated attacker who can register or modify documentation in a source code management (SCM) repository can bypass TechDocs sanitization checks by supplying a crafted markdown extension configuration, causing Python objects to be imported and instantiated in the documentation generator runtime, resulting in potential arbitrary code execution.

This vulnerability is rated Moderate rather than Important because of its configuration and permission requirements. Within Red Hat products, exploitation requires an administrator to deliberately enable in-tree documentation generation by setting both techdocs.builder: local and techdocs.generator.runIn: local.

Red Hat's mitigation

To reduce exposure to this flaw, implement operational access restrictions and isolate documentation generation:

1. Restrict catalog registration: Limit permissions for registering catalog entities and TechDocs components to trusted administrators, preventing untrusted users from adding unverified documentation repositories.

2. Enforce repository change controls: Apply branch protection and mandatory code review to repository documentation configuration files (such as mkdocs.yml) to verify markdown extension definitions before documentation is processed.

3. Isolate generator environments: Offload TechDocs generation to an external, sandboxed CI/CD build process rather than running generation inside the core platform container, ensuring build runners operate with minimal privileges and without access to backend credentials or internal network resources.

Caveat: Restricting catalog registration limits developer self-service onboarding, and external build pipelines require ongoing operational maintenance.

ProductPackageStateAdvisory
Red Hat Developer Hub 1rhdh/rhdh-hub-rhel9Affected
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-106558.

Attack patterns (CAPEC)

  • CAPEC-586 Object Injection 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