Security readout for executives and security teams
Plain-English summary
This vulnerability lets a low-privileged attacker make Backstage TechDocs run arbitrary Python code during documentation generation. The business risk is serious where developer portals build documentation from user- or repository-controlled mkdocs.yml files, because the build system may have access to internal services, tokens, or source metadata.
Executive priority
Treat this as urgent for any Backstage portal that builds TechDocs from contributor-controlled repositories. The vulnerability can convert documentation publishing into code execution inside internal build infrastructure, which may expose sensitive developer systems even without public internet exploitation evidence.
Technical view
@backstage/plugin-techdocs-node before 1.14.3 filters dangerous MkDocs configuration keys with an allowlist. The advisory says a gap in that allowlist permits crafted mkdocs.yml content to bypass TechDocs controls and execute arbitrary Python code during the build process. CVSS 9.1 indicates network reachability, low attack complexity, low privileges, and changed scope.
Likely exposure
Backstage environments using TechDocs builds with @backstage/plugin-techdocs-node versions before 1.14.3 are the stated exposure. Risk is highest where contributors can influence mkdocs.yml through repositories, pull requests, templates, or documentation pipelines processed by the portal.
Exploitation context
The source bundle does not show CISA KEV listing or cited evidence of active exploitation. Exploitation requires getting a crafted MkDocs configuration processed by TechDocs, so exposure depends on repository permissions, documentation build triggers, and the privileges of the build runtime.
Researcher notes
Focus validation on TechDocs build boundaries, mkdocs.yml trust assumptions, and the effective privileges of the documentation builder. The provided sources identify the affected package and fixed version, but do not provide complete product deployment matrices beyond Backstage versions before 1.14.3.
Mitigation direction
- Upgrade @backstage/plugin-techdocs-node or Backstage to version 1.14.3 or later.
- Check GitHub and Red Hat advisories for environment-specific guidance.
- Inventory TechDocs build pipelines that process repository-controlled mkdocs.yml files.
- Limit or pause untrusted TechDocs builds until patched, if upgrade is delayed.
- Review build runtime secrets and permissions for unnecessary access.
Validation and detection
- Check deployed Backstage and @backstage/plugin-techdocs-node versions against 1.14.3.
- Confirm runtime images and lockfiles contain the patched package version.
- Identify who can submit or modify mkdocs.yml processed by TechDocs.
- Review recent TechDocs build logs for unexpected Python execution indicators.
- Verify documentation builds still succeed after upgrading.
Public sources used
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Conservative CVE-to-ATT&CK context
These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.
ATT&CK lookup starting points
Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.
CWE-434: File access and web shell behavior lookup
File traversal and upload weaknesses can lead teams to review file, web shell, execution, and collection telemetry. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.
Open ATT&CK lookupCWE-74: Exact CWE lookup
Use the exact CWE identifier as the starting point before reviewing related ATT&CK behavior. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.
Open ATT&CK lookupCWE-791: Exact CWE lookup
Use the exact CWE identifier as the starting point before reviewing related ATT&CK behavior. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.
Open ATT&CK lookupExecution behavior lookup
The CVE wording references code or command execution, so execution technique review may help defensive triage. This is a Glexia inferred lookup path, not an official MITRE, ATT&CK, or CVE Program mapping.
Open ATT&CK lookupCVE-2026-29186 mapping review
Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.
Open ATT&CK lookup- Severity
- Critical
- CVSS
- 9.1 (3.1)
- Known Exploited
- No
- Published
Vector: CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:L/A:L
CNA and ADP enrichment extracted from CVE v5
These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.
SSVC decision data
CVSS vector scores
2 official scoresWe collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:L/A:L3.15.3redhat-SADPCVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:C/C:H/I:L/A:L1.85.3GitHub_MVulnerability scoring details
Base CVSS 3.1 score
9.1CriticalVector: CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:L/A:L
Base CVSS 3.1 score
7.7HighVector: CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:C/C:H/I:L/A:L
Vulnerability timeline
Timeline events are normalized from CVE metadata, CNA source timelines, ADP timelines, and KEV metadata when present.
- CVE reservedCVE Program
The CVE ID was reserved by the assigning CNA.
- ADP timelineredhat-SADP
Made public.
- CVE publishedCVE Program
The CVE record was published.
- ADP timelineredhat-SADP
Reported to Red Hat.
- CVE updatedCVE Program
The CVE record metadata indicates this as the latest update time.
ADP provider summaries
- 2026-03-07T16:01:40.949Z: Reported to Red Hat.
- 2026-03-07T15:03:51.422Z: Made public.
Source materials
- CVE List V5 sourceCVE List V5
- https://github.com/backstage/backstage/security/advisories/GHSA-928r-fm4v-mvrwCVE reference, GitHub_M · x_refsource_CONFIRM
- https://access.redhat.com/security/cve/CVE-2026-29186CVE reference, redhat-SADP · vdb-entry, x_refsource_REDHAT
- RHBZ#2445480CVE reference, redhat-SADP · issue-tracking, x_refsource_REDHAT
- https://security.access.redhat.com/data/csaf/v2/vex/2026/cve-2026-29186.jsonCVE reference, redhat-SADP · x_sadp-csaf-vex
- https://access.redhat.com/errata/RHSA-2026:9742CVE reference, redhat-SADP · vendor-advisory, x_refsource_REDHAT
- https://access.redhat.com/errata/RHSA-2026:13826CVE reference, redhat-SADP · vendor-advisory, x_refsource_REDHAT
Products and packages named in the record
CWE details
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.
Unrestricted Upload of File with Dangerous Type
Unrestricted Upload of File with Dangerous Type represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.
Improper Neutralization of Special Elements in Output Used by a Downstream Component ('Injection')
Improper Neutralization of Special Elements in Output Used by a Downstream Component ('Injection') represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.
Incomplete Filtering of Special Elements
Incomplete Filtering of Special Elements represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.