@backstage Backend-defaults vulnerabilities
🔔 Create alert RSS Version checker
Published CVEs affecting @backstage Backend-defaults: 3 record(s), with affected versions and fixes.
CVE-2026-106495
Medium · 4.3
CWE-284 Oct 12, 2026
Backstage: Improper access control in backend action invocation
Backstage is an open framework for building developer portals. Prior to 0.17.8, the @backstage/backend-defaults package is affected by improper access control in backend action invocation. An authenticated user could invoke actions that an operator had excluded through action configuration. Existing action permissions and downstream authorization remain enforced. This issue is fixed in version 0.17.8.
CVE-2026-106494
Medium · 4.4
CWE-22 Oct 6, 2026
Backstage: Improper input validation in cloud storage URL readers
Backstage is an open framework for building developer portals. Prior to 0.17.8, the @backstage/backend-defaults package is affected by improper input validation in cloud storage url readers. An attacker with write access to a cloud storage bucket used by Backstage could craft object names that could collide with protected files in the output directory. In certain deployment configurations, this could lead to content injection. This issue is fixed in version 0.17.8.
CVE-2026-106492
High · 7.6
CWE-269 Oct 6, 2026
Backstage: Improper preservation of access restrictions during service credential delegation
Backstage is an open framework for building developer portals. Prior to 0.16.1 and 0.17.8, the @backstage/backend-defaults package is affected by improper preservation of access restrictions during service credential delegation. An external service credential configured with access restrictions (e.g., read-only) could bypass those restrictions by routing requests through plugin delegation paths. This could allow a restricted service to perform operations beyond its intended scope, including write operations on plugins it was restricted to read-only access for. This issue is fixed in versions 0.16.1 and 0.17.8.