https://vulnerability.circl.lu Contains only the most 10 recent entries. http://www.rssboard.org/rss-specification python-feedgen en Wed, 07 Oct 2026 17:57:12 +0000 https://vulnerability.circl.lu/vuln/fkie_cve-2026-106505 <p>Backstage is an open framework for building developer portals. Prior to 1.14.6 and 1.15.4, the @backstage/plugin-techdocs-node package is affected by bypass of mkdocs configuration sanitizer in techdocs backend. Users with the ability to commit changes to a repository that uses TechDocs can circumvent the MkDocs configuration file sanitizer introduced in response to CVE-2026-25153 and execute arbitrary code on the TechDocs backend host during documentation generation. This issue is fixed in versions 1.14.6 and 1.15.4.</p> <p>Backstage is an open framework for building developer portals. Prior to 1.14.6 and 1.15.4, the @backstage/plugin-techdocs-node package is affected by bypass of mkdocs configuration sanitizer in techdocs backend. Users with the ability to commit changes to a repository that uses TechDocs can circumvent the MkDocs configuration file sanitizer introduced in response to CVE-2026-25153 and execute arbitrary code on the TechDocs backend host during documentation generation. This issue is fixed in versions 1.14.6 and 1.15.4.</p> https://vulnerability.circl.lu/vuln/fkie_cve-2026-106505 https://vulnerability.circl.lu/vuln/ghsa-p75x-jh7p-ppcx <p><strong>Affected:</strong> npm: @backstage/plugin-techdocs-node</p> <p>### Impact</p> <p>Users with the ability to commit changes to a repository that uses TechDocs can circumvent the MkDocs configuration file sanitizer introduced in response to CVE-2026-25153 and execute arbitrary code on the TechDocs backend host during documentation generation.</p> <p>### Patches</p> <p>Patched in`@backstage/plugin-techdocs-node` version `1.15.4`</p> <p>### Workarounds</p> <p>If you cannot upgrade immediately:</p> <p>- Use Docker mode with restricted access: Configure TechDocs with `runIn: docker` instead of `runIn: local`. This provides container isolation, though it does not fully mitigate the risk. - Limit repository write access to trusted parties, since exploitation requires the ability to commit files to a repository with TechDocs enabled. - Review incoming changes to MkDocs configuration files as part of your code review process.</p> <p><strong>Affected:</strong> npm: @backstage/plugin-techdocs-node</p> <p>### Impact</p> <p>Users with the ability to commit changes to a repository that uses TechDocs can circumvent the MkDocs configuration file sanitizer introduced in response to CVE-2026-25153 and execute arbitrary code on the TechDocs backend host during documentation generation.</p> <p>### Patches</p> <p>Patched in`@backstage/plugin-techdocs-node` version `1.15.4`</p> <p>### Workarounds</p> <p>If you cannot upgrade immediately:</p> <p>- Use Docker mode with restricted access: Configure TechDocs with `runIn: docker` instead of `runIn: local`. This provides container isolation, though it does not fully mitigate the risk. - Limit repository write access to trusted parties, since exploitation requires the ability to commit files to a repository with TechDocs enabled. - Review incoming changes to MkDocs configuration files as part of your code review process.</p> https://vulnerability.circl.lu/vuln/ghsa-p75x-jh7p-ppcx