{"resultsPerPage":1,"startIndex":0,"totalResults":1,"format":"NVD_CVE","version":"2.0","timestamp":"2026-06-11T13:58:09.568","vulnerabilities":[{"cve":{"id":"CVE-2026-25153","sourceIdentifier":"security-advisories@github.com","published":"2026-01-30T22:15:56.343","lastModified":"2026-02-19T15:26:37.430","vulnStatus":"Analyzed","cveTags":[],"descriptions":[{"lang":"en","value":"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."},{"lang":"es","value":"Backstage es un framework abierto para construir portales de desarrolladores, y @backstage/plugin-techdocs-node proporciona funcionalidades comunes de node.js para TechDocs. En versiones de @backstage/plugin-techdocs-node anteriores a 1.13.11 y 1.14.1, cuando TechDocs está configurado con 'runIn: local', un actor malicioso que puede enviar o modificar el archivo 'mkdocs.yml' de un repositorio puede ejecutar código Python arbitrario en el server de compilación de TechDocs a través de la configuración de hooks de MkDocs. Las versiones 1.13.11 y 1.14.1 de @backstage/plugin-techdocs-node contienen una corrección. La corrección introduce una lista de permitidos (allowlist) de claves de configuración de MkDocs compatibles. Las claves de configuración no compatibles (incluyendo 'hooks') ahora se eliminan de 'mkdocs.yml' antes de ejecutar el generador, con una advertencia registrada para indicar qué claves se eliminaron. Los usuarios de '@techdocs/cli' también deben actualizar a la última versión, que incluye la dependencia corregida de '@backstage/plugin-techdocs-node'. Algunas soluciones alternativas están disponibles. Configure TechDocs con 'runIn: docker' en lugar de 'runIn: local' para proporcionar aislamiento de contenedor, aunque no mitiga completamente el riesgo. Limite quién puede modificar los archivos 'mkdocs.yml' en los repositorios que TechDocs procesa; solo permita colaboradores de confianza. Implemente requisitos de revisión de PR para cambios en los archivos 'mkdocs.yml' para detectar configuraciones maliciosas de 'hooks' antes de que se fusionen. Use MkDocs &lt; 1.4.0 (por ejemplo, 1.3.1) que no soporta hooks. Nota: Esto puede limitar el acceso a características más nuevas de MkDocs. La compilación de documentación en pipelines de CI/CD usando '@techdocs/cli' no mitiga esta vulnerabilidad, ya que la CLI utiliza el mismo paquete vulnerable de '@backstage/plugin-techdocs-node'."}],"metrics":{"cvssMetricV31":[{"source":"security-advisories@github.com","type":"Secondary","cvssData":{"version":"3.1","vectorString":"CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:C/C:H/I:L/A:L","baseScore":7.7,"baseSeverity":"HIGH","attackVector":"NETWORK","attackComplexity":"HIGH","privilegesRequired":"LOW","userInteraction":"NONE","scope":"CHANGED","confidentialityImpact":"HIGH","integrityImpact":"LOW","availabilityImpact":"LOW"},"exploitabilityScore":1.8,"impactScore":5.3},{"source":"nvd@nist.gov","type":"Primary","cvssData":{"version":"3.1","vectorString":"CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H","baseScore":8.8,"baseSeverity":"HIGH","attackVector":"NETWORK","attackComplexity":"LOW","privilegesRequired":"LOW","userInteraction":"NONE","scope":"UNCHANGED","confidentialityImpact":"HIGH","integrityImpact":"HIGH","availabilityImpact":"HIGH"},"exploitabilityScore":2.8,"impactScore":5.9}]},"weaknesses":[{"source":"security-advisories@github.com","type":"Primary","description":[{"lang":"en","value":"CWE-94"}]}],"configurations":[{"nodes":[{"operator":"OR","negate":false,"cpeMatch":[{"vulnerable":true,"criteria":"cpe:2.3:a:linuxfoundation:backstage:*:*:*:*:*:*:*:*","versionEndExcluding":"1.13.11","matchCriteriaId":"086F7DE4-8356-4AE3-9E29-B852A5C4B2DB"},{"vulnerable":true,"criteria":"cpe:2.3:a:linuxfoundation:backstage:*:*:*:*:*:*:*:*","versionStartIncluding":"1.14.0","versionEndExcluding":"1.14.1","matchCriteriaId":"0393AC7C-1889-4869-ABAF-1C5D96CA2C06"}]}]}],"references":[{"url":"https://github.com/backstage/backstage/security/advisories/GHSA-6jr7-99pf-8vgf","source":"security-advisories@github.com","tags":["Vendor Advisory"]}]}}]}