{"id":"CVE-2026-25153","summary":"@backstage/plugin-techdocs-node vulnerable to arbitrary code execution via MkDocs hooks","details":"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 \u003c 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.","aliases":["GHSA-6jr7-99pf-8vgf"],"modified":"2026-08-12T03:51:18.624104023Z","published":"2026-01-30T21:31:58.870Z","database_specific":{"cna_assigner":"GitHub_M","cwe_ids":["CWE-94"],"osv_generated_from":"https://github.com/CVEProject/cvelistV5/tree/main/cves/2026/25xxx/CVE-2026-25153.json","unresolved_ranges":[{"extracted_events":[{"fixed":"1.13.11"}],"source":"AFFECTED_FIELD"}]},"references":[{"type":"WEB","url":"https://security.access.redhat.com/data/csaf/v2/vex/2026/cve-2026-25153.json"},{"type":"ADVISORY","url":"https://access.redhat.com/errata/RHSA-2026:6174"},{"type":"ADVISORY","url":"https://access.redhat.com/errata/RHSA-2026:6802"},{"type":"ADVISORY","url":"https://access.redhat.com/security/cve/CVE-2026-25153"},{"type":"ADVISORY","url":"https://github.com/CVEProject/cvelistV5/tree/main/cves/2026/25xxx/CVE-2026-25153.json"},{"type":"ADVISORY","url":"https://github.com/backstage/backstage/security/advisories/GHSA-6jr7-99pf-8vgf"},{"type":"ADVISORY","url":"https://nvd.nist.gov/vuln/detail/CVE-2026-25153"},{"type":"REPORT","url":"https://bugzilla.redhat.com/show_bug.cgi?id=2435576"}],"affected":[{"ranges":[{"type":"GIT","repo":"https://github.com/backstage/backstage","events":[{"introduced":"72ee1d9fd98f51c2e1aca58fd69163ad96c41162"},{"fixed":"99d7a6f42d71e86578c89c0669a3d962088ed8ae"}],"database_specific":{"source":["AFFECTED_FIELD","CPE_RANGE"],"cpe":"cpe:2.3:a:linuxfoundation:backstage:*:*:*:*:*:*:*:*","extracted_events":[{"introduced":"= 1.14.0"},{"last_affected":"= 1.14.0"},{"introduced":"1.14.0"},{"fixed":"1.14.1"}]}}],"versions":["= 1.14.0","v1.14.0"],"database_specific":{"source":"https://storage.googleapis.com/cve-osv-conversion/osv-output/CVE-2026-25153.json"}}],"schema_version":"1.9.0","severity":[{"type":"CVSS_V3","score":"CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:C/C:H/I:L/A:L"}]}