Descrizione
Backstage is an open framework for building developer portals, and @backstage/plugin-techdocs-node provides common node.js functionalities for TechDocs. In versions of @backstage/plugin-techdocs-node prior to 1.13.11 and 1.14.1, when TechDocs is configured with `runIn: local`, a malicious actor who can submit or modify a repository's `mkdocs.yml` file can execute arbitrary Python code on the TechDocs build server via MkDocs hooks configuration. @backstage/plugin-techdocs-node versions 1.13.11 and 1.14.1 contain a fix. The fix introduces an allowlist of supported MkDocs configuration keys. Unsupported configuration keys (including `hooks`) are now removed from `mkdocs.yml` before running the generator, with a warning logged to indicate which keys were removed. Users of `@techdocs/cli` should also upgrade to the latest version, which includes the fixed `@backstage/plugin-techdocs-node` dependency. Some workarounds are available. Configure TechDocs with `runIn: docker` instead of `runIn: local` to provide container isolation, though it does not fully mitigate the risk. Limit who can modify `mkdocs.yml` files in repositories that TechDocs processes; only allow trusted contributors. Implement PR review requirements for changes to `mkdocs.yml` files to detect malicious `hooks` configurations before they are merged. Use MkDocs < 1.4.0 (e.g., 1.3.1) which does not support hooks. Note: This may limit access to newer MkDocs features. Building documentation in CI/CD pipelines using `@techdocs/cli` does not mitigate this vulnerability, as the CLI uses the same vulnerable `@backstage/plugin-techdocs-node` package.
Come correggere
Priorità: Alta — pianificare la correzione entro pochi giorni. Motivazione: CVSS 9.1.
Versioni da aggiornare
- Linuxfoundation Backstage/Plugin-Techdocs-Node: vulnerabili le versioni precedenti alla
1.13.11→ aggiornare alla1.13.11o successiva. - Linuxfoundation Backstage/Plugin-Techdocs-Node: vulnerabili le versioni dalla
1.14.0precedenti alla1.14.1→ aggiornare alla1.14.1o successiva.
Patch e advisory
- Advisory del vendor: github.com/backstage/backstage/security/advisor…
- Advisory di terze parti: access.redhat.com/errata/RHSA-2026:6174
- Advisory di terze parti: access.redhat.com/errata/RHSA-2026:6802
- Advisory di terze parti: access.redhat.com/security/cve/CVE-2026-25153
- Advisory di terze parti: bugzilla.redhat.com/show_bug.cgi
- Advisory di terze parti: security.access.redhat.com/data/csaf/v2/vex/2026/cve-2026-25153…
Mitigazioni temporanee
Da applicare solo se non è possibile aggiornare subito:
- Bloccare l'accesso esterno al componente, applicare regole WAF per payload di code/template injection e monitorare l'esecuzione di processi figli.
Verifica
- Individuare tutti gli asset con il prodotto interessato (inventario, scanner di vulnerabilità, CMDB).
- Confrontare la versione installata con quelle indicate sopra.
- Applicare l'aggiornamento in un ambiente di test, poi in produzione; riavviare i servizi se richiesto.
- Ripetere la scansione per confermare la correzione.
Configurazioni interessate
| Vendor | Prodotto | Versioni vulnerabili | Corretta in |
|---|---|---|---|
| Linuxfoundation | Backstage/Plugin-Techdocs-Node | < 1.13.11 | 1.13.11 |
| Linuxfoundation | Backstage/Plugin-Techdocs-Node | ≥ 1.14.0 < 1.14.1 | 1.14.1 |
Riferimenti
- Advisory del vendorhttps://github.com/backstage/backstage/security/advisories/GHSA-6jr7-99pf-8vgf
- Advisory di terze partihttps://access.redhat.com/errata/RHSA-2026:6174
- Advisory di terze partihttps://access.redhat.com/errata/RHSA-2026:6802
- Advisory di terze partihttps://access.redhat.com/security/cve/CVE-2026-25153
- Advisory di terze partihttps://bugzilla.redhat.com/show_bug.cgi?id=2435576
- Advisory di terze partihttps://security.access.redhat.com/data/csaf/v2/vex/2026/cve-2026-25153.json