How severe is CVE-2024-55637?

CVE-2024-55637 has a CVSS score of 9.8/10, rated CRITICAL. Immediate patching is strongly recommended.

Which packages are affected by CVE-2024-55637?

CVE-2024-55637 affects the following packages: drupal/core (Packagist), drupal/core (Packagist), drupal/core (Packagist), drupal/core-recommended (Packagist), drupal/core-recommended (Packagist), drupal/core-recommended (Packagist), drupal/drupal (Packagist), drupal/drupal (Packagist), and 1 more. Ecosystems affected: Packagist.

How do I fix CVE-2024-55637?

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.

How do I detect CVE-2024-55637 in my Packagist dependencies?

Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for drupal/core. O3's reachability analysis confirms whether the vulnerable code path is actually invoked in your application, so you act on real exposure instead of every transitive match.

How do I mitigate CVE-2024-55637 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 CVE-2024-55637?

O3 pinpoints whether CVE-2024-55637 is reachable in your code and exactly where to fix it, then blocks exploitation in production at runtime until the patched version is deployed.

Is CVE-2024-55637 actively exploited in the wild?

No public exploit code has been indexed for CVE-2024-55637 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 CVE-2024-55637?

CVE-2024-55637 has an EPSS (Exploit Prediction Scoring System) score of 0.8%, placing it in the 52th 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 CVE-2024-55637?

CVE-2024-55637 is classified as CWE-915 (CWE-915), Deserialization of Untrusted Data (CWE-502). These weakness types describe the underlying flaw category, which helps determine the potential impact and the right class of mitigation. This is a high-impact weakness class that often enables remote code execution or data exposure.

When was CVE-2024-55637 published, and has it been updated?

CVE-2024-55637 was published on December 10, 2024 and was last updated on April 10, 2026. Advisory data evolves as severity scores, affected ranges, and exploit intelligence are revised — always check the latest version of the advisory before acting.

🐘 Packagist

CVE-2024-55637

CRITICAL

Drupal core contains a potential PHP Object Injection vulnerability

Also known asBIT-drupal-2024-55637DRUPAL-CORE-2024-007GHSA-w6rx-9g2x-mg5g

Published

Dec 10, 2024

Updated

Apr 10, 2026

Affected

9 pkgs

Patched

9 / 9

Exploits

None indexed

EPSS Exploitation Probability

via FIRST.org ↗

0.8%probability of exploitation in next 30 days

Lower Risk52th percentile-9.18%

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.

Blast Radius

9 pkgs affected

🐘drupal/core🐘drupal/core🐘drupal/core🐘drupal/core-recommended🐘drupal/core-recommended🐘drupal/core-recommended🐘drupal/drupal🐘drupal/drupal+1 more

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

Deserialization of Untrusted Data vulnerability in Drupal Core allows Object Injection.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.

Drupal core contains a chain of methods that is exploitable when an insecure deserialization vulnerability exists on the site. This so-called gadget chain presents no direct threat but is a vector that can be used to achieve remote code execution if the application deserializes untrusted data due to another vulnerability.

Affected Packages

9 total 9 fixed

Ecosystem	Package	Vulnerable range	Fix
🐘Packagist	`drupal/core`	≥ 8.8.0&&< 10.2.11	10.2.11
🐘Packagist	`drupal/core`	≥ 10.3.0&&< 10.3.9	10.3.9
🐘Packagist	`drupal/core`	≥ 11.0.0&&< 11.0.8	11.0.8
🐘Packagist	`drupal/core-recommended`	≥ 8.8.0&&< 10.2.11	10.2.11
🐘Packagist	`drupal/core-recommended`	≥ 10.3.0&&< 10.3.9	10.3.9
🐘Packagist	`drupal/core-recommended`	≥ 11.0.0&&< 11.0.8	11.0.8

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. O3's reachability analysis confirms whether the vulnerable code path is actually invoked in your application, so you act on real exposure instead of every transitive match.
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
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 pinpoints whether CVE-2024-55637 is reachable in your code and exactly where to fix it, then blocks exploitation in production at runtime until the patched version is deployed.

Tailored to CVE-2024-55637. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.

Frequently Asked Questions

Deserialization of Untrusted Data vulnerability in Drupal Core allows Object Injection.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. Drupal core contains a chain of methods that is exploitable when an insecure deserialization vulnerability exists on the site. This so-called gadget chain presents no direct threat but is a vector that can be used to achieve remote code execution if the application deserializes untrusted data due to another vulnerability.

O3 Security · Impact-Aware SCA

Is CVE-2024-55637 in your dependencies?

O3 detects CVE-2024-55637 across Packagist dependencies and uses function-level reachability to confirm whether the vulnerable code path is actually reachable — not just present. No false positives.

Scan my dependencies How O3 SCA works