GitHub Advisoryadvisory · npm

GHSA-p7g9-rp3g-mgfg Backstage: Catalog unprocessed read endpoints allow authenticated cross-owner data access without permission checks

MEDIUM Published 2026-05-06 Modified 2026-05-14 Official page ↗
Aliases
CVE-2026-44374
Ecosystem
npm
Packages
@backstage/plugin-catalog-unprocessed-entities-common, @backstage/plugin-catalog-unprocessed-entities, @backstage/plugin-catalog-backend-module-unprocessed
Severity
Moderate
CVSS vector
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:N/A:N
Weaknesses
CWE-863
Reviewed
2026-05-06

Affected packages

• npm @backstage/plugin-catalog-unprocessed-entities-common: < 0.0.15 → fixed in 0.0.15 • npm @backstage/plugin-catalog-unprocessed-entities: < 0.2.30 → fixed in 0.2.30 • npm @backstage/plugin-catalog-backend-module-unprocessed: < 0.6.11 → fixed in 0.6.11

Description

Impact The unprocessed entities read endpoints in `@backstage/plugin-catalog-backend-module-unprocessed` do not enforce permission authorization checks. Any authenticated user can access unprocessed entity records regardless of ownership. This is an information disclosure vulnerability affecting Backstage installations using this module. ### Patches This is patched in `@backstage/plugin-catalog-backend-module-unprocessed` version 0.6.11, `@backstage/plugin-catalog-unprocessed-entities-common` version 0.0.15 and `@backstage/plugin-catalog-unprocessed-entities` version 0.2.30. Users should upgrade all packages. ### Workarounds If users cannot upgrade, they can remove the `@backstage/plugin-catalog-backend-module-unprocessed` module from their backend until the patch is applied. There is no configuration-based workaround to add permission checks to these endpoints without upgrading.

Related

Alias · CVE (1)

  • CVE-2026-44374 Backstage is an open framework for building developer portals. vulnerability

Weakness · CWE (1)

  • CWE-863 Incorrect Authorization weakness

References