<?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://db.gcve.eu/rss/recent/all/10</id>
  <title>Most recent entries from all</title>
  <updated>2026-10-08T16:00:14.513113+00:00</updated>
  <author>
    <name>Vulnerability-Lookup</name>
    <email>info@gcve.eu</email>
  </author>
  <link href="https://db.gcve.eu" 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://db.gcve.eu/vuln/fkie_cve-2026-106455</id>
    <title>fkie_cve-2026-106455</title>
    <updated>2026-10-08T16:00:14.531289+00:00</updated>
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml">
        <p>Backstage is an open framework for building developer portals. From 0.11.12 until 1.14.7 and 1.15.5, the @backstage/plugin-techdocs-node package is affected by improper validation of mkdocs plugin configuration in techdocs. 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. This issue is fixed in @backstage/plugin-techdocs-node versions 1.14.7 and 1.15.5.</p>
      </div>
    </content>
    <link href="https://db.gcve.eu/vuln/fkie_cve-2026-106455"/>
  </entry>
  <entry>
    <id>https://db.gcve.eu/vuln/ghsa-q38j-6vcm-2f5m</id>
    <title>GHSA-q38j-6vcm-2f5m — Backstage: Improper validation of MkDocs plugin configuration in TechDocs</title>
    <updated>2026-10-08T16:00:14.531357+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>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.</p>
<p>### Patches</p>
<p>Upgrade `@backstage/plugin-techdocs-node` to a patched version for the applicable release line:</p>
<p>- `1.14.x`: upgrade to `1.14.7` or later in that line, available in [Backstage v1.50.6](https://github.com/backstage/backstage/releases/tag/v1.50.6).
- `1.15.x`: upgrade to `1.15.5` or later, available in [Backstage v1.54.8](https://github.com/backstage/backstage/releases/tag/v1.54.8).
- Current mainline: upgrade to `2.0.0` or later, available in [Backstage v1.55.0](https://github.com/backstage/backstage/releases/tag/v1.55.0).</p>
<p>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.</p>
<p>### Workarounds</p>
<p>- Restrict control of TechDocs source repositories and catalog registration to trusted maintainers.
- Run documentation builders with outbound access to private and link-local networks de…</p></div>
    </content>
    <link href="https://db.gcve.eu/vuln/ghsa-q38j-6vcm-2f5m"/>
  </entry>
</feed>
