Mardi 6 octobre 2026
12 CVE
-
CVE-2026-106494 4.9 Moyenne
backstage · @backstage backend-defaults · Linuxfoundation backstage\/backend defaults · Linuxfoundation backstage
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-106493 4.1 Moyenne
backstage · @backstage plugin-catalog-backend-module-azure · @backstage plugin-catalog-backend-module-aws · Linuxfoundation backstage
Backstage is an open framework for building developer portals. Prior to 1.54.6, cloud storage catalog providers did not sufficiently validate object paths. A principal able to create or rename objects in a configured Azure Blob Storage or AWS S3 catalog source could cause catalog descriptors to be read from outside the intended storage boundary, limited to locations reachable with the backend's configured credentials. This issue is fixed in 1.54.6.
-
CVE-2026-106492 6.5 Moyenne
backstage · @backstage backend-defaults · Linuxfoundation backstage\/backend-defaults · Linuxfoundation backstage
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.
-
CVE-2026-106491 6.4 Moyenne
backstage · @backstage plugin-proxy-backend · Linuxfoundation backstage\/plugin-proxy-backend · Linuxfoundation backstage
Backstage is an open framework for building developer portals. Prior to 0.6.17, the @backstage/plugin-proxy-backend package is affected by improper input validation in proxy-backend. An authenticated Backstage user could craft a request URL that causes the proxy-backend to forward the request to a path outside the configured base path on the target server. This is limited to target servers already configured as proxy endpoints and requires Backstage authentication by default. This issue is fixed in version 0.6.17.
-
CVE-2026-106490 6.5 Moyenne
backstage · @backstage plugin-techdocs-backend · Linuxfoundation backstage\/plugin-techdocs-backend · Linuxfoundation backstage
Backstage is an open framework for building developer portals. Prior to 2.2.4, the @backstage/plugin-techdocs-backend package is affected by improper input validation in techdocs static content requests. When using the Azure Blob Storage provider, an authenticated Backstage user may be able to read restricted TechDocs content when entity-level permissions are enabled. Deployments that intentionally disable the default backend authentication policy may have broader exposure. This issue is fixed in version 2.2.4.
-
CVE-2026-106489 6.5 Moyenne
backstage · @backstage plugin-techdocs-backend · Linuxfoundation backstage\/plugin-techdocs-backend · Linuxfoundation backstage
Backstage is an open framework for building developer portals. Prior to 2.2.4, the @backstage/plugin-techdocs-backend package is affected by improper authorization enforcement for techdocs static content. An authenticated user with access to one TechDocs documentation site could craft a URL able to read documentation belonging to a different entity. This only affects deployments using the external TechDocs builder with an external storage provider (S3, GCS, etc.) and the permission framework enabled. Instances that do not use the permission framework are unaffected, since TechDocs content is visible to all authenticated users by design. This issue is fixed in version 2.2.4.
-
CVE-2026-106488 8.1 Élevée
backstage · @backstage plugin-auth-backend-module-oidc-provider · Linuxfoundation backstage\/plugin-auth-backend-module-oidc-provider · Linuxfoundation backstage
Backstage is an open framework for building developer portals. Prior to 0.4.20, the @backstage/plugin-auth-backend-module-oidc-provider package is affected by improper authentication in the oidc provider. Deployments using OIDC email-based identity resolution with a provider that permits unverified email addresses may allow an authenticated provider user to assume another catalog identity. This may grant access and permissions associated with that user. No direct availability impact is demonstrated. This issue is fixed in version 0.4.20.
-
CVE-2026-106487 5.0 Moyenne
backstage · @backstage plugin-kubernetes-backend · Linuxfoundation backstage\/plugin-kubernetes-backend · Linuxfoundation backstage
Backstage is an open framework for building developer portals. Prior to 0.21.10, the @backstage/plugin-kubernetes-backend package is affected by unsupported catalog cluster authentication mode in kubernetes backend. Deployments using catalog cluster discovery may be affected when catalog contributors can create or modify kubernetes-cluster Resource entities. With the required endpoint permissions and pod RBAC, the backend can use its local in-cluster identity, potentially exposing Kubernetes resources readable by that identity. The credential is used only with the local in-cluster API endpoint and is not sent to the catalog-supplied endpoint. This issue is fixed in version 0.21.10.
-
CVE-2026-106463 5.4 Moyenne
backstage · @backstage plugin-catalog-backend-module-gitlab · Linuxfoundation backstage\/plugin-catalog-backend-module-gitlab · Linuxfoundation backstage
Backstage is an open framework for building developer portals. Prior to 0.8.7, the @backstage/plugin-catalog-backend-module-gitlab package is affected by improper authorization in gitlab organizational user ingestion. Deployments that enable GitLab organization event ingestion and rely on scoped catalog users as an access boundary may admit an unintended catalog identity. Depending on sign-in and permission configuration, this may allow unauthorized access with the permissions of a standard authenticated user. This issue is fixed in version 0.8.7.
-
CVE-2026-106462 6.4 Moyenne
backstage · @backstage plugin-scaffolder-backend · @backstage plugin-scaffolder-backend-module-azure · @backstage plugin-scaffolder-backend-module-bitbucket-cloud
Backstage is an open framework for building developer portals. Prior to 1.54.6, scaffolder source-control actions may not consistently enforce intended credential boundaries. An authenticated user could cause an affected action to fall back to broader integration credentials and perform operations with more access than intended. This issue is fixed in 1.54.6 when operators also enable scaffolder.requireScmUserCredentials after upgrading.
-
CVE-2026-106459 8.5 Élevée
backstage · @backstage plugin-scaffolder-backend-module-sentry · Linuxfoundation backstage\/plugin-scaffolder-backend-module-sentry · Linuxfoundation backstage
Backstage is an open framework for building developer portals. From 0.3.0 until 0.3.8, the @backstage/plugin-scaffolder-backend-module-sentry package is affected by improper input validation in sentry scaffolder actions. An authenticated internal user who can execute the affected actions may cause the backend to contact unintended destinations and disclose Sentry integration credentials. Subsequent impact depends on network reachability and the privileges granted to the configured token. This issue is fixed in version 0.3.8.
-
CVE-2026-106455 7.7 Élevée
backstage · @backstage plugin-techdocs-node · Linuxfoundation backstage plugin-techdocs-node · Linuxfoundation backstage
Backstage is an open framework for building developer portals. From 0.11.12 until 1.14.7 and 1.15.5, the @backstage/plugin-techdocs-node package is affected by improper validation of mkdocs plugin configuration in techdocs. An authenticated attacker with control over a TechDocs source repository could cause a documentation build to retrieve and publish data from network locations reachable by the build environment. Exposure depends on deployment topology, build mode, and target endpoint protections. Modern cloud metadata services that require tokens or special headers are not directly accessible through the affected behavior. This issue is fixed in @backstage/plugin-techdocs-node versions 1.14.7 and 1.15.5.