@backstage/plugin-auth-backend-module-cloudflare-access-provider
Affected
- introduced
0.1.0, fixed0.5.0(semver)
Fixed versions
0.5.0
Fix
- Fixed version
0.5.0npm install @backstage/[email protected]
Advisory
Also known as: CVE-2026-106457
Backstage: Insufficient audience validation in the Cloudflare Access auth provider
Impact
The Cloudflare Access auth provider verifies a token'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's audience already being enforced upstream.
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.
A successful sign-in also depends on the deployment's sign-in resolver mapping the presented identity to a Backstage user. The resulting impact depends on the permissions assigned to that identity.
Patches
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.
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:
auth:
providers:
cfaccess:
teamName: example
audience: ${AUTH_CFACCESS_AUDIENCE}
Workarounds
Medium Basis: The source's own band: MODERATE
0.1.0, fixed 0.5.0 (semver)0.5.0
0.5.0npm install @backstage/[email protected]Fix commands are the export's own generic commands. Ojuju never runs them. Check them against your setup first.
Check your own computer: guard packages check
Source: GitHub Advisory Database (reviewed advisories) · CC BY 4.0