Skip to content

Update dependency @backstage/plugin-catalog-backend-module-unprocessed to v0.6.11 - abandoned#51

Open
mend-on-mend[bot] wants to merge 1 commit into
mainfrom
whitesource-remediate/npm-backstage-plugin-catalog-backend-module-unprocessed-vulnerability
Open

Update dependency @backstage/plugin-catalog-backend-module-unprocessed to v0.6.11 - abandoned#51
mend-on-mend[bot] wants to merge 1 commit into
mainfrom
whitesource-remediate/npm-backstage-plugin-catalog-backend-module-unprocessed-vulnerability

Conversation

@mend-on-mend

@mend-on-mend mend-on-mend Bot commented May 7, 2026

Copy link
Copy Markdown

This PR contains the following updates:

Package Change Age Confidence
@backstage/plugin-catalog-backend-module-unprocessed (source) 0.6.10.6.11 age confidence

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

CVE-2026-44374 / GHSA-p7g9-rp3g-mgfg

More information

Details

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.

Severity

  • CVSS Score: 4.3 / 10 (Medium)
  • Vector String: CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:N/A:N

References

This data is provided by OSV and the GitHub Advisory Database (CC-BY 4.0).


Release Notes

backstage/backstage (@​backstage/plugin-catalog-backend-module-unprocessed)

v0.6.11

Compare Source

Patch Changes

v0.6.10

Compare Source

Patch Changes

v0.6.9

Compare Source

Patch Changes

v0.6.8

Compare Source

Patch Changes

v0.6.7

Compare Source

Patch Changes

v0.6.6

Compare Source

Patch Changes

v0.6.5

Compare Source

Patch Changes

v0.6.4

Compare Source

Patch Changes

v0.6.3

Compare Source

Patch Changes

v0.6.2

Compare Source

Patch Changes

Configuration

📅 Schedule: (UTC)

  • Branch creation
    • ""
  • Automerge
    • At any time (no schedule defined)

🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.

Rebasing: Whenever PR is behind base branch, or you tick the rebase/retry checkbox.

🔕 Ignore: Close this PR and you won't be reminded about these updates again.


  • If you want to rebase/retry this PR, check this box

…d to v0.6.11

Signed-off-by: mend-on-mend[bot] <mend-on-mend[bot]@users.noreply.github.com>
@mend-on-mend

mend-on-mend Bot commented May 7, 2026

Copy link
Copy Markdown
Author

Edited/Blocked Notification

Renovate will not automatically rebase this PR, because it does not recognize the last commit author and assumes somebody else may have edited the PR.

You can manually request rebase by checking the rebase/retry box above.

⚠️ Warning: custom changes will be lost.

@mend-on-mend mend-on-mend Bot changed the title Update dependency @backstage/plugin-catalog-backend-module-unprocessed to v0.6.11 Update dependency @backstage/plugin-catalog-backend-module-unprocessed to v0.6.11 - abandoned Jun 8, 2026
@mend-on-mend

mend-on-mend Bot commented Jun 8, 2026

Copy link
Copy Markdown
Author

Autoclosing Skipped

This PR has been flagged for autoclosing. However, it is being skipped due to the branch being already modified. Please close/delete it manually or report a bug if you think this is in error.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

0 participants