How severe is GHSA-rjqg-3h9m-fx5x?

No CVSS score has been assigned to GHSA-rjqg-3h9m-fx5x yet. Review the advisory details and affected package list to assess your exposure.

Which packages are affected by GHSA-rjqg-3h9m-fx5x?

GHSA-rjqg-3h9m-fx5x affects the following packages: drupal/core (Packagist), drupal/core (Packagist), drupal/core (Packagist). Ecosystems affected: Packagist.

How do I fix GHSA-rjqg-3h9m-fx5x?

Update drupal/core to 9.5.11 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-rjqg-3h9m-fx5x is resolved across your whole dependency graph.

How do I detect GHSA-rjqg-3h9m-fx5x in my Packagist dependencies?

Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for drupal/core, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.

How do I mitigate GHSA-rjqg-3h9m-fx5x if there is no patch (or I can't update yet)?

If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.

How does O3 Security protect against GHSA-rjqg-3h9m-fx5x?

O3 Security's impact-aware SCA analyses which vulnerable code paths your application actually calls, so a match like GHSA-rjqg-3h9m-fx5x can be triaged on real exposure rather than presence alone.

Is GHSA-rjqg-3h9m-fx5x actively exploited in the wild?

No public exploit code has been indexed for GHSA-rjqg-3h9m-fx5x yet. This does not mean the vulnerability cannot be exploited — absence of public exploits does not imply safety. Apply the recommended fix and use O3 Security to monitor your exposure.

What is the EPSS score for GHSA-rjqg-3h9m-fx5x?

GHSA-rjqg-3h9m-fx5x has an EPSS (Exploit Prediction Scoring System) score of 0.8%, placing it in the 56th percentile of all CVEs. EPSS is maintained by FIRST.org and estimates the probability that a vulnerability will be exploited in the wild within the next 30 days. This score indicates relatively lower exploitation probability, though the CVSS severity should still guide your patching priority.

What type of vulnerability is GHSA-rjqg-3h9m-fx5x?

GHSA-rjqg-3h9m-fx5x is classified as Information Exposure (CWE-200). This weakness type describe the underlying flaw category, which helps determine the potential impact and the right class of mitigation.

When was GHSA-rjqg-3h9m-fx5x published, and has it been updated?

GHSA-rjqg-3h9m-fx5x was published on September 28, 2023 and was last updated on December 10, 2025. Advisory data evolves as severity scores, affected ranges, and exploit intelligence are revised — always check the latest version of the advisory before acting.

🐘 Packagist

Not in CISA KEV

GHSA-rjqg-3h9m-fx5x — drupal/core

Fix: drupal/core@1cd2741

GHSA-rjqg-3h9m-fx5x is a Information Exposure vulnerability in drupal/core. A fix is available for drupal/core — see the affected versions and patch details below.

Cache poisoning in drupal/core

Also known asBIT-drupal-2023-5256CVE-2023-5256DRUPAL-CORE-2023-006

Published

Sep 28, 2023

Updated

Dec 10, 2025

Affected

3 pkgs

Patched

3 / 3

Exploits

None indexed

Exploitation data as of Sep 24, 2026 · OSV.dev, NVD, FIRST.org (EPSS)

Exploitation Status

No confirmed exploitation observed yet

A successful exploit gives an attacker total control of the affected component, not partial access.
CISA’s own triage has not observed active exploitation or public proof-of-concept code for this CVE as of its last assessment.

Exploitation and automatability from CISA’s SSVC triage for GHSA-rjqg-3h9m-fx5x.

EPSS Exploitation Probability

via FIRST.org ↗

0.8%probability of exploitation in next 30 days

Lower Risk0.00%

Lower risk than most CVEs56th percentile — riskier than 56% of all scored CVEsHighest risk

EPSS (Exploit Prediction Scoring System) is a daily probability model maintained by FIRST.org. It estimates the likelihood a CVE will be exploited in production environments within the next 30 days, derived from real-world threat intelligence signals.

Real-World Exposure

3 pkgs affected

🐘drupal/core🐘drupal/core🐘drupal/core

Real-time download stats are indexed for npm and PyPI packages. This vulnerability affects Packagist packages — download data is not available via public APIs for these ecosystems.

Description

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.

Affected Packages

3 total 3 fixed

Ecosystem	Package	Vulnerable range	Fix
🐘Packagist	`drupal/core`	≥ 8.7.0&&< 9.5.11	9.5.11`composer require drupal/core:^9.5.11`
🐘Packagist	`drupal/core`	≥ 10.0.0&&< 10.0.11	10.0.11`composer require drupal/core:^10.0.11`
🐘Packagist	`drupal/core`	≥ 10.1.0&&< 10.1.4	10.1.4`composer require drupal/core:^10.1.4`

Detection & mitigation playbook

Open-source dependency

Detect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for drupal/core, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update drupal/core to 9.5.11 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-rjqg-3h9m-fx5x is resolved across your whole dependency graph.
Workarounds
If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.
How O3 protects you
O3 Security's impact-aware SCA analyses which vulnerable code paths your application actually calls, so a match like GHSA-rjqg-3h9m-fx5x can be triaged on real exposure rather than presence alone.

Tailored to GHSA-rjqg-3h9m-fx5x. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.

Frequently Asked Questions

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.

O3 Security · Impact-Aware SCA

Is GHSA-rjqg-3h9m-fx5x in your dependencies?

O3 Security finds GHSA-rjqg-3h9m-fx5x across Packagist dependencies, including transitive ones, and its impact-aware SCA ranks findings by whether your code actually calls the vulnerable path.

Scan my dependencies How O3 SCA works