CVE-2024-55637 is a critical-severity (CVSS 9.8) CWE-915 vulnerability in drupal/core. A fix is available for drupal/core — see the affected versions and patch details below.
Drupal core - Moderately critical - Gadget chain - SA-CORE-2024-007
Exploitation Status
No confirmed exploitation observed yet
- CISA assesses this as automatable — exploitation doesn’t require manual, per-target effort, which raises the odds of mass scanning and opportunistic attacks.
- 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 CVE-2024-55637.
EPSS Exploitation Probability
Probability of exploitation in the next 30 days, from FIRST.org EPSS.
How urgent is this, really
Where this sits among everything scored
Real-World Exposure
drupal/core🐘drupal/core🐘drupal/core🐘drupal/core-recommended🐘drupal/core-recommended🐘drupal/core-recommended🐘drupal/drupal🐘drupal/drupal+1 moreReal-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
Drupal core contains a potential PHP Object Injection vulnerability that (if combined with another exploit) could lead to Remote Code Execution. It is not directly exploitable.
This issue is mitigated by the fact that in order for it to be exploitable, a separate vulnerability must be present to allow an attacker to pass unsafe input to unserialize(). There are no such known exploits in Drupal core.
To help protect against this potential vulnerability, types have been added to properties in some of Drupal core's classes. If an application extends those classes, the same types may need to be specified on the subclass to avoid a TypeError.
This issue affects Drupal Core: from 8.0.0 before 10.2.11, from 10.3.0 before 10.3.9, from 11.0.0 before 11.0.8.
Affected Packages
| Ecosystem | Package | Vulnerable range | Fix |
|---|---|---|---|
| 🐘Packagist | drupal/core | ≥ 8.8.0&&< 10.2.11 | 10.2.11composer require drupal/core:^10.2.11 |
| 🐘Packagist | drupal/core | ≥ 10.3.0&&< 10.3.9 | 10.3.9composer require drupal/core:^10.3.9 |
| 🐘Packagist | drupal/core | ≥ 11.0.0&&< 11.0.8 | 11.0.8composer require drupal/core:^11.0.8 |
| 🐘Packagist | drupal/core-recommended | ≥ 8.8.0&&< 10.2.11 | 10.2.11composer require drupal/core-recommended:^10.2.11 |
| 🐘Packagist | drupal/core-recommended | ≥ 10.3.0&&< 10.3.9 | 10.3.9composer require drupal/core-recommended:^10.3.9 |
| 🐘Packagist | drupal/core-recommended | ≥ 11.0.0&&< 11.0.8 | 11.0.8composer require drupal/core-recommended:^11.0.8 |
Affected Products
drupaldrupalDetection & mitigation playbook
Open-source dependencyDetect
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 10.2.11 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2024-55637 is resolved across your whole dependency graph.
Workarounds
Do not deserialise data from untrusted sources: where the format allows it, restrict deserialisation to an explicit allowlist of expected types, and prefer a data-only format (JSON, Protobuf) over one that can reconstruct arbitrary objects until you can upgrade.
Frequently Asked Questions
Is CVE-2024-55637 in your dependencies?
Find it across Packagist, including transitive dependencies.