https://vulnerability.circl.lu Contains only the most 10 recent entries. http://www.rssboard.org/rss-specification python-feedgen en Wed, 07 Oct 2026 23:53:17 +0000 https://vulnerability.circl.lu/vuln/fkie_cve-2026-106457 <p>Backstage is an open framework for building developer portals. From 0.1.0 until 0.5.0, the @backstage/plugin-auth-backend-module-cloudflare-access-provider package is affected by insufficient audience validation in the cloudflare access auth provider. The Cloudflare Access auth provider verifies a token&#39;s signature and team issuer, but affected versions do not verify that the token was issued for the Backstage application. A user holding a valid token for another Access application in the same Cloudflare Zero Trust team may therefore be able to authenticate to Backstage if that token reaches the auth endpoint without the Backstage application&#39;s audience already being enforced upstream. Cloudflare Access normally evaluates the protected application before forwarding requests. This issue is fixed in version 0.5.0.</p> <p>Backstage is an open framework for building developer portals. From 0.1.0 until 0.5.0, the @backstage/plugin-auth-backend-module-cloudflare-access-provider package is affected by insufficient audience validation in the cloudflare access auth provider. The Cloudflare Access auth provider verifies a token&#39;s signature and team issuer, but affected versions do not verify that the token was issued for the Backstage application. A user holding a valid token for another Access application in the same Cloudflare Zero Trust team may therefore be able to authenticate to Backstage if that token reaches the auth endpoint without the Backstage application&#39;s audience already being enforced upstream. Cloudflare Access normally evaluates the protected application before forwarding requests. This issue is fixed in version 0.5.0.</p> https://vulnerability.circl.lu/vuln/fkie_cve-2026-106457 https://vulnerability.circl.lu/vuln/ghsa-q333-f498-w2x7 <p><strong>Affected:</strong> npm: @backstage/plugin-auth-backend-module-cloudflare-access-provider</p> <p>### Impact</p> <p>The Cloudflare Access auth provider verifies a token&#39;s signature and team issuer, but affected versions do not verify that the token was issued for the Backstage application. A user holding a valid token for another Access application in the same Cloudflare Zero Trust team may therefore be able to authenticate to Backstage if that token reaches the auth endpoint without the Backstage application&#39;s audience already being enforced upstream.</p> <p>Cloudflare Access normally evaluates the protected application before forwarding requests. The reported reproduction exercises the provider directly and does not demonstrate bypass through the ordinary Cloudflare-protected Backstage URL. Relevant deployment topologies include direct origin access, alternate routes around the intended Access application, or another proxy forwarding the assertion unchanged.</p> <p>A successful sign-in also depends on the deployment&#39;s sign-in resolver mapping the presented identity to a Backstage user. The resulting impact depends on the permissions assigned to that identity.</p> <p>### Patches</p> <p>Upgrade `@backstage/plugin-auth-backend-module-cloudflare-access-provider` to version `0.5.0` or later. The fixed package is available in [Backstage v1.55.0](https://github.com/backstage/backstage/releases/tag/v1.55.0).</p> <p>This is a breaking configuration change. Before upgrading, set `auth.providers.cfaccess.audience` to the Audience (AUD) tag for the Backstage application in Cloudflare Zero Trust:</p> <p>```yaml auth: pro…</p> <p><strong>Affected:</strong> npm: @backstage/plugin-auth-backend-module-cloudflare-access-provider</p> <p>### Impact</p> <p>The Cloudflare Access auth provider verifies a token&#39;s signature and team issuer, but affected versions do not verify that the token was issued for the Backstage application. A user holding a valid token for another Access application in the same Cloudflare Zero Trust team may therefore be able to authenticate to Backstage if that token reaches the auth endpoint without the Backstage application&#39;s audience already being enforced upstream.</p> <p>Cloudflare Access normally evaluates the protected application before forwarding requests. The reported reproduction exercises the provider directly and does not demonstrate bypass through the ordinary Cloudflare-protected Backstage URL. Relevant deployment topologies include direct origin access, alternate routes around the intended Access application, or another proxy forwarding the assertion unchanged.</p> <p>A successful sign-in also depends on the deployment&#39;s sign-in resolver mapping the presented identity to a Backstage user. The resulting impact depends on the permissions assigned to that identity.</p> <p>### Patches</p> <p>Upgrade `@backstage/plugin-auth-backend-module-cloudflare-access-provider` to version `0.5.0` or later. The fixed package is available in [Backstage v1.55.0](https://github.com/backstage/backstage/releases/tag/v1.55.0).</p> <p>This is a breaking configuration change. Before upgrading, set `auth.providers.cfaccess.audience` to the Audience (AUD) tag for the Backstage application in Cloudflare Zero Trust:</p> <p>```yaml auth: pro…</p> https://vulnerability.circl.lu/vuln/ghsa-q333-f498-w2x7