<?xml version='1.0' encoding='UTF-8'?>
<?xml-stylesheet href="/static/style.xsl" type="text/xsl"?>
<feed xmlns="http://www.w3.org/2005/Atom" xml:lang="en">
  <id>https://vulnerability.circl.lu/rss/recent/all/10</id>
  <title>Most recent entries from all</title>
  <updated>2026-10-07T23:53:24.080309+00:00</updated>
  <author>
    <name>Vulnerability-Lookup</name>
    <email>info@circl.lu</email>
  </author>
  <link href="https://vulnerability.circl.lu" rel="alternate"/>
  <generator uri="https://lkiesow.github.io/python-feedgen" version="1.0.0">python-feedgen</generator>
  <subtitle>Contains only the most 10 recent entries.</subtitle>
  <entry>
    <id>https://vulnerability.circl.lu/vuln/fkie_cve-2026-106509</id>
    <title>fkie_cve-2026-106509</title>
    <updated>2026-10-07T23:53:24.098725+00:00</updated>
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml">
        <p>Backstage is an open framework for building developer portals. Prior to 1.14.6, the @backstage/plugin-techdocs-node package is affected by improper validation of mkdocs theme configuration in techdocs. When TechDocs is configured to build documentation locally or in a container, a user with write access to a registered repository can include configuration values in mkdocs.yml that cause arbitrary code execution during the documentation build process. This issue is fixed in versions 1.14.6 and 1.15.4.</p>
      </div>
    </content>
    <link href="https://vulnerability.circl.lu/vuln/fkie_cve-2026-106509"/>
  </entry>
  <entry>
    <id>https://vulnerability.circl.lu/vuln/ghsa-8w7q-29mw-gf5c</id>
    <title>GHSA-8w7q-29mw-gf5c — Backstage: Improper validation of MkDocs theme configuration in TechDocs</title>
    <updated>2026-10-07T23:53:24.098820+00:00</updated>
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml"><p><strong>Affected:</strong> npm: @backstage/plugin-techdocs-node</p>
<p>### Impact</p>
<p>When TechDocs is configured to build documentation locally or in a container, a user with write access to a registered repository can include configuration values in `mkdocs.yml` that cause arbitrary code execution during the documentation build process.</p>
<p>### Patches</p>
<p>Patched in `@backstage/plugin-techdocs-node` version `1.15.4`</p>
<p>### Workarounds</p>
<p>- Configure TechDocs with `techdocs.generator.runIn: 'docker'` instead of `'local'` to provide container isolation, though this does not fully mitigate the risk.
- Restrict write access to repositories registered in the Backstage catalog to trusted users.</p></div>
    </content>
    <link href="https://vulnerability.circl.lu/vuln/ghsa-8w7q-29mw-gf5c"/>
  </entry>
</feed>
