{"items":[{"id":"NVI-00012156","kind":"vulnerability","title":"Backstage's scaffolder credential handling may allow unintended GitHub authentication fallback","revision":2,"unknowns":["Customer inventory, deployment, reachability and exploitation have not been inspected."],"lifecycle":"active","identifiers":["GHSA-29gx-h2m3-xw44","CVE-2026-106462"],"plain_summary":"GitHub lists this reviewed advisory for @backstage/plugin-scaffolder-backend, @backstage/plugin-scaffolder-backend-module-github, @backstage/plugin-scaffolder-backend-module-gitlab, @backstage/plugin-scaffolder-backend-module-azure, @backstage/plugin-scaffolder-backend-module-bitbucket-cloud. Published version ranges and source prerequisites are shown below; this is not an inspection of a visitor’s application.","review_status":"source_listed","control_topics":[],"public_actions":[{"summary":"Identify the exact component and deployed version, examine the linked publisher’s conditions, and retain evidence of any mitigation.","source_ids":["sr-64525025333ffae578ca909f9b68ba68"],"action_type":"investigate","limitations":"Confirm current vendor support, compatibility and deployment evidence. This report has not tested a fix in your system.","current_supported_target":null}],"schema_version":"1.1.0","source_metrics":[{"kind":"CVSS","as_of":"2026-10-07T18:01:55.000Z","value":"6.4 medium","meaning":"GitHub source severity; exploitability and local consequence require separate evidence.","source_id":"sr-b973dc2d24d31561a6005ca5fc20b208"},{"kind":"EPSS","as_of":"2026-10-31T12:00:27.000Z","value":"0.172%","meaning":"FIRST EPSS model v2026.06.15; exploitation probability over 30 days, percentile 0.06528. Missing scores are unknown.","source_id":"sr-64525025333ffae578ca909f9b68ba68"}],"why_it_matters":"Published affected context helps an owner decide what evidence to gather. This report has not examined your application.","related_sources":[{"id":"sr-b973dc2d24d31561a6005ca5fc20b208","url":"https://github.com/advisories/GHSA-29gx-h2m3-xw44","basis":"vendor_advisory","notes":"GitHub Advisory Database; CC-BY-4.0. Each advisory links its original attribution. Null normalizes fields.","title":"GHSA-29gx-h2m3-xw44","publisher":"GitHub Advisory Database","observed_at":"2026-11-01T00:58:46.232Z"},{"id":"sr-64525025333ffae578ca909f9b68ba68","url":"https://www.first.org/epss/data.html","basis":"official_catalog","notes":"FIRST EPSS; probability of exploitation in the next 30 days, not local compromise. Dataset date/model retained; FIRST services terms apply.","title":"CVE-2026-106462","publisher":"FIRST EPSS","observed_at":"2026-11-01T01:39:43.064Z"}],"affected_context":[{"certainty":"source_listed","source_ids":["sr-b973dc2d24d31561a6005ca5fc20b208"],"technology":"@backstage/plugin-scaffolder-backend","known_exclusions":[],"conditions_summary":"### Impact\n\nScaffolder actions that interact with source control systems may not consistently enforce the intended credential boundaries under certain configurations. An authenticated user could perform operations with broader access than intended.\n\n### Patches\n\n- `@backstage/plugin-scaffolder-backend` version `4.1.0`\n- `@backstage/plugin-scaffolder-backend-module-azure` version `0.2.25`\n- `@backstage/plugin-scaffolder-backend-module-bitbucket-cloud` version `0.3.10`\n- `@backstage/plugin-scaffolder-backend-module-bitbucket-server` version `0.2.25`\n- `@backstage/plugin-scaffolder-backend-module-github` version `0.9.13`\n- `@backstage/plugin-scaffolder-backend-module-gitlab` version `0.11.10`\n\nThe fix introduces a new configuration option that enforces user-provided credentials for supported SCM actions. The new behavior is opt-in for compatibility. After upgrading, set:\n\n```yaml\nscaffolder:\n  requireScmUserCredentials: true\n```\n\nBefore enabling this setting, review and update your templates as described in the software templates documentation referred to below.\n\n### Workarounds\n\nIf you cannot upgrade and enable the setting immediately:\n\n- Restrict who can create Scaffolder tasks and ","public_affected_ranges":["< 4.1.0"]},{"certainty":"source_listed","source_ids":["sr-b973dc2d24d31561a6005ca5fc20b208"],"technology":"@backstage/plugin-scaffolder-backend-module-github","known_exclusions":[],"conditions_summary":"### Impact\n\nScaffolder actions that interact with source control systems may not consistently enforce the intended credential boundaries under certain configurations. An authenticated user could perform operations with broader access than intended.\n\n### Patches\n\n- `@backstage/plugin-scaffolder-backend` version `4.1.0`\n- `@backstage/plugin-scaffolder-backend-module-azure` version `0.2.25`\n- `@backstage/plugin-scaffolder-backend-module-bitbucket-cloud` version `0.3.10`\n- `@backstage/plugin-scaffolder-backend-module-bitbucket-server` version `0.2.25`\n- `@backstage/plugin-scaffolder-backend-module-github` version `0.9.13`\n- `@backstage/plugin-scaffolder-backend-module-gitlab` version `0.11.10`\n\nThe fix introduces a new configuration option that enforces user-provided credentials for supported SCM actions. The new behavior is opt-in for compatibility. After upgrading, set:\n\n```yaml\nscaffolder:\n  requireScmUserCredentials: true\n```\n\nBefore enabling this setting, review and update your templates as described in the software templates documentation referred to below.\n\n### Workarounds\n\nIf you cannot upgrade and enable the setting immediately:\n\n- Restrict who can create Scaffolder tasks and ","public_affected_ranges":["< 0.9.13"]},{"certainty":"source_listed","source_ids":["sr-b973dc2d24d31561a6005ca5fc20b208"],"technology":"@backstage/plugin-scaffolder-backend-module-gitlab","known_exclusions":[],"conditions_summary":"### Impact\n\nScaffolder actions that interact with source control systems may not consistently enforce the intended credential boundaries under certain configurations. An authenticated user could perform operations with broader access than intended.\n\n### Patches\n\n- `@backstage/plugin-scaffolder-backend` version `4.1.0`\n- `@backstage/plugin-scaffolder-backend-module-azure` version `0.2.25`\n- `@backstage/plugin-scaffolder-backend-module-bitbucket-cloud` version `0.3.10`\n- `@backstage/plugin-scaffolder-backend-module-bitbucket-server` version `0.2.25`\n- `@backstage/plugin-scaffolder-backend-module-github` version `0.9.13`\n- `@backstage/plugin-scaffolder-backend-module-gitlab` version `0.11.10`\n\nThe fix introduces a new configuration option that enforces user-provided credentials for supported SCM actions. The new behavior is opt-in for compatibility. After upgrading, set:\n\n```yaml\nscaffolder:\n  requireScmUserCredentials: true\n```\n\nBefore enabling this setting, review and update your templates as described in the software templates documentation referred to below.\n\n### Workarounds\n\nIf you cannot upgrade and enable the setting immediately:\n\n- Restrict who can create Scaffolder tasks and ","public_affected_ranges":["< 0.11.10"]},{"certainty":"source_listed","source_ids":["sr-b973dc2d24d31561a6005ca5fc20b208"],"technology":"@backstage/plugin-scaffolder-backend-module-azure","known_exclusions":[],"conditions_summary":"### Impact\n\nScaffolder actions that interact with source control systems may not consistently enforce the intended credential boundaries under certain configurations. An authenticated user could perform operations with broader access than intended.\n\n### Patches\n\n- `@backstage/plugin-scaffolder-backend` version `4.1.0`\n- `@backstage/plugin-scaffolder-backend-module-azure` version `0.2.25`\n- `@backstage/plugin-scaffolder-backend-module-bitbucket-cloud` version `0.3.10`\n- `@backstage/plugin-scaffolder-backend-module-bitbucket-server` version `0.2.25`\n- `@backstage/plugin-scaffolder-backend-module-github` version `0.9.13`\n- `@backstage/plugin-scaffolder-backend-module-gitlab` version `0.11.10`\n\nThe fix introduces a new configuration option that enforces user-provided credentials for supported SCM actions. The new behavior is opt-in for compatibility. After upgrading, set:\n\n```yaml\nscaffolder:\n  requireScmUserCredentials: true\n```\n\nBefore enabling this setting, review and update your templates as described in the software templates documentation referred to below.\n\n### Workarounds\n\nIf you cannot upgrade and enable the setting immediately:\n\n- Restrict who can create Scaffolder tasks and ","public_affected_ranges":["< 0.2.25"]},{"certainty":"source_listed","source_ids":["sr-b973dc2d24d31561a6005ca5fc20b208"],"technology":"@backstage/plugin-scaffolder-backend-module-bitbucket-cloud","known_exclusions":[],"conditions_summary":"### Impact\n\nScaffolder actions that interact with source control systems may not consistently enforce the intended credential boundaries under certain configurations. An authenticated user could perform operations with broader access than intended.\n\n### Patches\n\n- `@backstage/plugin-scaffolder-backend` version `4.1.0`\n- `@backstage/plugin-scaffolder-backend-module-azure` version `0.2.25`\n- `@backstage/plugin-scaffolder-backend-module-bitbucket-cloud` version `0.3.10`\n- `@backstage/plugin-scaffolder-backend-module-bitbucket-server` version `0.2.25`\n- `@backstage/plugin-scaffolder-backend-module-github` version `0.9.13`\n- `@backstage/plugin-scaffolder-backend-module-gitlab` version `0.11.10`\n\nThe fix introduces a new configuration option that enforces user-provided credentials for supported SCM actions. The new behavior is opt-in for compatibility. After upgrading, set:\n\n```yaml\nscaffolder:\n  requireScmUserCredentials: true\n```\n\nBefore enabling this setting, review and update your templates as described in the software templates documentation referred to below.\n\n### Workarounds\n\nIf you cannot upgrade and enable the setting immediately:\n\n- Restrict who can create Scaffolder tasks and ","public_affected_ranges":["< 0.3.10"]},{"certainty":"source_listed","source_ids":["sr-b973dc2d24d31561a6005ca5fc20b208"],"technology":"@backstage/plugin-scaffolder-backend-module-bitbucket-server","known_exclusions":[],"conditions_summary":"### Impact\n\nScaffolder actions that interact with source control systems may not consistently enforce the intended credential boundaries under certain configurations. An authenticated user could perform operations with broader access than intended.\n\n### Patches\n\n- `@backstage/plugin-scaffolder-backend` version `4.1.0`\n- `@backstage/plugin-scaffolder-backend-module-azure` version `0.2.25`\n- `@backstage/plugin-scaffolder-backend-module-bitbucket-cloud` version `0.3.10`\n- `@backstage/plugin-scaffolder-backend-module-bitbucket-server` version `0.2.25`\n- `@backstage/plugin-scaffolder-backend-module-github` version `0.9.13`\n- `@backstage/plugin-scaffolder-backend-module-gitlab` version `0.11.10`\n\nThe fix introduces a new configuration option that enforces user-provided credentials for supported SCM actions. The new behavior is opt-in for compatibility. After upgrading, set:\n\n```yaml\nscaffolder:\n  requireScmUserCredentials: true\n```\n\nBefore enabling this setting, review and update your templates as described in the software templates documentation referred to below.\n\n### Workarounds\n\nIf you cannot upgrade and enable the setting immediately:\n\n- Restrict who can create Scaffolder tasks and ","public_affected_ranges":["< 0.2.25"]}],"null_published_at":"2026-11-01T22:58:19.136Z","source_updated_at":"2026-10-07T18:01:55.000Z","source_disclosed_at":"2026-10-07T18:01:53.000Z","is_synthetic_fixture":false,"null_last_reviewed_at":null,"public_change_summary":"Dated EPSS estimate updated; this is not a new disclosure or proof of exploitation.","null_first_observed_at":"2026-11-01T00:58:46.232Z"},{"id":"NVI-00012156","kind":"vulnerability","title":"Backstage's scaffolder credential handling may allow unintended GitHub authentication fallback","revision":1,"unknowns":["Customer inventory, deployment, reachability and exploitation have not been inspected."],"lifecycle":"active","identifiers":["GHSA-29gx-h2m3-xw44","CVE-2026-106462"],"plain_summary":"GitHub lists this reviewed advisory for @backstage/plugin-scaffolder-backend, @backstage/plugin-scaffolder-backend-module-github, @backstage/plugin-scaffolder-backend-module-gitlab, @backstage/plugin-scaffolder-backend-module-azure, @backstage/plugin-scaffolder-backend-module-bitbucket-cloud. Published version ranges and source prerequisites are shown below; this is not an inspection of a visitor’s application.","review_status":"source_listed","control_topics":[],"public_actions":[{"summary":"Identify the exact component and deployed version, examine the linked publisher’s conditions, and retain evidence of any mitigation.","source_ids":["sr-b973dc2d24d31561a6005ca5fc20b208"],"action_type":"investigate","limitations":"Confirm current vendor support, compatibility and deployment evidence. This report has not tested a fix in your system.","current_supported_target":null}],"schema_version":"1.1.0","source_metrics":[{"kind":"CVSS","as_of":"2026-10-07T18:01:55.000Z","value":"6.4 medium","meaning":"GitHub source severity; exploitability and local consequence require separate evidence.","source_id":"sr-b973dc2d24d31561a6005ca5fc20b208"}],"why_it_matters":"Published affected context helps an owner decide what evidence to gather. This report has not examined your application.","related_sources":[{"id":"sr-b973dc2d24d31561a6005ca5fc20b208","url":"https://github.com/advisories/GHSA-29gx-h2m3-xw44","basis":"vendor_advisory","notes":"GitHub Advisory Database; CC-BY-4.0. Each advisory links its original attribution. Null normalizes fields.","title":"GHSA-29gx-h2m3-xw44","publisher":"GitHub Advisory Database","observed_at":"2026-11-01T00:58:46.232Z"}],"affected_context":[{"certainty":"source_listed","source_ids":["sr-b973dc2d24d31561a6005ca5fc20b208"],"technology":"@backstage/plugin-scaffolder-backend","known_exclusions":[],"conditions_summary":"### Impact\n\nScaffolder actions that interact with source control systems may not consistently enforce the intended credential boundaries under certain configurations. An authenticated user could perform operations with broader access than intended.\n\n### Patches\n\n- `@backstage/plugin-scaffolder-backend` version `4.1.0`\n- `@backstage/plugin-scaffolder-backend-module-azure` version `0.2.25`\n- `@backstage/plugin-scaffolder-backend-module-bitbucket-cloud` version `0.3.10`\n- `@backstage/plugin-scaffolder-backend-module-bitbucket-server` version `0.2.25`\n- `@backstage/plugin-scaffolder-backend-module-github` version `0.9.13`\n- `@backstage/plugin-scaffolder-backend-module-gitlab` version `0.11.10`\n\nThe fix introduces a new configuration option that enforces user-provided credentials for supported SCM actions. The new behavior is opt-in for compatibility. After upgrading, set:\n\n```yaml\nscaffolder:\n  requireScmUserCredentials: true\n```\n\nBefore enabling this setting, review and update your templates as described in the software templates documentation referred to below.\n\n### Workarounds\n\nIf you cannot upgrade and enable the setting immediately:\n\n- Restrict who can create Scaffolder tasks and ","public_affected_ranges":["< 4.1.0"]},{"certainty":"source_listed","source_ids":["sr-b973dc2d24d31561a6005ca5fc20b208"],"technology":"@backstage/plugin-scaffolder-backend-module-github","known_exclusions":[],"conditions_summary":"### Impact\n\nScaffolder actions that interact with source control systems may not consistently enforce the intended credential boundaries under certain configurations. An authenticated user could perform operations with broader access than intended.\n\n### Patches\n\n- `@backstage/plugin-scaffolder-backend` version `4.1.0`\n- `@backstage/plugin-scaffolder-backend-module-azure` version `0.2.25`\n- `@backstage/plugin-scaffolder-backend-module-bitbucket-cloud` version `0.3.10`\n- `@backstage/plugin-scaffolder-backend-module-bitbucket-server` version `0.2.25`\n- `@backstage/plugin-scaffolder-backend-module-github` version `0.9.13`\n- `@backstage/plugin-scaffolder-backend-module-gitlab` version `0.11.10`\n\nThe fix introduces a new configuration option that enforces user-provided credentials for supported SCM actions. The new behavior is opt-in for compatibility. After upgrading, set:\n\n```yaml\nscaffolder:\n  requireScmUserCredentials: true\n```\n\nBefore enabling this setting, review and update your templates as described in the software templates documentation referred to below.\n\n### Workarounds\n\nIf you cannot upgrade and enable the setting immediately:\n\n- Restrict who can create Scaffolder tasks and ","public_affected_ranges":["< 0.9.13"]},{"certainty":"source_listed","source_ids":["sr-b973dc2d24d31561a6005ca5fc20b208"],"technology":"@backstage/plugin-scaffolder-backend-module-gitlab","known_exclusions":[],"conditions_summary":"### Impact\n\nScaffolder actions that interact with source control systems may not consistently enforce the intended credential boundaries under certain configurations. An authenticated user could perform operations with broader access than intended.\n\n### Patches\n\n- `@backstage/plugin-scaffolder-backend` version `4.1.0`\n- `@backstage/plugin-scaffolder-backend-module-azure` version `0.2.25`\n- `@backstage/plugin-scaffolder-backend-module-bitbucket-cloud` version `0.3.10`\n- `@backstage/plugin-scaffolder-backend-module-bitbucket-server` version `0.2.25`\n- `@backstage/plugin-scaffolder-backend-module-github` version `0.9.13`\n- `@backstage/plugin-scaffolder-backend-module-gitlab` version `0.11.10`\n\nThe fix introduces a new configuration option that enforces user-provided credentials for supported SCM actions. The new behavior is opt-in for compatibility. After upgrading, set:\n\n```yaml\nscaffolder:\n  requireScmUserCredentials: true\n```\n\nBefore enabling this setting, review and update your templates as described in the software templates documentation referred to below.\n\n### Workarounds\n\nIf you cannot upgrade and enable the setting immediately:\n\n- Restrict who can create Scaffolder tasks and ","public_affected_ranges":["< 0.11.10"]},{"certainty":"source_listed","source_ids":["sr-b973dc2d24d31561a6005ca5fc20b208"],"technology":"@backstage/plugin-scaffolder-backend-module-azure","known_exclusions":[],"conditions_summary":"### Impact\n\nScaffolder actions that interact with source control systems may not consistently enforce the intended credential boundaries under certain configurations. An authenticated user could perform operations with broader access than intended.\n\n### Patches\n\n- `@backstage/plugin-scaffolder-backend` version `4.1.0`\n- `@backstage/plugin-scaffolder-backend-module-azure` version `0.2.25`\n- `@backstage/plugin-scaffolder-backend-module-bitbucket-cloud` version `0.3.10`\n- `@backstage/plugin-scaffolder-backend-module-bitbucket-server` version `0.2.25`\n- `@backstage/plugin-scaffolder-backend-module-github` version `0.9.13`\n- `@backstage/plugin-scaffolder-backend-module-gitlab` version `0.11.10`\n\nThe fix introduces a new configuration option that enforces user-provided credentials for supported SCM actions. The new behavior is opt-in for compatibility. After upgrading, set:\n\n```yaml\nscaffolder:\n  requireScmUserCredentials: true\n```\n\nBefore enabling this setting, review and update your templates as described in the software templates documentation referred to below.\n\n### Workarounds\n\nIf you cannot upgrade and enable the setting immediately:\n\n- Restrict who can create Scaffolder tasks and ","public_affected_ranges":["< 0.2.25"]},{"certainty":"source_listed","source_ids":["sr-b973dc2d24d31561a6005ca5fc20b208"],"technology":"@backstage/plugin-scaffolder-backend-module-bitbucket-cloud","known_exclusions":[],"conditions_summary":"### Impact\n\nScaffolder actions that interact with source control systems may not consistently enforce the intended credential boundaries under certain configurations. An authenticated user could perform operations with broader access than intended.\n\n### Patches\n\n- `@backstage/plugin-scaffolder-backend` version `4.1.0`\n- `@backstage/plugin-scaffolder-backend-module-azure` version `0.2.25`\n- `@backstage/plugin-scaffolder-backend-module-bitbucket-cloud` version `0.3.10`\n- `@backstage/plugin-scaffolder-backend-module-bitbucket-server` version `0.2.25`\n- `@backstage/plugin-scaffolder-backend-module-github` version `0.9.13`\n- `@backstage/plugin-scaffolder-backend-module-gitlab` version `0.11.10`\n\nThe fix introduces a new configuration option that enforces user-provided credentials for supported SCM actions. The new behavior is opt-in for compatibility. After upgrading, set:\n\n```yaml\nscaffolder:\n  requireScmUserCredentials: true\n```\n\nBefore enabling this setting, review and update your templates as described in the software templates documentation referred to below.\n\n### Workarounds\n\nIf you cannot upgrade and enable the setting immediately:\n\n- Restrict who can create Scaffolder tasks and ","public_affected_ranges":["< 0.3.10"]},{"certainty":"source_listed","source_ids":["sr-b973dc2d24d31561a6005ca5fc20b208"],"technology":"@backstage/plugin-scaffolder-backend-module-bitbucket-server","known_exclusions":[],"conditions_summary":"### Impact\n\nScaffolder actions that interact with source control systems may not consistently enforce the intended credential boundaries under certain configurations. An authenticated user could perform operations with broader access than intended.\n\n### Patches\n\n- `@backstage/plugin-scaffolder-backend` version `4.1.0`\n- `@backstage/plugin-scaffolder-backend-module-azure` version `0.2.25`\n- `@backstage/plugin-scaffolder-backend-module-bitbucket-cloud` version `0.3.10`\n- `@backstage/plugin-scaffolder-backend-module-bitbucket-server` version `0.2.25`\n- `@backstage/plugin-scaffolder-backend-module-github` version `0.9.13`\n- `@backstage/plugin-scaffolder-backend-module-gitlab` version `0.11.10`\n\nThe fix introduces a new configuration option that enforces user-provided credentials for supported SCM actions. The new behavior is opt-in for compatibility. After upgrading, set:\n\n```yaml\nscaffolder:\n  requireScmUserCredentials: true\n```\n\nBefore enabling this setting, review and update your templates as described in the software templates documentation referred to below.\n\n### Workarounds\n\nIf you cannot upgrade and enable the setting immediately:\n\n- Restrict who can create Scaffolder tasks and ","public_affected_ranges":["< 0.2.25"]}],"null_published_at":"2026-11-01T01:04:01.248Z","source_updated_at":"2026-10-07T18:01:55.000Z","source_disclosed_at":"2026-10-07T18:01:53.000Z","is_synthetic_fixture":false,"null_last_reviewed_at":null,"public_change_summary":"First indexed by Null; source disclosure date is shown separately.","null_first_observed_at":"2026-11-01T00:58:46.232Z"}],"next_cursor":null,"snapshot_revision":"42594"}