@backstage/plugin-scaffolder-backend@0.0.0-nightly-20260825023435

The Backstage backend plugin that helps you create new things

Direct Vulnerabilities

Known vulnerabilities in the @backstage/plugin-scaffolder-backend package. This does not include vulnerabilities belonging to this package’s dependencies.

Fix vulnerabilities automatically

Snyk's AI Trust Platform automatically finds the best upgrade path and integrates with your development workflows. Secure your code at zero cost.

Fix for free
VulnerabilityVulnerable Version
  • H
Improper Handling of Case Sensitivity

@backstage/plugin-scaffolder-backend is a The Backstage backend plugin that helps you create new things

Affected versions of this package are vulnerable to Improper Handling of Case Sensitivity via isActionAuthorized in NunjucksWorkflowRunner.ts, where numeric or numeric-string values supplied as the path input to group-related scaffolder actions bypass permission condition checks. An authenticated attacker can pass a numeric path value to a group action, causing the authorization logic to skip evaluation of HAS_STRING_PROPERTY conditions and grant access that should be denied by the configured permission policy.

How to fix Improper Handling of Case Sensitivity?

Upgrade @backstage/plugin-scaffolder-backend to version 3.3.1, 3.4.1, 4.0.3, 4.1.0 or higher.

<3.3.1>=3.4.0 <3.4.1>=4.0.0 <4.0.3>=4.0.4 <4.1.0
  • H
Insertion of Sensitive Information into Log File

@backstage/plugin-scaffolder-backend is a The Backstage backend plugin that helps you create new things

Affected versions of this package are vulnerable to Insertion of Sensitive Information into Log File via the NunjucksWorkflowRunner in plugins/scaffolder-backend/src/scaffolder/tasks/NunjucksWorkflowRunner.ts, where a denied scaffolder action causes the runner to throw a NotAllowedError that includes the full serialized action input in the error message. An authenticated attacker who triggers an unauthorized action can read the complete input object - which may contain secrets, tokens, or other sensitive configuration - from the resulting error response.

How to fix Insertion of Sensitive Information into Log File?

Upgrade @backstage/plugin-scaffolder-backend to version 4.1.0 or higher.

<4.1.0
  • M
Incorrect Authorization

@backstage/plugin-scaffolder-backend is a The Backstage backend plugin that helps you create new things

Affected versions of this package are vulnerable to Incorrect Authorization via SCM scaffolder actions in bitbucketServer.ts and related action files, where the actions fall back to server-side integration credentials when no user-supplied token is provided. An authenticated attacker can trigger SCM operations (repository creation, pull request creation, and similar actions) that execute under the server's privileged integration credentials rather than the user's own credentials, allowing privilege escalation across SCM resources. This affects all SCM provider modules in the scaffolder backend, including Bitbucket Server, Bitbucket Cloud, Azure DevOps, and GitHub.

How to fix Incorrect Authorization?

Upgrade @backstage/plugin-scaffolder-backend to version 4.1.0 or higher.

<4.1.0
  • M
Incorrect Authorization

@backstage/plugin-scaffolder-backend is a The Backstage backend plugin that helps you create new things

Affected versions of this package are vulnerable to Incorrect Authorization via the getAuthorizeConditions function in checkPermissions.ts, which fails to enforce DENY authorization decisions when evaluating scaffolder task read permissions. An authenticated attacker can read scaffolder tasks that they have been explicitly denied access to, because the function only handles CONDITIONAL results and silently allows access when the authorization result is DENY.

How to fix Incorrect Authorization?

Upgrade @backstage/plugin-scaffolder-backend to version 4.1.0 or higher.

<4.1.0
  • M
Information Exposure

@backstage/plugin-scaffolder-backend is a The Backstage backend plugin that helps you create new things

Affected versions of this package are vulnerable to Information Exposure via the task list ordering parameter in the scaffolder backend router, where an authenticated user can supply an arbitrary field name as the order query parameter when listing scaffolder tasks. Because the field value is not validated against an allowlist before being used in a database query, this allows an attacker to probe internal database schema details through error responses or ordering behavior, resulting in unauthorized disclosure of sensitive information.

How to fix Information Exposure?

Upgrade @backstage/plugin-scaffolder-backend to version 4.1.0 or higher.

<4.1.0
  • M
Insertion of Sensitive Information into Log File

@backstage/plugin-scaffolder-backend is a The Backstage backend plugin that helps you create new things

Affected versions of this package are vulnerable to Insertion of Sensitive Information into Log File via the NunjucksWorkflowRunner in NunjucksWorkflowRunner.ts, where secret values interpolated into each iteration contexts are not redacted from task logs. When a workflow step uses the each construct and secrets are present in the template context, the resolved iteration values derived from those secrets are written to the task log in plaintext, allowing an attacker with access to task logs to recover secret material. The fix introduces a pre-iteration render pass without secrets to identify secret-derived values and register them as redactions before any logging occurs.

How to fix Insertion of Sensitive Information into Log File?

Upgrade @backstage/plugin-scaffolder-backend to version 4.1.0 or higher.

<4.1.0
  • M
Insertion of Sensitive Information into Log File

@backstage/plugin-scaffolder-backend is a The Backstage backend plugin that helps you create new things

Affected versions of this package are vulnerable to Insertion of Sensitive Information into Log File via the collectSecretRedactions function in NunjucksWorkflowRunner.ts, which fails to redact secret values from task step logs under certain conditions. The logger is initialised after an early-exit check, meaning secrets are not registered for redaction when a task is cancelled or encounters an error before the logger is created. Additionally, the diffing logic in collectSecretRedactions compares object entries by index rather than by key, causing secret-influenced values to be missed when the rendered object's key order differs between the secrets-present and secrets-absent renders, allowing secret values to appear in plain text in scaffolder task logs.

How to fix Insertion of Sensitive Information into Log File?

Upgrade @backstage/plugin-scaffolder-backend to version 4.1.0 or higher.

<4.1.0
  • C
Race Condition

@backstage/plugin-scaffolder-backend is a The Backstage backend plugin that helps you create new things

Affected versions of this package are vulnerable to Race Condition via the retryTask method in DatabaseTaskStore.ts, where a task retry operation is performed without first validating that the task is in a terminal state. An authenticated attacker can trigger a retry on a task that is currently open or processing, causing the task's status to be reset to open and its event history to be manipulated, potentially leading to unauthorized re-execution of scaffolder tasks with elevated privileges and full confidentiality, integrity, and availability impact on downstream systems.

How to fix Race Condition?

Upgrade @backstage/plugin-scaffolder-backend to version 3.3.1, 3.4.1, 4.0.3, 4.1.0 or higher.

<3.3.1>=3.4.0 <3.4.1>=4.0.0 <4.0.3>=4.0.4 <4.1.0
  • C
Insertion of Sensitive Information Into Sent Data

@backstage/plugin-scaffolder-backend is a The Backstage backend plugin that helps you create new things

Affected versions of this package are vulnerable to Insertion of Sensitive Information Into Sent Data via the task serialization logic in router.ts, which previously included secrets and state fields in API responses for task retrieval endpoints. An authenticated attacker can read task secrets - such as credentials or tokens stored in scaffolder task context - by querying the task list or task detail endpoints, as these fields were included in the serialized response without being stripped.

How to fix Insertion of Sensitive Information Into Sent Data?

Upgrade @backstage/plugin-scaffolder-backend to version 3.3.1, 3.4.1, 4.0.3, 4.1.0 or higher.

<3.3.1>=3.4.0 <3.4.1>=4.0.0 <4.0.3>=4.0.4 <4.1.0
  • L
Insertion of Sensitive Information into Log File

@backstage/plugin-scaffolder-backend is a The Backstage backend plugin that helps you create new things

Affected versions of this package are vulnerable to Insertion of Sensitive Information into Log File via the log redaction mechanism in task event logs. An attacker can access sensitive session tokens by registering a malicious template in the catalog and having a victim execute it.

How to fix Insertion of Sensitive Information into Log File?

Upgrade @backstage/plugin-scaffolder-backend to version 3.1.4 or higher.

<3.1.4
  • H
Symlink Attack

@backstage/plugin-scaffolder-backend is a The Backstage backend plugin that helps you create new things

Affected versions of this package are vulnerable to Symlink Attack via multiple actions, including debug:log, fs:delete, and archive extraction. A user who create and execute Scaffolder templates can read, delete, or write arbitrary files outside the intended workspace.

How to fix Symlink Attack?

Upgrade @backstage/plugin-scaffolder-backend to version 2.2.2, 3.0.2, 3.1.1 or higher.

<2.2.2>=3.0.0-next.0 <3.0.2>=3.1.0-next.0 <3.1.1
  • L
Insertion of Sensitive Information into Log File

@backstage/plugin-scaffolder-backend is a The Backstage backend plugin that helps you create new things

Affected versions of this package are vulnerable to Insertion of Sensitive Information into Log File via the fetch:template action, which duplicates logging of the input values. An attacker can access sensitive information by reviewing logs where secrets may not have been properly redacted.

Note: This is only exploitable if ${{ secrets.x }} are passed as arguments to fetch:template.

How to fix Insertion of Sensitive Information into Log File?

Upgrade @backstage/plugin-scaffolder-backend to version 2.1.1 or higher.

<2.1.1
  • H
Arbitrary Code Injection

@backstage/plugin-scaffolder-backend is a The Backstage backend plugin that helps you create new things

Affected versions of this package are vulnerable to Arbitrary Code Injection due to the usage of insecure sandbox plugin. Exploiting this vulnerability is possible by an attacker with write access to a registered scaffolder template, and it allows manipulation of the template in a way that allows remote code execution.

Note: This was only exploitable in the template YAML definition itself and not by user input data.

How to fix Arbitrary Code Injection?

Upgrade @backstage/plugin-scaffolder-backend to version 1.15.0 or higher.

<1.15.0