GHSA-q38j-6vcm-2f5m Backstage: Improper validation of MkDocs plugin configuration in TechDocs

• npm @backstage/plugin-techdocs-node: >= 0.11.12, < 1.14.7 → fixed in 1.14.7 • npm @backstage/plugin-techdocs-node: >= 1.15.0, < 1.15.5 → fixed in 1.15.5

Impact An authenticated attacker with control over a TechDocs source repository could cause a documentation build to retrieve and publish data from network locations reachable by the build environment. Exposure depends on deployment topology, build mode, and target endpoint protections. Modern cloud metadata services that require tokens or special headers are not directly accessible through the affected behavior. Patches Upgrade `@backstage/plugin-techdocs-node` to a patched version for the applicable release line: • `1.14.x`: upgrade to `1.14.7` or later in that line, available in Backstage v1.50.6. • `1.15.x`: upgrade to `1.15.5` or later, available in Backstage v1.54.8. • Current mainline: upgrade to `2.0.0` or later, available in Backstage v1.55.0. The update removes MkDocs plugins outside the built-in allowlist. To retain additional plugins, review them and configure `techdocs.generator.mkdocs.dangerouslyAllowAdditionalPlugins`, or supply `dangerouslyAllowAdditionalPlugins` when creating the generator directly. Plugins supplied through `defaultPlugins` remain permitted. Workarounds • Restrict control of TechDocs source repositories and catalog registration to trusted maintainers. • Run documentation builders with outbound access to private and link-local networks denied. • Require token- or header-protected cloud instance metadata services.