Live › vulnerability › CVE-2026-115923
Go to dashboardBackstage's catalog rules check the raw location URL, but the URL reader fetches a canonicalized version, so percent-encoded paths can make an untrusted source match a trusted pattern. An authenticated user who can create catalog locations can get untrusted entity content admitted as trusted.
Summary written from the sources below. Check the originals before acting.
First seen by InfraStack 2026-10-26 18:31 UTC. All times on this page are UTC.
Teams running Backstage with the catalog backend that let users with the catalog.location.create permission register locations, and that rely on catalog.rules to restrict which URLs are trusted. Deployments where only administrators create locations, or that do not use catalog.rules URL restrictions, are less exposed; the sources do not say what downstream consequences follow in a given configuration.
No product ranges from the sources yet.
@backstage/plugin-catalog-backend version with yarn why @backstage/plugin-catalog-backend or npm ls @backstage/plugin-catalog-backend; versions below 3.9.2, or from 4.0.0 through 4.0.1, are affected.catalog.rules and catalog.locations in the app config for allow-listed URL patterns that users can add locations under.@backstage/plugin-catalog-backend to 3.9.2 on the 3.x line, or to 4.0.2 on the 4.x line.Each row is the first time that source carried this signal. The analyst’s rows are its own findings.
Backstage is an open framework for building developer portals. Prior to 3.9.2 and from 4.0.0 until 4.0.2, DefaultCatalogRulesEnforcer in @backstage/plugin-catalog-backend compares the raw location.target URL against catalog.rules, while URL readers canonicalize the same URL before fetching it. An authenticated user with catalog.location.create permission can use percent-encoded path segments to make an untrusted URL match a trusted location pattern even though the canonical URL resolves outside that scope. This admits entity content from an untrusted source as trusted, while further downstream consequences depend on deployment configuration. This issue is fixed in versions 3.9.2 and 4.0.2.
This page as .md · .json · in your agent: get_signal("CVE-2026-115923")
NVD data is provided by NIST and is public domain. Posts quoted belong to their authors.