Skip to main content
Vulnerability Database/CVE-2026-106492

CVE-2026-106492: Backstage Privilege Escalation Vulnerability

CVE-2026-106492 is a privilege escalation vulnerability in Backstage that allows restricted service credentials to bypass access controls through plugin delegation. This post covers technical details, affected versions, impact, and mitigation steps.

Published:

Disclaimer: This content was generated using AI. While we strive for accuracy, please verify critical information with official sources.

Sources: National Vulnerability Database, CISA KEV, Exploit-DB

CVE-2026-106492 Overview

Backstage, the open framework for building developer portals, contains an access control flaw in the @backstage/backend-defaults package. Prior to versions 0.16.1 and 0.17.8, external service credentials configured with access restrictions (such as read-only) could bypass those restrictions when requests were routed through plugin delegation paths. A restricted service could perform operations outside its intended scope, including write operations against plugins it should only be able to read. The vulnerability is tracked under CWE-269: Improper Privilege Management and resolved in the referenced patch releases.

Critical Impact

Authenticated services with restricted credentials can elevate their effective permissions by delegating calls through plugin paths, undermining least-privilege controls in Backstage backends.

Affected Products

  • Backstage @backstage/backend-defaults prior to 0.16.1
  • Backstage @backstage/backend-defaults prior to 0.17.8
  • Backstage monorepo releases prior to v1.49.6 and v1.54.6

Discovery Timeline

  • 2026-10-06 - CVE-2026-106492 published to NVD
  • 2026-10-07 - Last updated in NVD database

Technical Details for CVE-2026-106492

Vulnerability Analysis

Backstage supports external service-to-service authentication where each external credential can be issued with an accessRestrictions policy. The policy binds a subject to a specific set of plugins and HTTP methods, enabling patterns such as read-only integrations.

The flaw lives in the credential delegation layer of @backstage/backend-defaults. When one plugin calls another on behalf of a service principal, the delegation flow preserved the subject identity but did not consistently reapply the original credential's full access restriction map. The downstream plugin evaluated the request against its own context, effectively dropping restrictions that should have followed the principal across hops.

An attacker controlling a restricted service token can therefore invoke write-capable endpoints on a target plugin by routing the request through an intermediate plugin that delegates the call. The result is privilege escalation across the Backstage backend plugin graph.

Root Cause

The root cause is improper preservation of access restrictions during service credential delegation in DefaultAuthService and ExternalAuthTokenHandler. The handler returned a subject with only the plugin-scoped accessRestrictions, omitting the full AccessRestrictionsMap needed by downstream plugins to enforce the same policy. This is a classic [CWE-269] privilege management defect.

Attack Vector

Exploitation requires network access to a Backstage backend and a valid external service credential with any level of configured access. The attacker uses the restricted token to call a plugin endpoint that performs a delegated request to another plugin, then performs an operation that the original credential should have been denied.

typescript
// Patch excerpt: packages/backend-defaults/src/entrypoints/auth/DefaultAuthService.ts
  BackstageServicePrincipal,
  BackstageUserPrincipal,
} from '@backstage/backend-plugin-api';
-import { AuthenticationError } from '@backstage/errors';
+import { AuthenticationError, NotAllowedError } from '@backstage/errors';
 import { JsonObject } from '@backstage/types';
 import { decodeJwt } from 'jose';
 import { ExternalAuthTokenHandler } from './external/ExternalAuthTokenHandler';

// Patch excerpt: packages/backend-defaults/src/entrypoints/auth/external/ExternalAuthTokenHandler.ts
    | {
        subject: string;
        accessRestrictions?: BackstagePrincipalAccessRestrictions;
+       allAccessRestrictions?: AccessRestrictionsMap;
      }
    | undefined
  > {

Source: Backstage commit 40346245 and Backstage commit bc80ffda. The fix introduces allAccessRestrictions so the full restriction map travels with the principal, and raises NotAllowedError when a delegated call violates the originating credential's policy.

Detection Methods for CVE-2026-106492

Indicators of Compromise

  • Audit log entries showing an external service subject performing write operations against a plugin where its configured accessRestrictions permit only read access.
  • Requests from the same external service identity hitting multiple plugins in rapid succession via internal delegation endpoints.
  • Unexpected mutations in catalog, scaffolder, or TechDocs plugins attributed to automation accounts without a corresponding user principal.

Detection Strategies

  • Compare the configured accessRestrictions map for each external service in app-config.yaml against actual request patterns in Backstage backend logs.
  • Alert on any 2xx response for POST, PUT, PATCH, or DELETE methods issued by a service principal whose configured policy is read-only.
  • Review plugin-to-plugin delegation chains for calls that originate from external service tokens and terminate at state-changing handlers.

Monitoring Recommendations

  • Enable verbose auth logging in @backstage/backend-defaults to capture subject and target plugin for every authenticated request.
  • Forward Backstage backend logs to a central analytics platform and build dashboards keyed on service principal, HTTP method, and target plugin.
  • Track the version of @backstage/backend-defaults in use across environments and flag deployments still running pre-0.16.1 or pre-0.17.8 builds.

How to Mitigate CVE-2026-106492

Immediate Actions Required

  • Upgrade @backstage/backend-defaults to 0.16.1 or 0.17.8, or move to Backstage release v1.49.6 or v1.54.6.
  • Inventory all external service credentials and rotate any token whose restrictions may have been bypassed.
  • Review audit logs for the window between credential issuance and patch deployment to identify suspicious delegated writes.

Patch Information

The fix is published in Backstage release v1.49.6 and Backstage release v1.54.6. Technical details and coordinated disclosure notes are available in GitHub Security Advisory GHSA-cq7v-rfgc-5c7v.

Workarounds

  • Temporarily revoke external service credentials that rely on accessRestrictions for least-privilege enforcement until the patched version is deployed.
  • Place a reverse proxy in front of Backstage that enforces per-token method and path allowlists independent of application-layer checks.
  • Disable plugins that expose cross-plugin delegation endpoints if they are not required by your deployment.
bash
# Pin patched versions in your Backstage workspace
yarn up @backstage/backend-defaults@^0.17.8

# Verify the installed version
yarn why @backstage/backend-defaults

Disclaimer: This content was generated using AI. While we strive for accuracy, please verify critical information with official sources.

Sources: National Vulnerability Database, CISA KEV, Exploit-DB

Experience the Most Advanced Cybersecurity Platform

See how the world’s most intelligent, autonomous cybersecurity platform can protect your organization today and into the future.