CVE-2026-44374 — @backstage/plugin-catalog…
MEDIUMCVE-2026-44374 is a medium-severity (CVSS 4.3) CWE-863 vulnerability in @backstage/plugin-catalog-unprocessed-entities-common. A fix is available for @backstage/plugin-catalog-unprocessed-entities-common — see the affected versions and patch details below.
Backstage: Catalog unprocessed read endpoints allow authenticated cross-owner data access without permission checks
Exploitation Status
No confirmed exploitation observed yet
- CISA’s own triage has not observed active exploitation or public proof-of-concept code for this CVE as of its last assessment.
Exploitation and automatability from CISA’s SSVC triage for CVE-2026-44374.
EPSS Exploitation Probability
Probability of exploitation in the next 30 days, from FIRST.org EPSS.
How urgent is this, really
Where this sits among everything scored
Real-World Exposure
How broadly this vulnerability is actually deployed: weekly install volume shows current usage, and reverse-dependency count shows how many other packages break if it stays unpatched.
@backstage/plugin-catalog-unprocessed-entities-commonnpm@backstage/plugin-catalog-unprocessed-entitiesnpm@backstage/plugin-catalog-backend-module-unprocessednpmDescription
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.
Affected Packages
| Ecosystem | Package | Vulnerable range | Fix |
|---|---|---|---|
| 📦npm | @backstage/plugin-catalog-unprocessed-entities-common | all versions | 0.0.15npm install @backstage/plugin-catalog-unprocessed-entities-common@0.0.15 |
| 📦npm | @backstage/plugin-catalog-unprocessed-entities | all versions | 0.2.30npm install @backstage/plugin-catalog-unprocessed-entities@0.2.30 |
| 📦npm | @backstage/plugin-catalog-backend-module-unprocessed | all versions | 0.6.11npm install @backstage/plugin-catalog-backend-module-unprocessed@0.6.11 |
Affected Products
backstage\/plugin-catalog-backend-module-unprocessedlinuxfoundationbackstage\/plugin-catalog-unprocessed-entitieslinuxfoundationbackstage\/plugin-catalog-unprocessed-entities-commonlinuxfoundationDetection & mitigation playbook
Open-source dependencyDetect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for @backstage/plugin-catalog-unprocessed-entities-common, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update @backstage/plugin-catalog-unprocessed-entities-common to 0.0.15 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2026-44374 is resolved across your whole dependency graph.
Workarounds
Put an independent control in front of the weakness: restrict the affected endpoint or interface to trusted networks, require an additional authentication factor or proxy-level check, and invalidate existing sessions and credentials in case the flaw has already been used.
Frequently Asked Questions
Is CVE-2026-44374 in your dependencies?
Find it across npm, including transitive dependencies.