Medium

Backstage catalog rules can be bypassed for URL locations using encoded path segments

  • Disclosed: 28.10.2026
  • Updated: 29.10.2026 01:17

Summary

@backstage/plugin-catalog-backend matches URL-type locations against catalog.rules location patterns using the raw URL string submitted by the user, while URL readers resolve that same string in canonical form when fetching the location's content. A URL can therefore be crafted so that it appears to belong to a trusted location scope during rule evaluation, but is fetched from a different scope.

Details

When a deployment restricts catalog kinds to trusted URL prefixes using catalog.rules location patterns, DefaultCatalogRulesEnforcer applies glob matching directly to the raw location.target string. The URL readers used for ingestion resolve the same target in canonical form, including normalizing percent-encoded dot segments. A registered location such as https://<host>/trusted/%2e%2e/attacker/repo/blob/main/catalog-info.yaml matches a https://<host>/trusted/** pattern as a raw string, but resolves to and is fetched from https://<host>/attacker/repo/... when its content is read.

An authenticated user with permission to register catalog locations (catalog.location.create) can use this to have an entity from an untrusted source admitted as if it originated from a trusted location scope.

Impact

The crossed boundary is the operator-configured catalog ingestion policy: entity content from outside the trusted location scope is ingested as if it were within it. Downstream consequences depend on deployment configuration, for example actions taken with integration credentials by processors or scaffolder when acting on the ingested entity. The assessment of this report found no basis for impact claims beyond the ingestion policy boundary itself.

Patches

This is fixed in @backstage/plugin-catalog-backend 3.9.2 (Backstage release 1.54.10) and 4.0.2 (Backstage release 1.56.1). Version 4.0.1 as published is not fixed.

Workarounds

No complete workaround is available for deployments that rely on URL location patterns to restrict catalog kinds. Restricting location registration permissions reduces exposure.

Affected software

Click a technology to see all vulnerabilities affecting it.

PlatformPackageVulnerable versionsFixed in
npm package @backstage/plugin-catalog-backend < 3.9.2, >= 4.0.0, < 4.0.2 3.9.2, 4.0.2

References

CVSS score 6.5/10
CVSS vector
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:H/A:N
Weakness (CWE)
CWE-22
Platform
npm
Package
@backstage/plugin-catalog-backend
Disclosed
28.10.2026
Updated
29.10.2026 01:17

Sources and licenses

OSV / GitHub Advisory Database - GHSA-w658-mh9p-ww8f - CC BY 4.0

Vulnerability history: @backstage/plugin-catalog-backend

All published vulnerabilities of this package (npm package), newest first. Shows whether this is a one-off slip or a package that needs watching.

Total entries
5
First → latest
02.2023 10.2026
Without a fix
0
Exploited in attacks
0

Severity breakdown

  • High 2
  • Medium 2
  • Low 1

Disclosures per year

  1. 2023: 1
  2. 2024: 1
  3. 2025: 0
  4. 2026: 3
  1. Backstage catalog rules can be bypassed for URL locations using encoded path segments this entry
    Medium · 6.5 CVE-2026-115923 < 3.9.2, >= 4.0.0, < 4.0.2 3.9.2, 4.0.2
  2. High · 6.5 CVE-2024-45815 < 1.26.0 1.26.0
  3. Medium · 6.8 CVE-2023-25571 < 1.7.2 1.7.2

Know which vulnerabilities affect your application

With the DockRay integration and software inventory enabled, DockRay checks reported component versions against known vulnerabilities and notifies you about confirmed matches. Coverage depends on the supported technology and available advisory data.

Connect your application
DockRay newsletter

Application security in your inbox

Important vulnerabilities, actionable guidance and practical advice for your applications. Choose your technologies and follow what matters to your project.

  • A daily digest of new vulnerabilities, critical ones included.
  • Notifications about important updates.
  • Practical advice on application security and monitoring.

Leave empty to receive updates for every technology.

Free to subscribe. Unsubscribe with one click in any email.