Skip to content
Heist/ feed
Back to feed
MediumFix available

Backstage: Insufficient audience validation in the Cloudflare Access auth provider

Type: advisorySources: OSV

### 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](https://github.com/backstage/backstage/releases/tag/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: ```yaml auth: providers: cf

Products
@backstage/plugin-auth-backend-module-cloudflare-access-provider
Affected versions
Not specified
Fixed versions
0.5.0
CVEs
CVE-2026-106457
Confirmed fixed CVEs
Not specified
Updated in this feed
28 Oct 2026, 08:47 UTC · Revision 1

Source evidence

Backstage: Insufficient audience validation in the Cloudflare Access auth provider

core-osv · Original source

Published 7 Oct 2026, 20:25 UTC

### 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](https://github.com/backstage/backstage/releases/tag/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: ```yaml auth: providers: cf

osv:GHSA-q333-f498-w2x7

@backstage/plugin-auth-backend-module-cloudflare-access-provider

Fixed versions: 0.5.0

Complete source record
{
  "id": "6223dbde342cd07dd1d2887c9a12eedeb3089fae0d025b374ff5dd863e33d39b",
  "url": "https://osv.dev/vulnerability/GHSA-q333-f498-w2x7",
  "method": "structured",
  "payload": {
    "kind": "advisory",
    "title": "Backstage: Insufficient audience validation in the Cloudflare Access auth provider",
    "summary": "### 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](https://github.com/backstage/backstage/releases/tag/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: ```yaml auth: providers: cf",
    "evidence": "osv:GHSA-q333-f498-w2x7",
    "products": [
      {
        "name": {
          "value": "@backstage/plugin-auth-backend-module-cloudflare-access-provider",
          "evidence": "/affected/0/package/name"
        },
        "prerequisites": [],
        "fixed_versions": [
          {
            "value": "0.5.0",
            "evidence": "/affected/0/ranges"
          }
        ],
        "affected_versions": []
      }
    ],
    "severity": "medium",
    "structured": {
      "id": "GHSA-q333-f498-w2x7",
      "aliases": [
        "CVE-2026-106457",
        "GHSA-q333-f498-w2x7"
      ],
      "metrics": [
        {
          "type": "CVSS_V3",
          "score": "CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:U/C:H/I:H/A:N"
        }
      ],
      "affected": [
        {
          "ranges": [
            {
              "type": "SEMVER",
              "events": [
                {
                  "introduced": "0.1.0"
                },
                {
                  "fixed": "0.5.0"
                }
              ]
            }
          ],
          "package": {
            "name": "@backstage/plugin-auth-backend-module-cloudflare-access-provider",
            "purl": "pkg:npm/%40backstage/plugin-auth-backend-module-cloudflare-access-provider",
            "ecosystem": "npm"
          },
          "database_specific": {
            "source": "https://github.com/github/advisory-database/blob/main/advisories/github-reviewed/2026/10/GHSA-q333-f498-w2x7/GHSA-q333-f498-w2x7.json"
          }
        }
      ],
      "modified": "2026-10-07T20:30:04.832917243Z",
      "provider": "osv",
      "references": [
        "https://github.com/backstage/backstage/security/advisories/GHSA-q333-f498-w2x7",
        "https://nvd.nist.gov/vuln/detail/CVE-2026-106457",
        "https://github.com/backstage/backstage/commit/ed9034cacd9def3b3674f0a764fe992f751e204d",
        "https://github.com/backstage/backstage",
        "https://github.com/backstage/backstage/releases/tag/v1.55.0"
      ],
      "provider_metadata": {
        "cwe_ids": [
          "CWE-287"
        ],
        "severity": "MODERATE",
        "github_reviewed": true,
        "nvd_published_at": "2026-10-06T21:17:16Z",
        "github_reviewed_at": "2026-10-07T20:25:25Z"
      }
    },
    "related_cves": [
      {
        "value": "CVE-2026-106457",
        "evidence": "/aliases"
      }
    ],
    "security_relevant": true,
    "severity_evidence": "/severity/0/score"
  },
  "source_id": "core-osv",
  "document_id": 97227,
  "published_at": "2026-10-07T20:25:25+00:00"
}