CriticalGHSA-rjqg-3h9m-fx5xBIT-drupal-2023-5256CVE-2023-5256DRUPAL-CORE-2023-006

Cache poisoning in drupal/core

Published 28 Sept 2023 · Updated 10 Dec 2025

Affected packages

drupal/coreComposer
Affected
>=8.7.0 <9.5.11
Fixed in
9.5.11
Update to the fixed version for your release line, for example:composer require drupal/core:^9.5.11
drupal/coreComposer
Affected
>=10.0.0 <10.0.11
Fixed in
10.0.11
Update to the fixed version for your release line, for example:composer require drupal/core:^10.0.11
drupal/coreComposer
Affected
>=10.1.0 <10.1.4
Fixed in
10.1.4
Update to the fixed version for your release line, for example:composer require drupal/core:^10.1.4

Details

In certain scenarios, Drupal's JSON:API module will output error backtraces. With some configurations, this may cause sensitive information to be cached and made available to anonymous users, leading to privilege escalation.

This vulnerability only affects sites with the JSON:API module enabled, and can be mitigated by uninstalling JSON:API.

The core REST and contributed GraphQL modules are not affected.

Is GHSA-rjqg-3h9m-fx5x 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.

Scan a project free, no signupOr connect GitHub to scan every repo

References

Advisory data from OSV.dev (opens OSV.dev in a new tab), refreshed daily.