<?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-10T10:48:20.041406+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-106491</id>
    <title>fkie_cve-2026-106491</title>
    <updated>2026-10-10T10:48:20.072624+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 0.6.17, the @backstage/plugin-proxy-backend package is affected by improper input validation in proxy-backend. An authenticated Backstage user could craft a request URL that causes the proxy-backend to forward the request to a path outside the configured base path on the target server. This is limited to target servers already configured as proxy endpoints and requires Backstage authentication by default. This issue is fixed in version 0.6.17.</p>
      </div>
    </content>
    <link href="https://db.gcve.eu/vuln/fkie_cve-2026-106491"/>
  </entry>
  <entry>
    <id>https://db.gcve.eu/vuln/ghsa-9ghw-48h5-v2w5</id>
    <title>GHSA-9ghw-48h5-v2w5 — Backstage: Improper input validation in proxy-backend</title>
    <updated>2026-10-10T10:48:20.072704+00:00</updated>
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml"><p><strong>Affected:</strong> npm: @backstage/plugin-proxy-backend</p>
<p>### Impact</p>
<p>An authenticated Backstage user could craft a request URL that causes the proxy-backend to forward the request to a path outside the configured base path on the target server. This is limited to target servers already configured as proxy endpoints and requires Backstage authentication by default.</p>
<p>### Patches</p>
<p>Patched in `@backstage/plugin-proxy-backend` version `0.6.17`</p>
<p>### Workarounds</p>
<p>- Deploy a reverse proxy or WAF in front of Backstage that normalizes request paths before they reach the backend.</p></div>
    </content>
    <link href="https://db.gcve.eu/vuln/ghsa-9ghw-48h5-v2w5"/>
  </entry>
</feed>
