Skip to content

chore(deps): update dependency @backstage/plugin-proxy-backend to v0.6.18 [security] - #93

Open
renovate[bot] wants to merge 1 commit into
mainfrom
renovate/npm-backstage-plugin-proxy-backend-vulnerability
Open

renovate[bot] wants to merge 1 commit into
mainfrom
renovate/npm-backstage-plugin-proxy-backend-vulnerability

Conversation

@renovate

@renovate renovate Bot commented Oct 9, 2026 •

Copy link
Copy Markdown

This PR contains the following updates:

Package Change Age Confidence
@backstage/plugin-proxy-backend (source) 0.6.17 → 0.6.18 age confidence

Warning

Some dependencies could not be looked up. Check the Dependency Dashboard for more information.


Backstage: Inconsistent credential enforcement for overlapping proxy routes

CVE-2026-106456 / GHSA-472h-9c5j-prrr

More information

Details

Impact

An operator can configure overlapping proxy paths with different credential requirements. When a parent path permits unauthenticated access and a nested path requires credentials, the parent exemption can also cover requests handled by the nested proxy. An unauthenticated caller may therefore reach the nested upstream through Backstage, including with static upstream credentials configured for that proxy.

Exploitation requires this specific overlapping route configuration. The resulting confidentiality and integrity impact depends on the capabilities exposed by the nested upstream.

Patches

Upgrade @backstage/plugin-proxy-backend to version 0.6.18 or later. The fixed package is available in Backstage v1.55.0.

Workarounds
  • Avoid nesting a credential-protected proxy path below a path configured with dangerously-allow-unauthenticated.
  • Apply the same credential requirement to overlapping proxy paths.
  • Restrict direct network access to the Backstage backend until the patched package is deployed.

Severity

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

References

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


Backstage: Inconsistent credential enforcement for overlapping proxy routes

CVE-2026-106456 / GHSA-472h-9c5j-prrr

More information

Details

Impact

An operator can configure overlapping proxy paths with different credential requirements. When a parent path permits unauthenticated access and a nested path requires credentials, the parent exemption can also cover requests handled by the nested proxy. An unauthenticated caller may therefore reach the nested upstream through Backstage, including with static upstream credentials configured for that proxy.

Exploitation requires this specific overlapping route configuration. The resulting confidentiality and integrity impact depends on the capabilities exposed by the nested upstream.

Patches

Upgrade @backstage/plugin-proxy-backend to version 0.6.18 or later. The fixed package is available in Backstage v1.55.0.

Workarounds
  • Avoid nesting a credential-protected proxy path below a path configured with dangerously-allow-unauthenticated.
  • Apply the same credential requirement to overlapping proxy paths.
  • Restrict direct network access to the Backstage backend until the patched package is deployed.

Severity

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

References

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


Release Notes

backstage/backstage (@​backstage/plugin-proxy-backend)

v0.6.18

Compare Source

Patch Changes

Configuration

📅 Schedule: (UTC)

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

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

♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.

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


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

This PR was generated by Mend Renovate. View the repository job log.

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