Drupal Core Access bypass vulnerability
Published 24 May 2022 · Updated 10 Dec 2025
Affected packages
- Affected
- >=8.8.0 <8.8.10
- Fixed in
- 8.8.10
composer require drupal/core:^8.8.10- Affected
- >=8.9.0 <8.9.6
- Fixed in
- 8.9.6
composer require drupal/core:^8.9.6- Affected
- >=9.0.0 <9.0.6
- Fixed in
- 9.0.6
composer require drupal/core:^9.0.6- Affected
- >=8.8.0 <8.8.10
- Fixed in
- 8.8.10
composer require drupal/drupal:^8.8.10- Affected
- >=8.9.0 <8.9.6
- Fixed in
- 8.9.6
composer require drupal/drupal:^8.9.6- Affected
- >=9.0.0 <9.0.6
- Fixed in
- 9.0.6
composer require drupal/drupal:^9.0.6Details
Access bypass vulnerability in of Drupal Core Workspaces allows an attacker to access data without correct permissions. The Workspaces module doesn't sufficiently check access permissions when switching workspaces, leading to an access bypass vulnerability. An attacker might be able to see content before the site owner intends people to see the content. This vulnerability is mitigated by the fact that sites are only vulnerable if they have installed the experimental Workspaces module. This issue affects Drupal Core8.8.X versions prior to 8.8.10; 8.9.X versions prior to 8.9.6; 9.0.X versions prior to 9.0.6.
Is GHSA-x2q9-r8gm-f657 in any of your client repos?
Checking one package by hand is fine. Checking it across forty client projects is not. NPMscan reads the lockfiles in every GitHub repo you pick, finds each project with an affected drupal/core, and gives you the command that fixes it.
References
Advisory data from OSV.dev (opens OSV.dev in a new tab), refreshed daily.