Update dependency @backstage/backend-defaults to ^0.12.0 [SECURITY] #180
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This PR contains the following updates:
^0.10.0→^0.12.0Backstage has a Possible Symlink Path Traversal in Scaffolder Actions
CVE-2026-24046 / GHSA-rq6q-wr2q-7pgp
More information
Details
Impact
Multiple Scaffolder actions and archive extraction utilities were vulnerable to symlink-based path traversal attacks. An attacker with access to create and execute Scaffolder templates could exploit symlinks to:
debug:logaction by creating a symlink pointing to sensitive files (e.g.,/etc/passwd, configuration files, secrets)fs:deleteaction by creating symlinks pointing outside the workspaceThis affects any Backstage deployment where users can create or execute Scaffolder templates.
Patches
This vulnerability is fixed in the following package versions:
@backstage/backend-defaultsversion 0.12.2, 0.13.2, 0.14.1, 0.15.0@backstage/plugin-scaffolder-backendversion 2.2.2, 3.0.2, 3.1.1@backstage/plugin-scaffolder-nodeversion 0.11.2, 0.12.3Users should upgrade to these versions or later.
Workarounds
References
Severity
CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:C/C:H/I:N/A:LReferences
This data is provided by OSV and the GitHub Advisory Database (CC-BY 4.0).
Backstage has a Possible SSRF when reading from allowed URL's in
backend.reading.allowCVE-2026-24048 / GHSA-q2x5-4xjx-c6p9
More information
Details
Impact
The
FetchUrlReadercomponent, used by the catalog and other plugins to fetch content from URLs, followed HTTP redirects automatically. This allowed an attacker who controls a host listed inbackend.reading.allowto redirect requests to internal or sensitive URLs that are not on the allowlist, bypassing the URL allowlist security control.This is a Server-Side Request Forgery (SSRF) vulnerability that could allow access to internal resources, but it does not allow attackers to include additional request headers.
Patches
This vulnerability is fixed in
@backstage/backend-defaultsversion 0.12.2, 0.13.2, 0.14.1, and 0.15.0. Users should upgrade to this version or later.Workarounds
backend.reading.allowto only trusted hosts that you control and that do not issue redirectsReferences
Severity
CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:C/C:L/I:N/A:NReferences
This data is provided by OSV and the GitHub Advisory Database (CC-BY 4.0).
Release Notes
backstage/backstage (@backstage/backend-defaults)
v0.12.2Compare Source
v0.12.1Compare Source
Patch Changes
33bd4d0: Deduplicate discovered features discovered with discoveryFeatureLoader4eda590: Fixed cache namespace and key prefix separator configuration to properly use configured values instead of hardcoded plugin ID. The cache manager now correctly combines the configured namespace with plugin IDs using the configured separator for Redis and Valkey. Memcache and memory store continue to use plugin ID as namespace.f244e61: Addbackend.loggerconfig options to configure theRootLoggerService.Read more about the new configuration options in the
Root Logger Service
documentation.
Updated dependencies
v0.12.0Compare Source
Minor Changes
133519b: feat: new cache managerInfinispan Data GridPatch Changes
caee2eb: Fixed WinstonLogger throwing when redactions were null or undefineded74af5: Fixed bug in PackageDiscoveryService where packages with "exports" field caused ERR_PACKAGE_PATH_NOT_EXPORTED error during backend startup.3a7dad9: Updatedbetter-sqlite3to v12v0.11.1Compare Source
Patch Changes
ead925a: Add a standardtoStringon credentials objectse0189b8: UrlReader: Fix handling of access tokens for GitLab readURL requestsd1e4a6d: Fixed bug where the GitLab user token and GitLab integration token were being merged togetherv0.11.0Compare Source
Minor Changes
3ccb7fc: Enhanced error handling in the auditor service factory to pass errors as objects. Aligned WinstonRootAuditorService with the default service factory's error handling.Patch Changes
1220cf8: Added new rate limit middleware to allow rate limiting requests to the backendIf you are using the
configurecallback of the root HTTP router service and do NOT callapplyDefaults()inside it, please see the relevant changes that were made, to see if you want to apply them as well to your custom configuration.Rate limiting can be turned on by adding the following configuration to
app-config.yaml:Plugin specific rate limiting can be configured by adding the following configuration to
app-config.yaml:c999c25: Added some default implementations for the experimentalActionsServiceandActionsRegistryServiceunder/alphathat allow registration of actions for a particular plugin.Updated dependencies
Configuration
📅 Schedule: Branch creation - "" (UTC), 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.
This PR has been generated by Renovate Bot.