Backstage: Improper input validation in Sentry scaffolder actions
Exact source revision recorded 24 Oct 2026 13:17:17 UTC. It does not establish the source's current position. Latest evidence.
osv · GHSA-g734-fhp4-7mfp
Published### Impact An authenticated internal user who can execute the affected actions may cause the backend to contact unintended destinations and disclose Sentry integration credentials. Subsequent impact depends on network reachability and the privileges granted to the configured token. ### Patches Upgrade `@backstage/plugin-scaffolder-backend-module-sentry` to version `0.3.8` or later. The fixed package is available in [Backstage v1.54.8](https://github.com/backstage/backstage/releases/tag/v1.54.8) and [Backstage v1.55.0](https://github.com/backstage/backstage/releases/tag/v1.55.0). The update removes custom action-level `apiBaseUrl` values. Move any such value to `scaffolder.sentry.apiBaseUrl` before upgrading. ### Workarounds - Disable the affected actions until the patched package is deployed. - Restrict `scaffolder.action.execute` permission for the affected Sentry actions to trusted users and templates.
- Source published
- 7 Oct 2026 20:25:01 UTC
- Source modified
- 7 Oct 2026 20:30:04 UTC
- Observed here
- 24 Oct 2026 13:17:17 UTC
- Source terms
- GitHub Advisory Database · CC-BY-4.0
Original source record · Cite this exact observation · Complete original publisher JSON
This view projects the publisher's source fields for reading; the original JSON retains additional fields and CVE enrichment containers. Attribution: osv · GitHub Advisory Database · CC-BY-4.0. Source text is retained; field grouping and change labels are provided by ChangeIntel.
CVSS_V3 · CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:L/A:N
Publisher rating · HIGH