CVE-2026-44374

CVE-2026-44374 is a medium-severity incorrect authorization vulnerability in @backstage/plugin-catalog-unprocessed-entities-common (npm), affecting versions < 0.0.15. It is fixed in 0.0.15, 0.2.30, 0.6.11.

Summary

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

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.

The application does not correctly enforce access controls, allowing a principal to access resources or operations beyond their granted permissions. Typical impact: unauthorized data access or execution of privileged operations.

CVE-2026-44374 has a CVSS score of 4.3 (Medium). The vector is network-reachable, low privileges required, and no user interaction. A CVSS score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether this affects your application depends on whether the vulnerable code is present and reachable in your environment. A fixed version is available (0.0.15, 0.2.30, 0.6.11); upgrading removes the vulnerable code path.

Affected versions

@backstage/plugin-catalog-unprocessed-entities-common (< 0.0.15) @backstage/plugin-catalog-unprocessed-entities (< 0.2.30) @backstage/plugin-catalog-backend-module-unprocessed (< 0.6.11)

Security releases

@backstage/plugin-catalog-unprocessed-entities-common → 0.0.15 (npm) @backstage/plugin-catalog-unprocessed-entities → 0.2.30 (npm) @backstage/plugin-catalog-backend-module-unprocessed → 0.6.11 (npm)

Kodem intelligence

Severity tells you how bad this could be in the worst case. It does not tell you whether you are exposed. Exploitability and impact are functions of runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A vulnerable package can sit in your dependency tree and never run.

Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter. Kodem's runtime-powered SCA identifies whether this CVE is reachable in your applications.

See it in your environment

Remediation advice

Upgrade the following packages to resolve this vulnerability:

@backstage/plugin-catalog-unprocessed-entities-common to 0.0.15 or later; @backstage/plugin-catalog-unprocessed-entities to 0.2.30 or later; @backstage/plugin-catalog-backend-module-unprocessed to 0.6.11 or later

Kodem Kai can prioritize this vulnerability in your dependency tree and generate a fix recommendation.

Frequently Asked Questions

  1. What is CVE-2026-44374? CVE-2026-44374 is a medium-severity incorrect authorization vulnerability in @backstage/plugin-catalog-unprocessed-entities-common (npm), affecting versions < 0.0.15. It is fixed in 0.0.15, 0.2.30, 0.6.11. The application does not correctly enforce access controls, allowing a principal to access resources or operations beyond their granted permissions.
  2. How severe is CVE-2026-44374? CVE-2026-44374 has a CVSS score of 4.3 (Medium). This score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether it represents real risk in your environment depends on whether the vulnerable code is present and reachable.
  3. Which packages are affected by CVE-2026-44374?
    • @backstage/plugin-catalog-unprocessed-entities-common (npm) (versions < 0.0.15)
    • @backstage/plugin-catalog-unprocessed-entities (npm) (versions < 0.2.30)
    • @backstage/plugin-catalog-backend-module-unprocessed (npm) (versions < 0.6.11)
  4. Is there a fix for CVE-2026-44374? Yes. CVE-2026-44374 is fixed in 0.0.15, 0.2.30, 0.6.11. Upgrade to this version or later.
  5. Is CVE-2026-44374 exploitable, and should I be worried? Whether CVE-2026-44374 is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk. Get a demo
  6. What actually determines whether CVE-2026-44374 is exploitable, and how bad it is? Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.
  7. How do I fix CVE-2026-44374?
    • Upgrade @backstage/plugin-catalog-unprocessed-entities-common to 0.0.15 or later
    • Upgrade @backstage/plugin-catalog-unprocessed-entities to 0.2.30 or later
    • Upgrade @backstage/plugin-catalog-backend-module-unprocessed to 0.6.11 or later

Other vulnerabilities in @backstage/plugin-catalog-unprocessed-entities-common

Stop the waste.
Protect your environment with Kodem.

Get a personalized demo
Get a personalized demo